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

Principles of Operation
22
Historian to Historian is used to transfer data within a collective when the data cannot be sent
directly from the interface node. The following section describes typical configuration and
deployment scenarios when running Historian to Historian within a collective.
Tag Attribute Override Parameters
The interface supports tag attribute override parameters. These startup parameters must be
used when running the interface within a collective. Tag attribute override parameters enable
the interface to collect data for tags that are not actually configured for the Historian to
Historian interface.
Each member of a collective is required to have identical Historian point database definitions.
Using Historian to Historian within a collective will result in the need to have a tag
configured for Historian to Historian on one collective member but these same tags must also
be configured for the native data source interface on a different collective member.
For example, consider a secondary Historian Collective node that sits behind a firewall. The
primary Historian Collective node receives data directly from a Historian OPC and a
Historian ModBus interface node. The points on the secondary Historian Collective node are
defined exactly as they are on the primary Historian Collective node. This means these points
are either configured for the Historian OPC or the Historian ModBus interface