Prerquisites and Example Setup

This example illustrates the history transfer from an existing Source Historian through a "Transferring" inmation system to a Target Historian which is represented by another inmation system. So besides the Source Historian two other (virtual) host machines are needed. This document addresses the

One will run the inmation system which executes the history transfer while the other will act as the Target Historian, receiving the transferred data.

The Source Historian

To bring the historical data from the Source Historian into the system a Connector instance is needed, either running on the same machine as the Source Historian itself or on a local machine along with a suitable client for the historian, e.g. the OSI PI AF Client.
Information on the OSI PI Asset Framework and installation of the OSI PI AF Client can be found on the OSIsoft website.

For the connection to the OSI PI system historian or the Uniformance PHD Server the fitting Bridge Interface should be used, therefore the adequate Bridge service needs to be installed on the aforementioned Connector instance. The installation of the Bridge services is described in detail on dedicated pages for the inmationPIBridge (for the OSI PI system historian) and the PHDBridge (for the Uniformance PHD Server).

For this example we will be using an OSI PI system historian as Source Historian.

The Target Historian

For the "Target Historian" inmation system with at least the Core and a Connector component as well as a running MongoDB need to be installed. But for simplicity’s sake a full installation of the system (including all components) will also work.

Another instance of the Connector component needs to be installed using the Node Installer Setup which will be the egress connector of the Transferring system.

Adding an MQTT Broker Service

As we will be using MQTT to make the data available to the target historian, an MQTT Broker needs to be installed on the Target Historian machine. The documentation page on Preparing the Sample MQTT Broker provides detailed information.

Creating an MQTT DataSource Object

 

On the Target Historian machine, in DataStudio …​

1 Right-click on the local Connector object and select Admin  New  External Interfaces  Datasource

2 In the Create Object Wizard, provide an Object Name.

3 Then click Next > to move on to the Server Type section of the wizard.

4 From the drop-down list, select Mqtt.

5 Add a new Subscription Data sub-compound by clicking on the + icon.

6 Enter a Subscriber Name. For this example, use History Transfer Subscriber.

7 Expand the Subscription Data property compound and for the Topic property enter "#". This MQTT wildcard subscribes to all incoming MQTT topics.

8 Click Create to close the wizard and create the Datasource object in the I/O Model.

The Transferring System

On the machine designated as the Transferring system an inmation system needs to be installed, the Core being the only required component. But a full installation of the system will also work.

1 For the Connector instance on the Source Historian machine, create a new Connector object on the "Transferring" machine, using the IP address of the Source Historian and port of the Connector instance.

2 Create another Connector object - this time for the connector component installed on the Target Historian machine, providing the IP address for this machine and the port settings for the Connector component installed there.

Continue Reading

The next page addresses the Creation of a Generic Time Series Buffer object which is needed by the History Transport Manager object.