Start Responder Services

Once you have finished configuring the various Responder Services you will need to start them. To start the services use the Responder Windows Service.

You will also need to start an instance of Query Services and Telemetry Services. To do this, open Computer Management on the Responder Server (right-click My Computer and select Manage). Expand Services and Applications and select Services. In the right-side window, right-click Responder Query Service and select Start. Repeat this step for the Telemetry Service (if configured.)

Determine the Number of Services

When determining the number of services to start consider the following:

For every 5000 calls per hour expected, you will need a dedicated instance of Data Services to handle the volume. If the server or database machine is not large enough to process at this rate, the number of dedicated Data Services may need to be increased.
Pair up Prediction Services and Data Services (1:1) to a level that you can handle all of the predictions and incident processing after call processing is complete. You may have to experiment with test scenarios with a maximum expected call volume to determine the correct settings.
After ensuring one instance of Data Services is running for every instance of Prediction Services running, start up one more instance of Data Services. This instance will handle writing calls to the database.
You may also want to start an additional instance of Data Services to handle dispatchers in the system.
We recommend running only one instance of Line Display Services across all servers. Running more than one could potentially cause conflicts which may result in incorrect Line Display data.
Always be aware of the amount of CPU being used. If you start to max out the CPu frequently or start paging large amounts of memory, you may need to reduce the number of services or upgrade the machine.

For a small utility, consider starting with the following.

Data Services: 5

Prediction Services: 3

Archive Services: 2

Query Services: 1

Line Display Services: 1

Telemetry Services: 1

Note, this is only a suggested starting point. Adjust the number of services as needed to best suit your needs.

The following metrics can aid in determining whether you're running the optimal number of services.

Calls Waiting to Process: Watch the number of calls that have exceeded the callStewCookTime value (set during Prediction Services configuration) but have not yet been processed. If you have a large number of calls eligible to be processed, then additional Data Services/Prediction Services instances would help process these calls in a more timely manner. To examine the calls metric, you may need a DBA to create a database query that identifies any rows that have a null incident ID and an expired callStewCookTime value (this value is greater than the current time).

Responder Data Services Low Message Queue: Watch the rxserver.service.low message queue. If this queue is building up, you will need additional Data Services instances to handle the entry of calls into the system.