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

Endpoint Web Service

After install, the Endpoint Web Service is active and ready to accept any incoming messages at the Endpoint URL displayed when the installer completes. However, scenarios such as setting up SSL require additional configuration.

Accepting SSL Connections

To use SSL for incoming messages, upstream clients (typically instrumented applications), must be configured to initiate requests via HTTPS. See the appropriate documentation included with your PreEmptive Analytics product(s) to configure instrumented applications appropriately.

Importing Certificate(s)

To configure SSL, you must import a valid, trusted SSL certificate in .pfx format. To import this certificate into IIS:

1. Open the IIS Manager (inetmgr.exe).
2. Select the server node.
3. Select Server Certificates.
4. Choose Import... from the Actions pane.
5. Follow the steps to import the .pfx file.

These changes take effect immediately, no restart is required.

Enabling

To configure the Endpoint Web Service to use HTTPS:

1. Open the IIS Manager (inetmgr.exe).
2. Under the server node, select the configured Web Site.
3. Choose Bindings... from the Actions pane.
4. Click Add....
5. Choose https in the Type drop-down.
6. Choose the Port (443 is the default).
7. Choose the imported certificate in the SSL certificate drop-down.
8. Select OK.
9. Select Close, then close the IIS Manager.
10. Ensure your firewall configuration allows access as appropriate.

These changes take effect immediately, no restart is required.

Note: If you wish to prevent unencrypted data transfer, then you must also remove the original http binding.

Disabling

To remove HTTPS support:

1. Open the IIS Manager (inetmgr.exe).
2. Under the server node, select the configured Web Site.
3. Choose Bindings... from the Actions pane.
4. Select the appropriate HTTPS binding.
5. Click Remove.
6. Click Yes.
7. Select Close, then close the IIS Manager.
8. Review your firewall configuration and ensure ports are not left open unnecessarily.

These changes take effect immediately, no restart is required.

IIS Idle Time-Out

IIS Application Pools, such as the one associated with the Endpoint Web Service, have an Idle Time-out feature. If the service receives no requests for the specified amount of time (default is 20 minutes), it will become inactive to conserve resources. When a request is received by IIS, the service will reactivate. This feature affects the Endpoint Status WMI counter.

To change or disable the time-out:

1. Open the IIS Manager (inetmgr.exe).
2. Under the server node, select Application Pools.
3. Select the PreEmptive Analytics Data Hub pool.
4. SelectAdvanced Settings... from the Actions pane.
5. Under the Process Model section, locate Idle Time-out (minutes).
6. Modify the value associated with that field:
   • To change, specify the number of minutes for the time-out.
   • To disable, specify 0.
7. Click OK.

These changes take effect immediately, no restart is required.

Maximum Request Size

The Endpoint Web Service has a maximum request size to protect against denial-of-service attacks from large requests. While the default setting of 4194304 bytes (4 MiB) is orders of magnitude above the typical message size, you may wish to adjust it for specific scenarios.

To change the maximum request size:

1. Open [Application folder]\Web\Web.config.
2. In the <system.webServer> section, under <security> and <requestFiltering>, locate the <requestLimits> element.
3. Alter the maxAllowedContentLength attribute to indicate the maximum request size, in bytes.
4. Save the file.

These changes take effect immediately, no restart is required.

Support for Cross-Domain Silverlight Clients

If clients are sending messages from Microsoft Silverlight web applications and said web application is not hosted on the same domain as the Data Hub, additional configuration is required for security purposes via clientaccesspolicy.xml, crossdomain.xml, or both.

After creating said file(s) with the appropriate permissions for your application, copy the file(s) to the [Application folder]\Web folder. No restart should be required.