Appendix B: Other (Optional) Configuration Notes

Manual Deployment of Tracking Applications to Web Server

If you prefer to manually deploy Tracking Viewer or Tracking Server Web Monitor to a Web server, rather than using the Tracking Server Post Installer, you can follow these steps:

  1. Identify the home folder for your Web server where published documents are stored. For Apache this location is usually <Apache installation folder>/htdocs. For IIS this location is usually C:\InetPub.
  2. To manually deploy Tracking Viewer, locate the "Viewer" folder inside of the Tracking Server installation folder. Simply copy the entire “Viewer” folder into your Web server’s publication root (from step 1). For example, a typical installation location for the “Viewer” folder is C:\Program Files\ArcGIS\TrackingServer.
  3. To manually deploy Tracking Server Web Monitor, locate the "TrackingServerWebMonitor" folder inside of the Tracking Server installation folder. Simply copy the entire “TrackingServerWebMonitor” folder into your Web server’s publication root (from step 1). For example, a typical installation location for the “TrackingServerWebMonitor” folder is C:\Program Files\ArcGIS\TrackingServer\Gateway.

Installing the Tracking Server SDK

The Tracking Server SDK provides tools for customizing your Tracking Server. It contains technical documentation intended for developers, templates for custom development in Visual Studio, and sample applications that can be used with Tracking Server.

The Tracking Server SDK is included with Tracking Server. It can be installed by running the Tracking Server Installer and clicking Setup next to "Tracking Server SDK".

Changing the Client Connection Port

If you choose to reconfigure Tracking Server to listen for connections on a port other than 5506, follow these steps:

  1. Open the gateway properties file under <Tracking Server Location>\Gateway\bin.
  2. Modify the property called "clientport" to the desired value.
  3. Save the file.
  4. Restart the Gateway Service.
CautionCaution:

These changes will not be reflected in the gateway unless the Gateway Windows Service is restarted.

Feature Logger

Feature Logger is a data link that provides the capability for real-time data messages to be logged to a database. Currently, Feature Logger can log to personal geodatabases and ArcSDE SQLServer databases. Feature Logger will create the tables within a created geodatabase. It is the sole responsibility of the user to perform database tuning. Refer to Tracking Server Help, installed with Tracking Server, for more information on using Feature Logger.


Published 7/8/2010