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

UniInt Failover Configuration
76
Quick Overview
The Quick Overview below may be used to configure this Interface for failover. The failover
configuration requires the two copies of the interface participating in failover be installed on
different nodes. Users should verify non-failover interface operation as discussed in the
Installation Checklist section of this manual prior to configuring the interface for failover
operations. If you are not familiar with UniInt failover configuration, return to this section
after reading the rest of the
UniInt Failover Configuration section in detail. If a failure occurs
at any step below, correct the error and start again at the beginning of step 6 Test in the table
below. For the discussion below, the first copy of the interface configured and tested will be
considered the primary interface and the second copy of the interface configured will be the
backup interface.
Configuration

One Data Source

Two Interfaces
Prerequisites

Interface 1 is the Primary interface for collection of FactoryTalk Historian data from
the data source.

Interface 2 is the Backup interface for collection of FactoryTalk Historian data from
the data source.

You must set up a shared file.

Phase 2: The shared file must store data for five failover tags: (1) Active ID,
(2) Heartbeat 1, (3) Heartbeat 2, (4) Device Status 1 and (5) Device Status 2.

Each interface must be configured with two required failover command line
parameters: (1) its FailoverID number ( /UFO_ID ); (2) the FailoverID number of its
Backup interface ( /UFO_OtherID ). You must also specify the name of the Historian
Server host for exceptions and Historian tag updates.

All other configuration parameters for the two interfaces must be identical.