You can deploy the AWCM in four modes. In most cases the Two Instances (Active – Passive Servers) mode is the preferred method. The following is a list of the four available modes and a description of each.
Single AWCM server processes all requests. This is the simplest configuration.
Two Instances (Active – Passive Servers) Preferred Deployment
Both servers (an active primary server and a passive secondary server) run behind a load balancer. The load balancer periodically checks the health of the primary and secondary servers. If the primary server is deemed as down, the load balancer switches all the requests to the secondary server until the primary is back online.
This method ensures that high availability is maintained, but the amount of network requests is of no concern. This is preferred for the on-premises customer that is only using Cloud Connector with AWCM and is not requiring AWCM for device-specific functionality (remote control, file manager, GCM replacement, etc).
Horizontal Scaling with Multiple Instances (Active – Active Servers, With Implicit Clustering)
AWCM server instances with clients (device agents, console, remote control and the VMware Enterprise Systems Connector, VMware Enterprise Systems Connector) using session persistence (via the awcmsessionid cookie) on a load balancer, which is the optimal solution for horizontal scalability. Multiple AWCM servers run behind a load balancer. Unlike the “active-passive” deployment above, this method is preferred when network traffic becomes a concern with balancing connections from multiple clients (devices, VMware Enterprise Systems Connector, VMware Tunnel) is more important than just high availability.
For more information, see the following AirWatch Knowledge Base article: https://support.air-watch.com/articles/115001666028.
AirWatch supports session persistence. VMware Enterprise Systems Connector and remote control provide the session persistence option.
Multiple Instances (Active – Active Servers, With Explicit Clustering)
Multiple AWCM instances are active behind a load balancer. These servers establish a cluster by means of TCP communication using the default port 5701 within your internal LAN. The caveat with this deployment option is performance overhead resulting from inter-node communication to maintain a single view of in-memory data.
Remote control is not supported in this configuration as it requires persistence on the load balancer.
For customers upgrading from AWCM 4.x to AWCM 6.x and wanting to use explicit clustering, please refer to the following KB article: https://support.air-watch.com/articles/115001665788.