Add AVEVA CONNECT as a replication server

If you want to connect from AVEVA Historian to CONNECT as a next-tier server, follow these steps. Historian supports up to three total replication server connections to CONNECT and PI Server.

Note the following about using CONNECT as a replication server:

• Asset names cannot include a question mark (?) or hash mark (#).

• If a tag's raw type is Integer but its minimum or maximum value is configured as a float value, the raw type will be changed to Float when it is replicated to CONNECT. This applies to replication servers added in Historian SP2023 R2 SP1 and later. If a replication server was added in an earlier version of Historian, the raw type will not be changed from Integer to Float. Re-add the replication server if you want a tag’s raw type to be changed to Float from Integer if its minimum or maximum value is configured as a float value.

To add CONNECT as a replication server

1. In the Operations Control Management Console, expand a server group and then expand a server.

2. Expand Configuration Editor, expand System Configuration, and then expand Replication.

3. Right-click Replication Servers and select New Replication Server. The New Replication Server dialog box appears.

   

4. Select CONNECT as the Replication Environment.

5. Configure the basic options for the replication server as follows:

   • Node Name/IP Address
     Specify a Node Name for the next-tier server. This name must not contain spaces.

     Note: This value is not used to connect to the target, but it is used for creating the configuration folder structure. If the name includes spaces, the configuration folder will not be created correctly. The connection details are determined when you click the Register... button.

   • Description
     Enter a description of the server. This description appears in the Operations Control Management Console and in Historian Client reports.

   • Store & Forward path
     Enter the store-and-forward path for data for this next-tier replication server. This must be an absolute path on the current computer. Remote paths are not supported for store-and-forward addresses.

   • Replicate Alarms and Events
     This option is not currently supported for replication to CONNECT.

6. Click Register... to sign in to CONNECT and select a tenant with access to CONNECT.

7. After a successful login, a list of available namespaces displays. CONNECT is hosted in multiple regions. Select a namespace in the appropriate region for your needs, then click Register. The New Replication Server dialog box redisplays. Your connection with CONNECT is registered, and a Client ID is generated and added to the Connection Info section.

8. Click Next. The New Replication Server - Advanced dialog box appears.

   

   Summary replication is not supported for replication to CONNECT.

9. In the Simple Replication Tag Naming Scheme area, select the replication tag naming scheme to use. Specify a custom naming scheme by selecting Custom and clicking the ellipsis button to the right of the box. The Naming Scheme dialog box appears. For information about configuring the naming scheme, see Specify naming schemes for replication.

10. Configure the remaining advanced settings as follows:

    • Min SF Duration

      Enter the minimum duration in seconds for the replication service to function in store-and-forward mode. The replication service functions in store-and-forward mode for this length of time even if the condition that caused the replication service to function in store-and-forward mode no longer exists. The duration can be an integer from 0 to 3600. Pick a value that provides a smooth transition for store-and-forward operation and prevents the system from repeatedly going in and out of store-and-forward mode.

    • Buffer Count

      Enter the number of 64KB buffers to allocate for the new replication server. This can be an integer from 128 to 2048. You may need to increase the buffer count to accommodate high data rates.

    • SF free space

    • Compression Enabled, Bandwidth, High Latency Network

      These options are not used for replication to CONNECT.

11. Click Finish. The new replication server appears in the replication server list.

Upgrading SP2023 R2 replication servers

Existing replication servers configured in SP2023 R2 will not send data to CONNECT data services after you upgrade to SP2023 R2 SP1 unless

• you have Tenant Contributor privileges for CONNECT, or

• you re-register each replication server with CONNECT data services.

Whenever possible, we recommend re-registering each replication server with CONNECT data services when upgrading from SP2023 R2 to SP2023 R2 SP1.

Limitations of using CONNECT data services as a replication server

• Forward-slash is not supported in replicated destination tag names.

• The following set of characters are supported in replicated destination tag names, however they will be replaced by ASCII codes in CONNECT data services: * ? ; {{ }} [ ] | \\ ` ' \"

• When replicating to CONNECT data services, if multiple assets in Application Server have the same contained name, use different contained names for those assets. If the contained name is created in App Server before replication, the destination tag name should use the contained name instead of the object name.

• CONNECT data services supports Asset IDs (the combination of asset name, hierarchy position, and tag name) of up to 250 characters. Asset IDs of more than 250 characters may result in incorrect metadata.

• Existing tags in CONNECT data services, as well as the hierarchy in Visualization, can only be updated or deleted manually.

• If you update the tag type of a replicated tag, the tag must be re-added to the replication list.