UniInt End User
Download 1.93 Mb.
|
PI BASemAPI
Remote Cache BuildsUsers 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 PI Server or if identical interface configuration will be deployed as in a failover configuration using the same host PI 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 PI 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 PI 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 PI Server. The PI Server must be version 3.x or later. The following entries on the startup command file must be identical on both the remote and destination nodes. The entries are not case sensitive. The interface executable name. The host PI Server name. Use the actual host PI Server name or IP Address. Do not use /host=localhost. The /ps parameter. The /id parameter. The /cachemode parameter must be defined. Download 1.93 Mb. Share with your friends:
|