Configure AVEVA Events to CONNECT for MES Curation

AVEVA Events to CONNECT is the event data-collection agent that collects JSON data from MES Curator Web API endpoints and transfers them to Type store, Assets, and Graph API endpoints in CONNECT data services.

The MES Cloud integration Events to CONNECT component settings in the post-install Configurator enable you to configure the event data to publish to AVEVA CONNECT. The General, Data Ingress, Data Egress, and (Optional) Health tabs need to be populated to successfully configure the AVEVA Events to CONNECT agent.

Note: To access Events to CONNECT for MES Curation, a licensed version of MES Middleware MES Curation Services component must be installed and configured.

For general information about configuring the AVEVA Events to CONNECT agent, refer to the AVEVA Events to CONNECT online help (https://docs.aveva.com).

To configure AVEVA Events to CONNECT for MES Curation

1. Complete each of the following:

   • Import MES Curator Data Ingress endpoint configurations and create MES Events to CONNECT Component Ids using the General tab. See, Understand Data Ingress and System Component settings.

   • Configure CONNECT data services endpoints accepting event messages using the Data Egress tab. See, Configure Events to CONNECT Data Egress settings.

   • (Optional) Configure the agent endpoints for health information using the Health settings tab. For detailed instructions, refer to the AVEVA Events to CONNECT online help.

2. Select Configure to set up the publication of MES Events to CONNECT.

   Progress information and any errors, if they occur, appear in the Configurator's Configuration Messages window. If the configuration completes successfully, a success message appears in the Configuration Messages window. Also, the MES Curation Services status indicator changes to a green check mark. If errors are encountered, check the Operations Control Management Console (OCMC) Log Viewer for details. To view additional details, enable the Log Script Execution log flag in the log viewer.

   Important: Once configured, the data ingress status is stopped and the agent must be manually started to begin listening by default. For detailed instructions, refer to the AVEVA Events to CONNECT online help (https://docs.aveva.com).