Before Using AVEVA Gateway Data Publisher
- Last UpdatedApr 01, 2026
- 2 minute read
Before using AVEVA™ Gateway Data Publisher, you must make sure that the following tasks are performed.
-
The prerequisites mentioned in System Requirements and Other Prerequisites are met.
-
Access tokens are configured for each instance of the AVEVA™ Gateway Data Publisher.
-
The staging area for your AVEVA™ Gateway Data Publisher instance is defined. For information on how to set the staging area, see Configure AVEVA Gateway Data Publisher for Your AVEVA Gateway.
-
The URL for publishing the data through AVEVA™ Ingestion Service is set in AVEVA™ Gateway Data Publisher. For information on how to do this, see Configure AVEVA Gateway Data Publisher for Your AVEVA Gateway.
Gateway Data Publisher 1.4 onwards, following changes are applied.
-
Publisher node does not accept TokenName and DefaultEndPointUrl properties. Instead, it now supports EndPointName property. EndPointName is optional and it's default value is default.
-
Gateway Data Publisher instance will now decrypt the EndPointUrl and AccessToken by using EndPointName. If EndPointName is not provided, it will use default.

To make the existing configuration settings compatible with the latest GDP installation, perform the following steps:
-
For GDP instance configuration Publisher node:
-
Change Version to 1.4 (at the beginning of configuration file)
-
Replace TokenName with EndPointName and leave the same value (skip if TokenName was not present)
-
Remove DefaultEndPointUrl property
-
-
Run Gdp.Service.Exe token add --name "{EndPointName}" --value "{NewAccessToken}" --end-point "{DefaultEndPointUrl}"
