Creating AVEVA Gateway Data Publisher Instances

The AVEVA™ Gateway Data Publisher instances for your AVEVA Gateway are created using the InitGdpCfg.json file available at the installation location of AVEVA™ Gateway Data Publisher. A sample location is as follows: C:\Program Files\AVEVA\AVEVA Gateway Data Publisher\Examples\Configuration

The following image provides an example for the contents of the InitGdpCfg.json file.

To create an instance of AVEVA™ Gateway Data Publisher for your AVEVA Gateway:

1. Open the InitGdpCfg.json file from the following location: <installation location of the gateway data publisher>\Examples\Configuration.

2. Add an init command to the file in the syntax provided in the image above.

   The init command must contain the following parameters:

   • instance-name - Name of the AVEVA™ Gateway Data Publisher instance.

   • logs-location-path - Location for the log files for the AVEVA™ Gateway Data Publisher.

     If you specify this parameter, it overrides the default logs location for AVEVA™ Gateway Data Publisher and its instances.

     The default logs location for a user account is C:\Users\{user.name}\AppData\Local\Gdp\Logs

     The default logs location for the system account is C:\Windows\System32\config\systemprofile\AppData\Local\Gdp\Logs

     Log files can be accessed anytime while AVEVA™ Gateway Data Publisher and instances are running. The format for the name of the log files is as follows: gdp-service_dd-mm-yyyy_HH-MM-SS_RndNo

   • config-file-path - Location of the configuration file for the instance.

   • watched-directory - The location that is currently watched by AVEVA™ Gateway Data Publisher.

     AVEVA™ Gateway Data Publisher can detect the trigger.start file in any of the sub folders of this location. The changes are picked for publishing from the folder where the trigger.start file is located and all its sub folders.

     You can change the location of the watched directory by changing the location in the InitGdpCfg.json file. After you make the changes and save the file, the instance is restarted.

   • staging-database-directory - (Optional) Location of the database directory for AVEVA™ Gateway Data Publisher. If you want to store the database at a custom location, you need to add this new parameter to the InitGdpCfg.json file as shown in the following image:

     

     By default, the staging area for the database directory is located at the same location as the watched-directory but with the suffix .gdp.

You can dynamically add or remove instances by adding or removing the RunGDP commands to InitGdpCfg.json file. After you make the desired changes and save the file, the instances are added or removed accordingly.

Note: In addition, you must also create a file with the name specified in the Value section of the config-file-path argument. For information on how to create this file and the contents of it, see Configuring AVEVA Gateway Data Publisher for Your AVEVA Gateway.

You can also specify these settings through the GDP Service Manager tool. For information on how to use the GDP Service Manager tool, see Running AVEVA Gateway Data Publisher as a Windows Service.