Configure replication to AVEVA PI server

Note: 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 PI Server. This applies to replication servers added in Historian SP2025 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 AVEVA PI Server 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 AVEVA PI Server as the Replication Environment.

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

   • Node Name/IP Address

     Enter the node name or IP address of the PI Web API node.

     Note: If the PI Server node and the Historian nodes are in different domains, they must be trusted domains.

   • 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 AVEVA PI Server.

   • Connection Info

     Enter the username and password for the PI Web API User.

   • TCP Port

     Enter the listen port that the PI Web API is configured with.

   • Select whether or not to accept untrusted certificates:

     • Require a trusted certificate: Require a trusted certificate for communication between the IDAS and Historian.

       The server's certificate must be trusted on the IDAS system. If both nodes are connected to the same System Management Server, certificate trust is managed by the System Management Server. If the IDAS system and Historian are not connected to the same System Management Server, when you test the connection, the configurator either prompts you to trust the server's certificate, or logs an error message if it cannot retrieve the certificate information.

     • Accept an untrusted certificate (NOT RECOMMENDED): Allow an untrusted connection.

       Note: Requiring a trusted certificate is strongly recommended. Untrusted connections should only be used in test environments.
       
       When this option is enabled the certificate used by the PI server must be trusted on the Historian server. Obtain a copy of the certificate from the PI server and see Install a trusted certificate for further directions.

6. Click Test Connection to verify the connection details.

7. When the test connection is successful, click Next. The New Replication Server - Advanced dialog box appears.

   Summary replication is not supported for replication to AVEVA PI Server.

8. 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.

9. 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 AVEVA PI Server.

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