How does Tracking Server work?

Tracking Server contains two functional elements: the tracking message server component and the tracking Web distribution component. These elements work together to collect and distribute tracking data to the people who use it on Web and desktop clients.

The Tracking Message Server Component

The tracking message server component is the engine and router that receives data via data links and server connections, processes actions based on location or location and attributes, logs data to geodatabases for later analysis, and pushes the data to various clients via data links.

Tip:

The tracking message server component runs as a Windows service, which you can stop and start from Tracking Server Manager or using the Tracking Server Controller.

The tracking message server component handles the routing of real-time data and command messages to connected systems using data links and server connections. The tracking message server component uses Microsoft Component Object Model (COM) technology to provide a robust, flexible architecture. This architecture allows developers to create data links to run within the process space of the server. Data links and server connections can be written in any language that supports multithreaded COM development such as C++. This is the recommended language for creating data links.

The Tracking Server Manager is used to control and manage the tracking message server component.

The Tracking Web Distribution Component

The tracking Web distribution component consumes the output from the tracking message server component and pushes this data to end user clients, such as ArcGIS Tracking Analyst or Tracking Viewer. The Tracking Server Client Gateway works as the tracking Web distribution component.

Tip:

The tracking Web distribution component runs as a Windows service, which you can stop and start using the Tracking Server Controller.