MES middleware load balancing considerations

The availability of the MES middleware is critical in keeping the production applications available to the end users. The MES middleware load can be distributed by installing the MES middleware on multiple servers. Each client is set up to connect to one MES middleware with an option to define additional MES middleware hosts in case of failure.

If the system includes the recommended one MES middleware host for each Application Server, Work Tasks Server, Terminal Server, Web Server, and Enterprise Integration, then the system will inherently be load‑balanced.

If a client machine only has the MES Middleware Proxy installed and directs transactions to an MES middleware on another machine, fail‑over can be configured by pointing the MES middleware proxy to multiple MES middleware hosts.To guarantee automatic fail-over of the MES middleware host, you can set up the software to take advantage of High Availability provided by both Hyper-V and VMware virtualized environments. For higher availability, a Windows Cluster Server can be used for the MES middleware host.

If the system includes the recommended one MES middleware host for each Application Server, Terminal Server, Web Portal Server, and Enterprise Integration, then there is no need to fail over.

If you are using Extensibility Hooks, they must be set up for each MES middleware host.