SaaS and on-premises customers should establish communications with AWCM. Performing this action allows you to configure an AirWatch instance to use a particular AWCM server.
Navigate to Groups & Settings > All Settings > System > Advanced > Site URLs to view the AirWatch Cloud Messaging section.Note:
If you are a SaaS customer and do not see this page in the system settings, then these settings have already been configured for you.
Configure the following settings:
Setting Description Enable AirWatch Server Check this box to allow the connection between the AirWatch Console and the AWCM server. AirWatch Server External URL
This field allows you to enter the servername used by external components and devices (e.g., VMware Enterprise Systems Connector) to securely (using HTTPS) communicate with AWCM. An example of an VMware Enterprise Systems Connector URL is: Acme.com.
Do not add https:// since this is assumed by the application and automatically added.
AirWatch External Port
This is the port that is being used by the servername above to communicate with AWCM.
For secure external communications, use port 443. If you are bypass offloading SSL, then you want to use an internal non-secure communications port, which is by default 2001 but can be changed to other port numbers.
AWCM Server Internal URL
This URL allows you to reach AWCM from internal components and devices (e.g., Admin Console, Device Services, etc.). Examples of AirWatch URLs are: https://Acme.com:2001/awcm or http://AcmeInternal.Local/awcm.
If your AWCM server and AirWatch Console are internal (within the same network), and you want to bypass offloaded SSL, there is no need for a secure connection, so you can use http instead of https. For example, http://AcmeInternal.Local:2001/awcm. This example shows the server resides within the internal network and is communicating on port 2001.