The ServiceControl installation file consists of an embedded MSI bootstrapper EXE and an embedded MSI. This installation can be executed standalone or via the Platform Installer. The installation package include a utility to manage the installation, upgrade and remove of ServiceControl services, including Monitoring instances. This utility is launched as the final step in the installation process and is also available via the Windows Start Menu.
The ServiceControl installation has the following prerequisites:
If ServiceControl is installed via the Platform Installer, then the installer will manage installation and configuration of the prerequisites.
Monitoring instances can be configured to use one of the supported transports listed below using the ServiceControl Management application:
- Azure Service Bus
- Azure Service Bus - Endpoint-oriented topology
- Azure Service Bus - Forwarding topology
- Azure Storage Queues
- Amazon Simple Queue Service (SQS)
- Microsoft Message Queuing (MSMQ)
- RabbitMQ - Conventional routing topology
- RabbitMQ - Direct routing topology
- SQL Server
Certain transport features are not supported natively by ServiceControl and will require a transport adapter. Contact email@example.com for further guidance.
Adding third-party transports via the ServiceControl Management application is not supported.
If MSMQ is the selected transport, then ensure the service has been installed and configured as outlined in Installing The Platform Components Manually.
Installing MSMQ is optional in the Platform Installer. See Platform Installer - MSMQ.
ServiceControl Management provides a simple means of setting up one or more Monitoring instances.
ServiceControl Management can be launched automatically at the end of the installation process to enable adding or upgrading ServiceControl or Monitoring instances.
ServiceControl Management will display the list of installed ServiceControl and Monitoring instances. If the version of the binaries used by an instance are older that those shipped with ServiceControl Management, an upgrade link will be shown against the version label.
To upgrade the service, click the upgrade link next to the service name.
Clicking the upgrade link will:
- Prompt for any new information that is required to run properly on the transport of choice.
- Stop the Monitoring instance Windows Service.
- Remove the old binaries.
- Run the new binaries to upgrade the Monitoring instance by applying new settings and/or creating any required additional queues.
- Start the Monitoring instance Windows Service.
Click on the
+ NEW link at the top of the screen and select "Monitoring instance" to launch the "New instance form". Complete the form to register a new Monitoring instance service.
When adding the first Monitoring instance service the default service name is
Particular.. It is possible to change this name to a custom service name. In doing so this is also changing the queue name associated with this Monitoring instance.
The metrics endpoint plugin will need the Monitoring instance name in order to send metric data to the Monitoring instance.