Configurations for multiple data sources

PI System Connector supports multiple data sources with unique settings. However, the Global Settings found in the data source configuration are applied to all data sources so that all data source uses the same global settings. The global settings are applied to all data sources configured for this instance of PI System Connector upon restart of data collection.

Data source configuration settings are managed through the PI System Connector Administration window, which provides Data Sources Details.

Note: If you have been running PI System Connector and open the PI System Connector Administration window to configure a data source, you may find that the fields populated with details from the previous data source are grayed out. Click Back to Settings under Data Source Settings to open the Global Settings window to change data source configuration settings.

Under Global Settings, configure the following fields:

• History Recovery Start Time

• All Discovery Scan Rate (Seconds)

• PI Point Discovery Scan Rate (seconds)

• Prefix PI Points, Digital State Sets, and Pointsources on destination Data Archive

• Send snapshot data for PI Points that match this query

• Replicate using Append and Delete write behaviors

Every data source configured for this instance will send data to the destination database that is configured for the relay.

Refer to Data source configuration reference.

Note: Users with multiple data sources associated with more than one database may wish to see two databases showing on the destination server. This is not possible with the current version of the relay architecture. The source database, or source AF element for each data source, is sent to the relay (exported) and added to the same destination database, as well as the same root element path on the relay. If there is a conflict between any of these items -- for instance, DataBase1 and DataBase2 both have an element "A" -- the settings for the last item imported to the destination are used. If there was a sub-element in the earlier arriving database, this results in data for that element not being sent to the destination server. The only way, in a multi-source system, to manage which database settings are imported first is to avoid conflicts through the structure of the AF hierarchy.

Tip: It is advisable to organize the asset structure of the data source under a single element. This guarantees that there will not be collisions resulting from the element structure, which otherwise might result in data loss. Multiple child elements could have the same name if they are organized under a unique parent name.