Responder Server

Responder Services include the following: Data Services, Prediction Services, Line Display Services, and Archive Services. You can now install the appropriate Server components that are explained below. These services may be installed on a single Responder server or separately on individual servers. By default, the configuration files for Responder Services are installed here: Program Files (x86)\Miner and Miner\Responder\Server. The Responder Windows Service may be used to manage these three services once they've been configured.

 

Multiple Responder Servers: If you are running multiple Responder servers, the configuration files for the redundant services MUST be configured the same. For example, if Prediction Services is configured even slightly differently on two different servers, you will see inconsistent prediction. Ensure that configuration files remain consistent across multiple servers.

• Data Services: This service acts as a liaison between Responder Explorer, the Responder database, and the Responder web interface. Data Services must be configured and running in order for Responder Explorer to be opened and utilized. Perform the following configurations:

  Data Services (Miner.Responder.DataServices.exe.config)

  Callbacks (Miner.Responder.DataServices.exe.config)

  Message Queuing

  Submit Rules (optional)  

• Prediction Services: This service fuels Responder's prediction engine. It is responsible for all incident prediction and roll-up. Prediction Services is not required, however it offers valuable outage prediction functionality and it is highly recommended that it be implemented. Perform the following configurations.

  Prediction Engine

  Prediction and SCADA

  Prediction Services configuration (Miner.Responder.PredictionServices.exe.config)

  Turn Off Probable State (optional) 

• Query Windows Service: This service handles refreshing and some queries to improve Data Services performance. If this service is not configured properly, the refreshing and queries are handled by Data Services. This service does not have a tab in the Responder Windows Service web browser.

• Message Router: This business service facilitates communication between the primary business server and any secondary business servers. If you have only one business server and one set of message queues, this configuration is not necessary and the Message Router tab won't appear in your Responder Windows Service web browser.

• Message Queuing: Message queuing allows the various Responder components to communicate. It must be enabled on the machine that hosts the Responder services (Data Services, Prediction Services and Archive Services) and on the client machine. 

• Line Display Service: This service allows you to include the line energization state on the map. Use the Line Display Services tab to configure, manage and execute Line Display Services. It is recommended that the Responder Data Services business service run on the same machine as the Line Display Service.

• Telemetry Service: This service allows you to gather stastical information on the processing of Responder data.

• Archive Services: This service acts as a liaison between Archive Explorer and the archive tables in the Responder database. Archive Services allows you to view and edit historical outage data. Also, when Archive Services is running, all incidents closed in Responder Explorer are automatically added to the Archive tables and made available in Archive Explorer. Perform the following configurations.

  Archive Services configuration (Miner.Responder.ArchiveServices.exe.config)

  History and Archive Tables (optional)

  Archive Log File (optional)

  Archive Cancelled Incidents (optional)

  Archive Submit Rules (optional)

  After you have configured Archive Services, you must assign the proper permissions to the message queues. These message queues are created when Archive Services is started for the first time. Start Archive Services, stop it, then assign permissions to the resulting message queues.

The XML files referenced above are located in the Responder/Server directory on the machine that hosts the Responder services. Once the Responder Services have been configured, the corresponding executable files must be launched. This may be done using the Responder Windows Service or by double-clicking the Miner.Responder.DataServices.exe, Miner.Responder.PredictionServices.exe, and/or Miner.Responder.ArchiveServices.exe files in Miner and Miner\Responder\Server. Both of these executable files are located in the same directory as the configuration files.

If you are using an Oracle database, your Responder server requires a Local Net Service Name.

Optionally, you may configure Responder to check out a specific Esri license. More information is available on the License Override page.