The Flex SCADA historian requires a new JMS Queue, scada-hist-queue. See WebLogic Configuration in this section for details on the JMS Queue.

In order to connect to an OSI PI historian PI's CA Certificate must be imported into the WebLogic servers truststore.

The certificate can be obtained by browsing to the PI Web API. For example:

The location of the weblogic truststore can be found by logging into the WebLogic console and selecting Servers -> <Managed Server> -> Security -> Custom Trust Key Store File Name. If it is not configured, then WebLogic will use the default Java truststore.

To import the certificate use the keytool command:

 

In order to connect to the PI Server the PI credentials must be stored. The location of the credentials can be configured in a CES Parameter nms.credentials for the app SCADA. For example:

 

The location must exist somewhere on the WebLogic server and the configuration file must take the following format:

 

The password can be stored in plain text or encrypted using the WebLogic encryption service, weblogic.security.Encrypt. The file must exist on each WebLogic instance in the cluster and the password must be encrypted using each instances encryption service.

 

The following SRS Rules must be configured when using the PI Historian.

Historian Delete Points: This rule controls whether a tag is deleted from the historian when the SCADA measurement is no longer configured to report to the historian. If true, all data for the SCADA measurement will be removed.

Historian Guaranteed Delivery: This rule controls where changes in value for SCADA measurements will have guaranteed delivery. If false, the system will discard any changes while the system is disconnected from the historian. If true, the system will store all changes until the connection with the historian is reestablished and then report the changes to the historian.

Historian PI Interface Enabled: This rule must be set to "yes" to enable the OIS PI Historian support in NMS.

Historian PI Maximum Changes: This controls the maximum number of SCADA measurement changes that can be sent to PI in one message. The default value is 5000 and the limit is defined by the maximum size of an http request to PI (defaults to 4MB which equates to roughly 30,000 changes). The size of the http request can be configured in PI using the parameter MaxRequestContentLength.

Historian PI Retry Batch Size for Changes: This controls the maximum number of SCADA measurement changes that will be sent to PI when retrying stored changes that failed to be sent the first time when the system is using guaranteed delivery. By default, the value is 500. The limit is defined by PI's client rate per IP limit calculated as

Rate limit per second per IP = RateLimitMaxRequests/RateLimitDuration

By default, the value is 1000.

 

Historian PI Retry Batch Size for Messages: This is similar to the Historian PI Retry Batch Size for Messages but for messages that create, update, or delete tags in the PI historian. The default value is 500.

Historian PI Tag Naming Rule: This rule allows the administrator to control the format of the Tag Name of a point in PI for a SCADA measurement.

Historian PI Tag Quality Naming Rule: Like the Historian Pi Tag Naming Rule, this allows the format of the Tag Name for the SCADA Measurements SCADA Quality to be configured. By default, this rule does not exist and the SCADA Quality is not stored in PI as a separate tag. Creating and configuring this rule will allow the SCADA quality to be stored in PI in a separate tag from its value.