3.15.3.8. Tunnel (Pull)

From the Edit Historian Connection window you can select Tunnel (Pull).

The Tunnel (Pull) historian type allows you to configure the DataHub instance as a tunnel slave to pull data from a remote external historian and log it to a local historian, by connecting to a DataHub tunnel master running on the remote machine. Please see External Historian 5 - Tunnel (Pull) for more details.

Connection Settings

Label

A unique text string used to identify this connection. This label is used to identify the connection when configuring store and forward, and to create the database name or retention policy in some historians. The label can contain only letters, numbers and the underscore ( _ ) character.

Tunnel connection name

The connection name of the tunnel you have configured to pull data from the remote DataHub instance. See Tunnel/Mirror in the Receiving Side section of the tutorial for more information. See the Tunnel (Pull) tutorial for more information.

Remote historian label

The Label configured for the historian on the remote side.

Accumulation time (ms)

The number of milliseconds that the sending DataHub instance will buffer data in memory before it gets pulled across the tunnel. Leaving this field blank means that no accumulation time will be enforced. If both this value and Maximum # of buffered values (below) are specified, then the DataHub instance will pull all buffered values across the tunnel whenever the first of these two limits is reached.

Maximum # of buffered values

The maximum number of values that the sending DataHub instance will buffer in memory before it gets pulled across the tunnel. Leaving this field blank means that no values will be buffered.

Log writes at information level

Checking this option causes messages regarding successful writes to the database to be logged at the Information level in the DataHub Event Log. If this is not checked then these messages are logged at the Debug level and are therefore normally hidden from the user.

Remote System

Remote forwarding strategy

The label of a forwarding strategy from the External Historian configuration of the DataHub instance on the sending side.

Unique forwarding client ID

A text string unique to this forwarding configuration that allows the historian to identify it. You can use the system-generated string, or enter your own.

Override read location

Allows you to forward a portion of the data set by resetting the start point to a more recent time. The date/time data format is YYYY-MM-DD HH:MM:SS, and can be edited as needed. The calendar button allows you to quickly enter the date.

Once you have completed the Tunnel (Pull)-specific configuration, you can return to Picking Points in General Configuration to continue.