Manufacturing: Factory Publication pattern

The Manufacturing: Factory Publication pattern generates an application that takes information from an OPC-UA or PI Server and retransmits this information over a selected transport for use in another application.

Image showing the Manufacturing: Factory Publication pattern solution. Data from an OPC-UA Server or a PI Server is read by the Manufacturing: Factory Publication pattern in IBM Integration Bus. In the pattern, an output stream is created to a destination application. The output stream is either MQ, MQTT, FILE, or MFT format.

Solution

An increasing number of scenarios exist where applications need access to the kind of data that is used in factory level systems. OPC-UA Servers and PI Servers are examples of these and this pattern accelerates development of applications that interact with these systems.

Through pattern parameters, the generated application supports the retransmission of OPC-UA and PI data over a selection of transports. In all cases, customization options are provided in the form of a custom map that can be modified after pattern creation to change the format of the output data.

The following output transports are supported:

MQTT output

Every message that is received by the OPC-UA or PI input nodes in the generated application is published on a chosen topic to the chosen MQTT Server.

MQ output

Every message that is received by the OPC-UA or PI input nodes in the generated application is placed on a specified WebSphere MQ queue.

File - Real-time output

Every message that is received by the OPC-UA or PI input nodes in the generated application generates a single file in the specified output directory. These files are time stamped and any attempt to write to a file that already exists results in an exception being thrown in the flow.

File - Batched output

Every message that is received by the OPC-UA or PI input nodes in the generated application is treated as a record in the specified output file in the specified output directory. During pattern creation, the user is asked how many records to place in the output file before the file is completed. If the file that is being written already exists, the existing file is archived by using a time stamp.

MFT - Real-time output

Every message that is received by the OPC-UA or PI input nodes in the generated application generates a single file in the specified output directory by using MFT. These files are time stamped and any attempt to write to a file that already exists results in that file being overwritten.

MFT - Batched output

Every message that is received by the OPC-UA or PI input nodes in the generated application is treated as a record in the specified output file in the specified output directory by using MFT. During pattern creation, the user is asked how many records to place in the output file before the file is completed. The user is also asked whether the file, if it already exists, should be overwritten.

If this option is selected during pattern creation, any of the listed solutions support the logging of every emitted message to an MQ queue.

Related tasks

Parameters for the pattern
Tasks to complete after generating the pattern