Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Manufacturing Execution System 2023 R2

TABLE OF CONTENTS

Configure the data ingress data source settings

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedMay 15, 2025
  • 4 minute read

Configure the MES Curation Service Data Source settings using the properties in the Data Ingress Data Source tab.

The post-install configurator Events to CONNECT displaying default MES settings.

Before you begin

The values used to set up the MES Curation Services AVEVA Identity Manager component are used to configure the Events to CONNECT Data Ingress Data Source properties. To view the MES Curation Services component settings:

  1. Open the System Management Console and navigate to the MES. Curator.Host component in the log viewer.

    System Management Console showing how to select the MES Curator Host component in the log viewer.

  2. Find the Program Start-URLSetup entry and double-click it to open the Message Details window.

    The MES Curation Service values for Token Endpoint, Client Id, Token Audience, and MES Curator HTTPS Port are displayed.

    System Management Console MES Curator Host component Program Start URL Setup log message details.

  3. Use the displayed values to update the Data Ingress Data Source settings.

    Important: The Client Secret created during the MES Curation Services component configuration must be used to configure the Data Ingress Data Source Client Secret. The Client Secret is not saved with the other component settings.

Update the Data Ingress Data Source settings

  1. Select the Data Source tab.

  2. In the Endpoint field, enter the endpoint of the MES Curator Host service.

    The endpoint must be entered as an HTTPS string ending with '/'. For example, https://On-premiseRestAPIHost:Port/mescurator/.

    For MES this is: https://[fully qualified machine name]/mescurator/.

  3. In the Health Controller field, enter the controller’s name of the MES Curator Host Rest API endpoint used to check the health of the on-premises application.

    For MES, the value of 'curatelog/health' should not be changed. For more information on the Health Check controller, refer to the AVEVA Events to CONNECT Help - Health Check Controller.

  4. In the Failed Requests Controller field, enter the controller’s name of the MES Curator Host Rest API endpoint to send the error response for failed requests to CONNECT data services.

    For MES, the value of 'error' should not be changed. For more information on the Failed Requests controller, refer to the AVEVA Events to CONNECT Help - Failed Requests Controller.

  5. Set up a secure connection using a bearer token obtained from client credential authentication security by doing the following:

    • Enter the Auth0 or OIDC provider's unique client identifier in the Client ID field.

      For MES, this is {machine name}.MESCURATOR from the MES Curation Services AIM configuration.

    • Enter the Auth0 or OIDC provider's password in the Client Secret field.

      For MES, this is the user entered value from the MES Curation Services AIM configuration.

  6. In the Token Endpoint field, enter the Auth0 or OIDC provider's token endpoint for the MES Curator Host REST API.

    The endpoint must be entered as an HTTPS string without an ending '/'. For MES, this is the AIM token endpoint 'https://[AIM Machine fully qualified name]/identitymanager/connect/token'.

  7. In the Token Audience field, enter the Auth0 or OIDC provider's token audience used to authenticate access to the MES Curator Host REST API.

    For MES, the AIM token audience is 'system' and should not be changed.

  8. (Optional) Update the Data Source Default parameters using the following settings:

    1. Select Validate Certificate to enable Events to CONNECT to validate the certificate of the on-premises REST API endpoint.

      Note: AVEVA strongly recommends only disabling server certificate validation for testing purposes.

    2. In the Request Interval field, enter the frequency that the Events to CONNECT agent requests information from the MES Curator Host.

    3. Select UTC to use UTC for date times.

    4. In the Data Collection field, select the data collection mode for Events to CONNECT. Choose from the following modes:

      • History Only: The Events to CONNECT component is not started and on-demand history recovery is enabled. For more information on history recovery, see Configure the data ingress history recovery settings.

      • Current Only: The Events to CONNECT component operates normally and on-demand history recovery is disabled.

      • Current with backfill: (default) The Events to CONNECT component operates normally, but disconnections are recorded based on device status. History recovery backfills up to 5 days of data once device status is good. On-demand history recovery is disabled.

      Note: If the data collection mode is updated, you must restart the Data Ingress Component.

    5. If Current with backfill is selected, select Backfill Historical Data to enable AVEVA Events to CONNECT to backfill historical data from the Backfill Start Date Time.

    6. If Backfill Historical Data is enabled, enter an date time (UTC) interval in the Backfill Start Date Time field for AVEVA Events to CONNECT to retrieve historical data.

      The interval can be a maximum of 4 days in the past.

  9. Select Validate to verify the Data Source settings.

  10. Select Configure to configure the Data Ingress Data Source settings and update the MES Curator Events to CONNECT JSON file.

    TitleResults for “How to create a CRG?”Also Available in