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

FactoryTalk Historian To Historian Interface User Guide 31
Chapter 4.
Interface Installation
Rockwell Automation recommends that interfaces be installed on interface nodes instead of
directly on the Historian Server node. An interface node is any node other than the Historian
Server node where the FactoryTalk Historian application Programming Interface (PI API) has
been installed (see the PI API manual). With this approach, the Historian Server need not
compete with interfaces for the machine‟s resources. The primary function of the Historian
Server is to archive data and to service clients that request data.
After the interface has been installed and tested, Buffering should be enabled on the interface
node. Buffering refers to either PI API Buffer Server (Bufserv) or the PI Buffer Subsystem
(PIBufss). For more information about Buffering see the
Buffering section of this manual.
In most cases, interfaces on interface nodes should be installed as automatic services.
Services keep running after the user logs off. Automatic services automatically restart when
the computer is restarted, which is useful in the event of a power failure.
The guidelines are different if an interface is installed on the Historian Server node. In this
case, the typical procedure is to install the Historian Server as an automatic service and install
the interface as an automatic service that depends on the PI Update Manager and PI Network
Manager services. This typical scenario assumes that Buffering is not enabled on the
Historian Server node. Bufserv can be enabled on the Historian Server node so that interfaces
on the Historian Server node do not need to be started and stopped in conjunction with
Historian, but it is not standard practice to enable buffering on the Historian Server node. The
Buffer Subsystem can also be installed on the Historian Server. See the UniInt Interface User
Manual for special procedural information.
Naming Conventions and Requirements
In the installation procedure below, it is assumed that the name of the interface executable is
PItoPI.exe and that the startup command file is called PItoPI.bat .
When Configuring the interface Manually
It is customary for the user to rename the executable and the startup command file when
multiple copies of the interface are run. For example,
PItoPI1.exe and PItoPI1.bat
would typically be used for interface number 1, PItoPI2.exe and PItoPI2.bat for
interface number 2, and so on. When an interface is run as a service, the executable and the
command file must have the same root name because the service looks for its command-line
parameters in a file that has the same root name.