Rockwell Automation FactoryTalk Historian SE 3.0 UniInt Interface User Guide - Manual (Page 71)

UniInt Interface User Manual 65
Server becomes disconnected for any reason, point synchronization will be restarted upon
reconnection to the Historian Server.
The ―Messages‖ section of this document contains a listing of typical messages sent to the
pipc.log file during the synchronization mode
Remote Cache Builds
Users have the option of building the cache files necessary for disconnected startup on a
remote machine. This feature is useful if the destination machine has limited network
connectivity with the Historian Server or if identical interface configuration will be deployed
as in a failover configuration using the same host Historian Server. For example, if the
interface node is running on a remote off-shore oil platform using a network connection with
limited throughput, the cache files may be built on an interface node or even the Historian
Server located at the corporate headquarters. The files may then be transferred to the remote
site as desired. The cache files built on the remote machine must be validated by the
destination interface node. To validate remotely created cache files, the interface startup
command file (.bat file) used in creating the remote cache files must contain identical entries
for the parameters necessary for the disconnected startup configuration in the startup
command file to be used on the destination interface node. The following is a list of
requirements necessary to successfully build caching files on a remote machine.

The interface must be built against UniInt version 4.3.0.x or later.

The interface node or Historian Server must have PI API version 1.6.1.x or later
installed.

The PI SDK must not be utilized to retrieve the extended point attributes from the
Historian Server.

The following entries on the startup command file must be identical on both the
remote and destination nodes. The entries are not case sensitive.
o The interface executable name.
o The host Historian Server name. Use the actual host Historian Server name
or IP Address. Do not use /host=localhost.
o The /ps parameter.
o The /id parameter.
o The /cachemode parameter must be defined.