User privileges required for replication to a PI server

When configuring replication from an AVEVA Historian to a PI Server, the Historian node needs sufficient permissions to write data to the PI Data Archive. Access control in PI is managed through Trusts, which define what users or systems can send data to the server.

Usually, replication from Historian to PI should work without any mapping present. However, if you encounter issues, create a trust mapping with a user identity that has sufficient permissions for replication.

Access the Trust configuration

1. Launch PI System Management Tools (SMT) on the PI Server.

2. In the navigation pane under System Management, select Security > Mappings & Trusts

3. The Mappings & Trusts window displays all existing security mappings and trust entries configured for your PI Data Archive.

Create or edit a Trust

To configure a remote Historian node to replicate data into the PI Server:

4. In the Mappings & Trusts window, open the Trusts tab.

5. Select New Trust or choose an existing trust and select Edit.

6. Configure the trust with the following settings:

   • Type of trust: PI-API application.

   • Network Path / IP Address: Enter either the Network Path or IP Address and NetMask of the Historian node.

   • PI Identity: Assign the appropriate PI user identity that determines privilege level.

7. Select Apply to save the changes.

User identities that support replication

The following PI Identities have been verified to successfully enable replication from Historian to PI: