Each AWCM server requires the following minimum requirements:

Hardware Requirements

The following hardware requirements are for dedicated AWCM servers.

  • Windows 2008, or any macOS with Java Virtual Machine (JVM)
  • 4GB of RAM
  • Dual-core Processor

AWCM is incorporated with the AirWatch installer and you can install it on the following systems:

  • On the same server as the AirWatch Console.

  • On the Device Services server.
  • On a dedicated server.

  • On a load-balanced server.

  • On a cloud server.

  • In a customer’s 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 AirWatch Console.

If you're installing AWCM on the Device Services server, then please see the VMware AirWatch Recommended Architecture Guide, available on AirWatch Resources, which contains hardware and sizing information when combining these components.

Software Requirements

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

  • 64-bit Java (Java Runtime Environment version 8).

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 AirWatch 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 Enterprise Systems 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 Enterprise Systems 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 AirWatch Knowledge Base article:  https://support.air-watch.com/articles/115001666028.