The IBM Integration Bus (IIB) Manufacturing Pack builds on IBM Integration Bus to provide support for applications in the manufacturing industry. One such feature is OSIsoft PI connectivity which allows users to integrate their industry data sources with IIB applications by using an OSIsoft PI server.
The IIB Manufacturing Pack provides OSIsoft PI client nodes that receive and process data from OSIsoft PI Servers. Sensors deployed in data sources collect data and send it to a PI Server. The PI Server then sends the data that you specify to a PI client. This data can be consumed by using IIB applications using the PI Input or PI Read Node.
In this article we learn how IBM Integration Bus Manufacturing Pack PI Nodes can be configured to connect to remote PI Supervisory control and data acquisition (SCADA) systems to fetch real-time data generated at remote sites.
PI-Input node
The PI-Input node is used to receive event notifications from a PI server. The event notifications generated by the PI-Input node is for a list of tags specified in the Basic tab of the node properties. It is also possible to provide a wildcard entry for the tags, illustrated in the next section.
Configuration
In order to use the PI-Input node in a message flow, it is required to install a supported version of the PI Asset Framework (AF) SDK utility. (see Tips for a Successful Deployment #2)
Before establishing the connection between IIB and the PI server, make sure your PI SDK utility can contact the PI server. This can be verified by accessing the PI System Explorer Client and navigating to (File > Connections and checking that the desired PI server is running/in a connected state).
It is mandatory to authenticate your integration server so that it can successfully connect to the PI server. This is done by using the PI SMT (System Management Tool). Access the PI SMT and navigate to the tab Security > Mappings and Trusts > Trusts. Now add an entry for DataFlowEngine.exe file as shown below.
While configuring a trust for DataFlowEngine.exe, you will need to provide additional information such as;
• Computer name/Full computer name
• Domain
• IP address
• Subnet Mask
• User ID
• Application Name
• Remote PI Server name/connection details
Node configuration
• PI connection – Provide a valid connection name mentioned in the PI AF SDK utility.
• Tags – The names of the tags that contain the data that you want to receive. You can specify multiple tags by using a comma separated list of values.
It is also possible to specify a wildcard entry for a tag. In such as case, the user receives entries for all matching tags that have been refreshed since the last message was emitted out. You can use an asterisk (*) to replace any number of characters or use a question mark (?) to replace one character in the tag name. If you wish to receive notifications for all tags present in the PI server, you should provide a * (symbolizing all tags on the server).
Ensure the integration node is allowed to run in the ‘manufacturing’ mode by using the mqsimode command.
For more details on how to configure an integration node for use with the IIB Manufacturing Pack, access the IBM Knowledge Center at
https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.manufacturing.doc/ma00094.htm
PI-Read node
The PI-Read node is used to read historical data for specified tags from a PI server. However, the data received from this node will be the most recent data/values associated with the specified tag(s). The tag data generated by the PI-Read node is for a list of tags specified in the Basic tab of the node properties. It is not possible to provide a wildcard entry for the required tags.
Configuration
In order to use the PI-Read node in a message flow, it is required to install a supported version of the PI SDK utility. It is mandatory to provide the necessary rights to your integration server so that it is able to contact the PI server. This is done by following the steps explained in the previous section.
Node configuration
• PI connection – Provide a valid connection name mentioned in the PI SDK utility.
• Tags – The names of the tags that contain the data that you want to receive. You can specify multiple tags by using a comma separated list of values, as shown below.
Tips for a successful deployment
1. The PI AF SDK utility contains PI SDK. Hence, if you setup a PI AF SDK utility, both PI nodes should be able to connect to it.
2. Use the exact same version of the PI AF SDK/PI SDK documented in the Integration Bus requirements.
For Windows:-
Software Product Compatibility Reports
For other supported operating systems, follow the master link at:-
System Requirements for IBM Integration Bus Manufacturing Pack 1.0
3. If you run into an exception as below:-
A ”System.Runtime.InteropServices.COMException” was thrown from the .NET AppDomain ”ReadPIData” to the broker from the source ”Manufacturing Nodes” with the message ”Retrieving the COM class factory for component with CLSID {4BCB2EG5-5H66-11D1-AN34-0060H0690109} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).”.
Solution- You need to review and register the above CSLID 4BCB2EG5-5H66-11D1-AN34-0060H0690109 with Windows operating system.
Reference
Read about the IBM Integration Bus Manufacturing Pack overview at:-
https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.manufacturing.doc/ma00010.htm
Troubleshooting and support information can be found at:-
https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.manufacturing.doc/ma00200.htm