Create a trust to view historical data (Advanced Continuous Historian) on a remote system from DeltaV Operate

Explicit logins are not supported in the Advanced Continuous Historian. You must create a trust for the remote client by completing the following steps:

Note

This procedure applies to DeltaV Operate workstations only. DeltaV Live workstations use the Windows user authentication method described in a separate topic.

Log on as Administrator to the system where the Advanced Continuous Historian is installed.
Start the PI System Management Tools by clicking All Programs → PI System → PI System Management Tools.
In the PI System Management Tools window, navigate to Security → Mappings & Trusts, and then select the Trusts tab.
Start the Add Trust Wizard by right-clicking in the Trusts window, and then selecting New Trust on the context menu.
In the Add Trust Wizard, complete the following steps:
1. Specify a trust name.
2. Enable the PI-API Application option.
3. Specify either or both the computer name of the client or the name of the application running on the client.
  By using the Application Name and Client Connection options, you can set up a trust relationship for one or more application running on a specified client, for all applications running on the client, or for a specified application running on any client.
  
  To use the Application Name option, specify up to the first eight characters of the client application's executable file name. For example: specify PREDICTP instead of PREDICTPRO.EXE for the PredictPro client application; specify PREDICT. instead of PREDICT.EXE for the Predict client application; specify CHS.EXE for the Process History View client application.
  
  To use the Client Connection option, it is recommended that you specify one or both of the following:
  
  Network Path, specifying the computer name of the client
  or
  
  IP Address and NetMask for Trust #1, specifying 10.4.x.x as the IP address of the DeltaV primary network and 255.255.0.0 as the network mask and IP Address and NetMask for Trust #2, specifying 10.8.x.x as the IP address of an existing DeltaV secondary network and 255.255.0.0 as the network mask
  Note
  If you do not specify the computer name of the client in Network Path, the trust using 10.4.x.x as the IP address of the DeltaV primary network only takes effect if the connection to the 10.8.x.x IP address of an existing DeltaV secondary network is unavailable.
4. Specify piadmins as the PI User.