Deploy a system configuration

After you export a system configuration, you have to manually deploy the configuration to the edge device in the field.

For details on how to deploy a configuration, see the specific system product documentation:

• AVEVA Adapter for Azure Event Hubs

• AVEVA Adapter for BACnet

• AVEVA Adapter for DNP3

• Edge Data Store

• AVEVA Adapter for Modbus TCP

• AVEVA Adapter for MQTT

• AVEVA Adapter for OPC UA

• AVEVA Adapter for RDBMS

• AVEVA Adapter for Structured Data Files

After deploying the configuration, manually update the configuration file on the device to replace any mustache tokens used as place holders for secrets with the actual secrets. Then, to have an accurate record of the configuration, import the configuration file, including any modifications made in the field except secrets, to the corresponding system twin in CONNECT data services.

Data source scenarios

If you need to access multiple data sources on the same device, you need to differentiate the data sources. You can use the following options to identify the data sources:

• Static IP address

• Fully qualified device name

We recommend you review your specific scenario with your network administrator to determine the appropriate configuration for your use case.