OVERVIEW

Installation

• Choosing a Host
• Deployment
• Reinstalling or Upgrading
• Installation Defaults

Configuration

• Instrumenting Applications
• Dispatch Service
• Endpoint Web Service
• Customer Experience Improvement Program

Management

• Restarting
• Performance Tuning

Monitoring

• Event Log
• WMI Counters
• RabbitMQ Monitoring

Troubleshooting

• Troubleshooting
• Deleting Messages
• HTTP Details

Advanced Configuration

• RabbitMQ
• Logging

LICENSE

Restarting

In some situations, you may need to restart either the Dispatch Service alone, or the entire Data Hub. Follow the steps below to ensure minimal downtime for the components in question.

Restarting the Dispatch Service

Configuration changes to the Dispatch Service are made by editing the Dispatch.config file and restarting the Dispatch Service. Restarting the Dispatch Service will briefly interrupt message delivery, but will not lose any data, and the Endpoint Web Service will continue to accept and queue new data.

To restart the Dispatch Service:

1. Open the Services console (services.msc).
2. Select PreEmptive Analytics Data Hub Dispatch Service, and note its current Status (e.g., Running).
3. Click Restart the service.
4. Ensure that the service stops and then starts properly.

Troubleshooting Service Shutdown

If the service does not stop properly, it is safe to forcefully end and then start the service:

1. Open Task Manager (taskmgr.exe).
2. Select the PreEmptive Analytics Data Hub Dispatch Service or HubDispatchService.exe process.
3. End the task.
4. In the Services console, refresh the page and select Start the service.

Troubleshooting Service Startup

If the service does not start properly, troubleshoot configuration errors:

1. Check the Event Log for errors.
2. Follow the instructions in the error message to correct any configuration errors.
3. In the Services console, click Start the service.
4. Repeat as necessary.

Restarting the Entire Data Hub

WARNING: Restarting the Data Hub will cause a temporary outage at the Endpoint. Messages sent by instrumented applications may, depending on the application's offline storage configuration, be lost.

To restart the Data Hub's components entirely, follow the directions in the following sections, in order.

Stop the Dispatch Service

1. Open the Services console (services.msc).
2. Locate PreEmptive Analytics Data Hub Dispatch Service.
3. Select Stop the service.

Stop the Endpoint Web Service

1. Open the IIS Manager (inetmgr.exe).
2. Under the server node, select the configured Web Site.
3. Select Stop from the Actions pane.

The Data Hub is now offline.

Stop RabbitMQ

1. Open the Services console (services.msc).
2. Locate RabbitMQ.
3. Select Stop the service.

Start RabbitMQ

1. Open the Services console (services.msc).
2. Locate RabbitMQ.
3. Select Start the service.
4. If the service does not start, check the RabbitMQ log folder for errors: [RabbitMQ data folder]\log.

Start the Endpoint Web Service

1. Open the IIS Manager (inetmgr.exe).
2. Under the server node, select the configured Web Site.
3. Select Start from the Actions pane.
4. If the service does not start, check the Event Log for errors.

The Data Hub is now back online. You should check the Event Log for any errors or warnings.

Start the Dispatch Service

1. Open the Services console (services.msc).
2. Locate PreEmptive Analytics Data Hub Dispatch Service.
3. Select Start the service.
4. If the service does not start, check the Event Log for errors.