Skip to content

Enterprise Integration#

Enterprise Integration provides you with an extensible way to integrate the MES solution with external systems. It promotes the adoption of best practices in the area of system integration and provides facilities that allow a low-code mechanism that can be used with configuration only, or minimal code.

You will need to:

  1. Create an IoT Event Definition of Scope Enterprise Integration, and add some properties, for example, Site Name and Site Description.

Screenshot showing an IoT Event Definition creation form with fields for Enterprise Integration properties.

  1. Create an Automation Controller of Scope Enterprise Integration and add to it the IoT Event Definition that was just created. In the Workflow view, the Job Start task should include 2 outputs: Site Name and Site Description (it inherits them from the IoT Event Definition).

Screenshot showing a new Automation Controller creation form with fields for name and description.

  1. Create an entry in the IntegrationHandlerResolution smart table with the mandatory values and the Message Type (value from the MessageType lookup table) and the IoT Event Definition that was just created.

Screenshot showing a UI with fields for adding an integration handler, including Message Type from the MessageType lookup table.

  1. Create an IntegrationEntry with the properties matching the entry that was just created in the IntegrationHandlerResolution smart table and an IntegrationEntryMessage (a JSON payload matching the properties of the IoT Event Definition - Site Name and Site Description).

When the IntegrationEntry is picked up for execution, the IoT Event Definition will be resolved from the IntegrationHandlerResolution smart table. The API Post Event is called with the resolved IoT Event Definition and the JSON defined in the IntegrationEntryMessage.

The Workflow defined in the Automation Controller will be executed by the Automation Manager process. The values defined in the IntegrationEntryMessage JSON will be available as outputs on the JobStart task. Therefore, other tasks can use that information to do whatever you defined in the Workflow.

Screenshot showing a workflow diagram for an automation controller.