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

UniInt Failover Configuration
78
Configuring Synchronization through a Shared File (Phase 2)
Step Description
1. Verify non-failover interface operation as described in the Installation Checklist section of
this manual
2. Configure the Shared File
Choose a location for the shared file. The file can reside on one of the interface nodes but
Rockwell Automation strongly recommends that you put the file on a dedicated file server
that has no other role in data collection.
Setup a file share and make sure to assign the permissions so that both Primary and
Backup interfaces have read/write access to the file.
3. Configure the interface parameters
Use the Failover section of the Interface Configuration Utility (ICU) to enable failover and
create two parameters for each interface: (1) a Failover ID number for the interface; and
(2) the Failover ID number for its backup interface.
The Failover ID for each interface must be unique and each interface must know the
Failover ID of its backup interface.
If the interface can perform using either Phase 1 or Phase 2 pick the Phase 2 radio button
in the ICU.
Select the synchronization File Path and File to use for Failover.
Select the type of failover required (Cold, Warm, Hot). The choice depends on what types
of failover the interface supports.
Ensure that the user name assigned in the “Log on as:” parameter in the Service section
of the ICU is a user that has read/write access to the folder where the shared file will
reside.
All other command line parameters for the primary and secondary interfaces must be
identical.
If you use a Historian Collective, you must point the primary and secondary interfaces to
different members of the collective by setting the SDK Member under the PI Host
Information section of the ICU.
[Option] Set the update rate for the heartbeat point if you need a value other than the
default of 5000 milliseconds.
4. Configure the Historian tags
Configure five Historian tags for the interface: the Active ID, Heartbeat 1, Heartbeat2,
Device Status 1 and Device Status 2. You can also configure two state tags for monitoring
the status of the interfaces.
Do not confuse the failover Device status tags with the UniInt Health Device Status tags.
The information in the two tags is similar, but the failover device status tags are integer
values and the health device status tags are string values.
Tag ExDesc digitalset
UniInt does not
examine the
remaining attributes,
but the PointSource
and Location1 must
match
ActiveID [UFO2_ACTIVEID]
IF1_Heartbeat
(IF-Node1)
[UFO2_HEARTBEAT:#]
IF2_Heartbeat
(IF-Node2)
[UFO2_HEARTBEAT:#]
IF1_DeviceStatus
(IF-Node1)
[UFO2_DEVICESTAT:#]
IF2_DeviceStatus
(IF-Node2)
[UFO2_DEVICESTAT:#]
IF1_State
(IF-Node1)
[UFO2_STATE:#] IF_State
IF2_State
(IF-Node2)
[UFO2_STATE:#] IF_State