...
AssetTrack has an import process for loading this data into itself. This process is capable of importing from different types of sources, but this document deals only with importing data from files. In a nutshell, you export XML or TSV files containing the data that you want to be imported into AssetTrack. This can include data for assets, employees, products, locations, and departments. You place these files in a specific directory that is monitored by the file importer. At scheduled intervals, the file importer looks for these files and imports them into AssetTrack. Your data is then available on your mobile device forms and web forms.
Setting up the Import Service
The importer typically runs on the same machine as AssetTrack Server but can run on a different machine if necessary.
...
Directory name | Description |
Incoming | The “pickup” directory that the importer will search for files to import. |
Outgoing | The “delivery” directory where the exporter places files that are outbound from AssetTrack to an external repository. |
Error | The directory where the import files are placed when there is a fatal problem with the import attempt. |
Archive | The directory where the import files are placed after a successful import. |
Configuration
The importer is configured using AssetTrack Server’s web front-end. After logging into the AssetTrack web application, click on the “Settings” link at the top left.
...
Figure 5: This settings screen specify the various directories that are used by the importer.
The Import File Specifications
A detailed specification of the file formats needed by the File Importer are defined in Import file format specifications.
Deactivation and reactivation
When data is removed from your repository (or goes inactive), it is deactivated in AssetTrack (versus being deleted). If you’ve deleted a record or you simply wish certain records to not show up in AssetTrack, you can just stop providing the records in the XML data and AssetTrack will deactivate it accordingly. If the same record shows up later, it will be reactivated in AssetTrack.
Full Import versus Changes Only
For each daily import, import process expects to have a full snapshot of your repository data (versus changes only). In other words, if you have 100 assets in your repository and only one asset has changed since the last import, the import process still needs all 100 assets. This applies to all sets of data.
Logging and monitoring
The importer logs to the local Windows Event Viewer. The importer can be configured with a range of verbosity settings so provide more or less logging information.
...