Configure the MES middleware proxy

You can access a MES middleware server from remote nodes on which MES client products or components are running by configuring the MES middleware proxy on the remote nodes.

• You must install the MES middleware proxy on all remote nodes on which OCOs, UCOs, or SROs are configured (e.g., using System Platform Object Editor or through GR‑Access) or deployed to run. For high‑transaction MES objects, it is recommended that a full MES Middleware component be installed on the node hosting MES objects.

• You must install the MES middleware proxy on all remote nodes making MES stateless or stateful API calls even when used in a custom application.

• If you are configuring the MES middleware proxy on a node, make sure that you have installed, configured, and started the MES middleware service on the remote server before configuring the MES middleware proxy.

• In a multi‑node system that has multiple MES middleware servers installed, each middleware server can be configured for the proxy to use. This allows the proxy to move communications to another middleware server if its current middleware server stops running. If this occurs, the proxy will attempt to connect to the next middleware server according to their order in the list.

The Middleware Proxy and AVEVA Identity Manager (AIM) tabs must be completed to successfully configure the Middleware Proxy component.

Configure the MES Middleware Proxy component

1. Complete each of the following:

   • Configure each middleware host to which to connect the proxy. See, Configure the MES middleware proxy settings.

   • Configure the AIM client registration information for the middleware proxy. See, Configure the MES middleware proxy AIM client registration.

2. Select Configure.

   If the middleware proxy can communicate with a middleware service successfully, a success message appears in the Configuration Messages box.

   If the proxy could not successfully communicate with a middleware service, a failure message appears in the message box.

   The MES Middleware Proxy component configuration status changes according to the following conditions:

   • If the proxy was able to successfully communicate with all of the middleware servers, the indicator changes to .

     Client applications on the node can now communicate with any of the middleware servers.

   • If communication failed with one or more middleware servers but succeeded with at least one, the indicator changes to .

     Client applications on the node can now communicate with any of the middleware servers for which communication succeeded.

   • If communication failed with all of the middleware servers, the proxy component configuration fails and the indicator changes to .

     Communication with at least one of the middleware servers will have to be established before client applications on the node can use the MES proxy.

Reconfiguring the middleware proxy if the System Management Server or MES middleware HTTPS port number Is changed

• If the System Management Server and MES middleware are on the same node and the HTTPS Port number is changed, change the proxy HTTPS Port number to match it and reconfigure the Middleware Proxy component. See Configure the MES middleware proxy settings.

• If the System Management Server and MES middleware are not on the same node and the common platform HTTPS Port number for the MES middleware node is changed, change the proxy HTTPS Port number to match it and reconfigure the Middleware Proxy component. See Configure the MES middleware proxy settings.

• If the SMS is changed, on the AVEVA Identity change the proxy AIM Host Name to match it and reconfigure the Middleware Proxy component. See Configure the MES middleware proxy AIM client registration.

• If the Common Platform HTTPS Port number is changed, change the proxy AIM HTTPS Port number to match it and reconfigure the Middleware Proxy component. See Configure the MES middleware proxy AIM client registration.