Overview of Publishing Real-Time Services
Real-time data from Tracking Server must be published as a tracking service in order for client applications to consume the real-time data. There are three Tracking Server components involved when publishing services from Tracking Server:
- Tracking Server Connector Data Link
- Tracking Gateway
- Web Connector (Optional Component)
Tracking Server Connector Data Link
The Tracking Server Connector Data Link is required in order to publish real-time services from Tracking Server. It connects to the Tracking Gateway and publishes real-time data to the Tracking Gateway. For real-time services to be working correctly, the Tracking Server Connector Data Link must be running and succussfully connected to the Tracking Gateway at all times.
Client applications connect to the Tracking Gateway in order to subscribe to real-time services from Tracking Server. Therefore, if the connection between the Tracking Server Connector Data Link and the Gateway is disrupted for any reason, real-time data is not able to stream from Tracking Server.
A typical Tracking Server installation uses a single Gateway to transmit real-time data to client applications, but multiple Gateways can be used for scalability.
Web Connector (Optional)
The Tracking Server Web Connector is an optional new component introduced with Tracking Server 10.1. The Web Connector connects to the Gateway in a similar way to other client applications. The Web Connector extends the capabilities of the Gateway by allowing tracking services to be consumed via REST in Web-friendly formats.
If the Web Connector is set up, configured, and running properly, then all real-time tracking services available from the Tracking Gateway will also be available through the Web Connector.