Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA NET Gatekeeper and AVEVA Change Manager

Automated Data Exchange in AVEVA NET Gatekeeper

  • Last UpdatedApr 30, 2026
  • 2 minute read

This feature handles both import and export of data based on the configuration settings made in TIM.WDA.SystemApplication.Config.xml. Your administrator can configure the export and import folders using the <DataExchange exportPath="C:\DocumentManager.TIM\Export" importPath="C:\DocumentManager.TIM\Import"/> element in web.config.xml during the installation. For more information, refer to AVEVA NET Gatekeeper and AVEVA Change Manager Administration Guide.

Automated Data Exchange: Data Import

Based on the system configuration, in TIM.WDA.SystemApplication.Config.xml, AVEVA NET Gatekeeper uses an import service to periodically check for XML files available for import from the C:\DocumentManager.TIM folder. AVEVA NET Gatekeeper periodically inspects an inbound Windows folder configured by your administrator for a Working Set Bulk Upload XML file or set of files. The application validates the files being uploaded, and reports errors that occur in an XML file, which is available in the sub-folder configured by the import service. Once the file is imported, the import service automatically creates an outbound folder for the file to place the result. Ensure that the NETWORK SERVICE account has the required permissions for AVEVA NET Gatekeeper to access the C:\DocumentManager.TIM\ImportGK\<Customer Name> folder. The import directory contains the Inbound and Outbound folders. The Inbound folder contains the Bulk Upload XML files intended for import. The Outbound folder contains the Bulk Upload XML files containing the data updated during the data import operation. The files in these folders contain the validation and system errors assigned to the <DataSet .../> section that to the Working Set or operation itself. You can use the settings in the TIM.DataExchange.ImportService import service to automate the process.

Note: The Greenfield Bulk Upload Working Set XML file should not contain the workingSetId attribute.

TitleResults for “How to create a CRG?”Also Available in