Using Tracking Server Web Monitor

Prerequisite:

Tracking Server Web Monitor requires that a supported version of the Adobe Flash Player be installed on the web browser that it is run in. The machine where Tracking Server is running must also have the Flex Policy Server running, so that Tracking Server Web Monitor has permission to access it. The Tracking Server Controller can be used to start the Flex Policy Server.

Tracking Server Web Monitor can be run either remotely (on a different machine than the Tracking Server it connects to) or locally (on the same machine as the Tracking Server it connects to). Also, Tracking Server Web Monitor may or may not be deployed to a Web server.

To use Tracking Server Web Monitor remotely, it is best that it be deployed on a Web server such as Apache or Internet Information Server. The Tracking Server Post Install application can be used to accomplish this. For more information, refer to the Tracking Server Install Notes document that was provided with your software.

Accessing Tracking Server Web Monitor

To access Tracking Server Web Monitor when it is deployed on a Web server, open a web browser and enter the following URL: http://<host_name>/TrackingServer/WebMonitor/index.html. For example, if you are connecting to Tracking Server Web Monitor and it is deployed locally, you would use: http://localhost/TrackingServer/WebMonitor/index.html. If you are connecting to Tracking Server Web Monitor and it is deployed on a machine named xyz, you would use: http://xyz/TrackingServer/WebMonitor/index.html.

To access Tracking Server Web Monitor if it is not deployed to a Web server, you must enter the full path to the TrackingServerWebMonitor/index.html file in your web browser, or simply open the file. A typical installation location for the “TrackingServerWebMonitor” folder is C:\Program Files\ArcGIS\TrackingServer\Gateway.

If your web browser has a supported version of the Flash Player installed, you will see Tracking Server Web Monitor in your browser. If not, you will be prompted to install a supported version of the Flash Player.

After Tracking Server Web Monitor appears in your web browser, a lot of information becomes available, as described below.

Steps:

1. Enter the server that is running the Gateway.

   In most cases, the Gateway is running on the same machine where Tracking Server is installed. Tracking Server communicates to client applications, including Tracking Server Web Monitor, through the Gateway.

2. Enter the Client Connection port number for the Gateway.

   The Client Connection port number can be found in the Gateway properties file. A typical location for the file is C:\Program Files\ArcGIS\TrackingServer\Gateway\bin.

3. Click Connect to connect to the Gateway using the Server and Port information.

   After connecting, you will be presented with all the information available in Tracking Server Web Monitor except for Tracking Services Status. You must log in using a valid username and password and click Authenticate in order to see this detailed information available for individual tracking services.

4. The IP address of Tracking Server connected to this Gateway.

   The IP address is highlighted in red text if Tracking Server is not connected to the Gateway.

5. Server Connection Date is the time when the connection was created between Tracking Server and the Gateway.
6. Number of connections to this Gateway.

   Tracking Server maintains a client connection to the Gateway.

7. The JVM Status Window shows various details about the Java Virtual Machine containing the Gateway process.
8. The Memory Usage Graph displays how much memory is being consumed by the Java Virtual Machine at any point in time.
9. The Tracking Services Status shows all of the Services available to the username/password combination that was used to connect. It shows the name of each service, the total number of messages that have been received through the service, the number of messages received in the last one second, and the amount of time that has passed since the last message was received.

   Clicking on the name of a service in the list causes detailed information about that service to appear, a Message Rate Chart and Service Definition information, as shown below.

10. The Time Since Last Message displays the amount of time that has passed since the last message was received. This text will turn red if the amount of time exceeds the Threshold Value, which may indicate a problem with the service.
11. The Threshold Value for Time Since Last Message is a user-defined amount of time. It should be set to the maximum expected time between data messages. If the amount of time defined by the Threshold Value has passed since the last message was received for a service, it indicates that there may be a problem with the service which may require further investigation.
12. Clicking on the name of a service in the Tracking Services Status list shows the Message Rate Chart for the service. The chart gives a history of how much data was received through the selected service at any point in the service’s history.
13. Clicking on the Service Definition tab displays more data about the service, such as the spatial reference and time zone of the data. A table is also included showing the attributes of the features in the selected service and the data types of the attributes.