Exporting and Importing Configurations
The Import / Export Configurations feature in Tracking Server Manager allows you to quickly and easily transfer an entire Tracking Server configuration from one machine to another. This includes message definitions, tracking services, service history settings, logging settings, data link configurations, Feature Logger settings, and actions.
The entire Tracking Server configuration is exported to a configuration file (.cfg), which can be imported into another Tracking Server.
When importing a configuration, configurations are appended to existing configurations. If any part of the configuration already exists, it wil be overwritten. For example, if a service named "Cars" is being imported and it already exists, then the existing service will be replaced with the imported one.
-
Open Tracking Server Manager and start the source Tracking Server that will be exporting its configuration, if it is not already running.
- Click File to expand the File menu and click Export Configurations...
- Browse to the location where you would like the configuration file to be saved and click Save.
Optionally, you can change the name of the file containing the exported configuration. The file is given the .cfg file extension.
- Move the configuration file to a location that will be accessible to the Tracking Server that will import it.
- Open Tracking Server Manager and start the target Tracking Server that will be importing the configuration, if it is not already running.
- Click File to expand the File menu and click Import Configurations...
- Browse to the configuration file, select it, and click Open.
- If any part of the configuration already exists on the target Tracking Server, you will see a dialog box listing which entities (for example, message definitions and services) will be overwritten. Click OK to proceed with the import.
If you do not want to overwrite any configuration entities (for example, message definitions and services) that are listed, you can click Cancel to cancel the entire import.
- The target Tracking Server now contains the same configurations as the source Tracking Server.
Caution:Some configurations are dependent on other properties of the machine on which Tracking Server is installed. Take note of the following dependencies for importing the following configurations:
- Feature Logger: If you are importing Feature Logger settings, then the SDE connection files required for the database connections must be moved from the source machine to the appropriate location on the target machine. Connection files are typically stored in locations such as C:\Documents and Settings\username\Application Data\ESRI\Desktop10.1\ArcCatalog or C:\Documents and Settings\username\Application Data\ESRI\Engine10.1\ArcCatalog, depending on whether you have Engine or Desktop installed. Also, if client database software is required for the database connection, the same client database software must be installed on the target machine.
- Error Logging: If paths to log file locations are specified on the source machine, then the exact same paths must exist on the target machine.
- Email Templates for Email Alerts: If you want to preserve the e-mail alert templates that exist on the source machine, you must copy the "TrackingEmailAlertConfig.cfg" file (in [Tracking Server install location]\bin) from the source machine to the target machine. If the file already exists on the target machine and you replace it, this will delete any existing e-mail alert templates on the target machine.
- Location Triggers: If you are importing actions that use location triggers, then the polygon data used in the triggers must be moved from the source machine to the exact same file location on the target machine. If this is not done, the imported location trigger will not work.
- Complex Services: If you are importing a complex service that uses a static Object Data Source table, you will need to edit or recreate the complex service in order to reload the records stored in the Object Data Source table.