To deploy VMware AirWatch Cloud Messaging, your system confiuration must meet certain requirements.

Hardware Requirements

The following hardware requirements are for dedicated AWCM servers.

  • Minimum: Windows Server 2008 R2; Supported: Windows Server 2012 R2, Windows Server 2016
  • 8GB of RAM
  • 4-core CPU (minimum 2GHz)

AWCM is incorporated with the Workspace ONE UEM installer and you can install it:

  • On the Device Services server.
  • On a dedicated server.
  • On a load-balanced server.
  • On a cloud server.
  • In a customer network with no access to the Internet.

Regardless of the deployment method, the device must have access to both AWCM and the Device Services server. Once the system is established on a server, an administrator creates a complete connection in the Workspace ONE UEM console.

If you install AWCM on the Device Services server, then reference the VMware AirWatch Recommended Architecture Guide, which contains hardware and sizing information when combining these components.

Software Requirements

The following software requirements are for the application server on which the AWCM is installed.

  • 64-bit Java (Java Runtime Environment version 8).
    Note: The necessary version of Java is included with the Workspace ONE UEM Installer, and will install automatically during Workspace ONE UEM installation.

Network Requirements

  • Devices must have access to both AWCM and the Device Services server, if they are not on the same application server.
  • Devices must reach the AWCM server on port 2001 by default (configurable).
  • The Workspace ONE UEM console, Device Services, API, and the Self-Service Portal must be configured to connect to your AWCM server on port 2001 by default (configurable).
    Note: You can configure access to the AWCM server to be done over port 443, provided that AWCM is not on a server already using that port.
  • VMware Tunnel and VMware AirWatch Cloud Connector must have access to the AWCM endpoint.

Load Balancing AWCM in an On-Premises Deployment

To deploy AWCM with multiple nodes behind a load balancer without clustering, you must account for persisting the connections to the AWCM servers. In the HTTP request that is sent to AWCM (from a device, the device services server, the console server, VMware AirWatch Cloud Connector, and so on), there is a cookie value called awcmsessionid, which is used to establish request level affinity to an AWCM node from a pool of nodes. You must configure your load balancer or proxy to parse the HTTP request for this value and use it for persistence.

For more information on how to achieve this on an F5 LTM, see the following Workspace ONE Knowledge Base article: https://support.workspaceone.com/articles/115001666028.