Enabling Non-AVEVA Client Applications to make MES Stateless API Calls

Note: Starting with MES version 23.1 asynchronous and event broker communications between the MES middleware and client components are encrypted.

To enable non-AVEVA client applications to make MES Stateless API calls

1. Shut down the non-AVEVA client application.
2. Ensure that the MES Middleware Proxy feature is installed.
3. Configure the System Management Server component with the correct values.
   For more information, refer to Implementing Secure Communication with the System Management Server in the MES Installation Guide.
4. Configure the MES Middleware Proxy component with the available MES Middleware Server nodes.
   For more information, refer to Configuring the MES Middleware Proxy Component in the MES Installation Guide.
5. Start the non-AVEVA client application.

Note: When the default self-signed certificate for System Management Server is used, make sure to configure the MES middleware proxy on the client node after the System Management Server is reconfigured. This step will make sure the correct certificate is reinstalled on the client node which is required for establishing a secure client/server communication.

Important: When the certificate on the client/server is out of sync, it may cause the synchronous, asynchronous, and event broker messages to not authenticate properly and function incorrectly. If this occurs messages may be lost and loss of data will result.