Rockwell Automation FactoryTalk Historian SE 3.0 H2H Interface User Guide - Manual (Page 106)

Security
100
Security Configuring using Trust Editor
The Trust Editor plug-in for System Management Tools 3.x may also be used to edit the Trust
table.
See the System Management chapter in the Historian Server manual for more details on
security configuration.
Historian Server v3.2
For Historian Server v3.2, the following example demonstrates how to edit the Historian
Proxy table:
C:\PI\adm> piconfig
@table pi_gen,piproxy
@mode create
@istr host,proxyaccount
piapimachine,piadmin
@quit
In place of piapimachine , put the name of the interface node as it is seen by Historian
Server.
Tag and Node Security
The receiving Historian Server must allow the interface tag attribute read access and data
read and write access. The source Historian Server must allow the interface tag attribute read
access and data read access for source tags.
System Manager Responsibilities
Securing the source archive data requires that both the source and receiving system managers
perform the following tasks.
Receiving System Manager
1. Give the source system manager a copy of the FactoryTalk Historian to Historian
Interface manual.
2. Edit the PItoPI.ini file and add the keys SecurityFile, SourceLogin, SourcePassword
under the section [PITOPI-#] where “#” is the interface identification number. The
three security keys may be listed under a particular scan class if the scan is retrieving
data from a PI 2 server different from the default source server (use section name
[PITOPI-#.*] where “*” is the scan class number).
Alternately, edit the startup script to contain the parameters /ln=pidemo /pw=pidemo
replacing pidemo with the PI user name and password under which the data will be
accessed. Set the name of the security file: for example /sf=test.