You can deploy the AWCM in four modes, depending on the resources and requirements unique to your deployment.

  1. Single Instance

    A single AWCM server processes all requests.

    This is the simplest configuration, but it has no redundancy in case of server failure.

  2. Two Instances (Active-Passive Servers)

    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 down, the load balancer switches all the requests to the secondary server until the primary is back online.

    The Active-Passive Server setup ensures that high availability is maintained when the number of network requests is of no concern.

    This setup is best for on-premises customers using ACC with AWCM who do not use AWCM for device-specific communication.

  3. Horizontal Scaling with Multiple Instances (Active-Active Servers with Implicit Clustering)

    Multiple AWCM servers run behind a load balancer and communicate with clients using session persistence (using the awcmsessionid cookie).

    This setup is best if balancing network traffic from multiple clients is more important than high availability. This is also the optimal solution for horizontal scalability.

    For more information, see the following Workspace ONE UEM Knowledge Base article: https://support.workspaceone.com/articles/115001666028.