AirWatch Cloud Messaging (AWCM) is used in conjunction with the VMware Enterprise Systems Connector to provide secure communication to your back-end systems. VMware Enterprise Systems Connector uses AWCM to communicate with the AirWatch Console.
AWCM also streamlines the delivery of messages and commands from the AirWatch Console by eliminating the need for end users to access the public Internet or utilize consumer accounts, such as Google IDs. It serves as a comprehensive substitute for Google Cloud Messaging (GCM) for Android devices and is the only option for providing Mobile Device Management (MDM) capabilities for Windows Rugged devices.
AirWatch configures AWCM in SaaS environments for customers who want to use it. If you are a SaaS customer, then you can read this guide to learn more about AWCM, but know that you do not have to perform the configuration steps within.
On-premises customers can use this guide to configure AWCM and Secure Channel. Since AWCM installation occurs during AirWatch application server installation, you can find the installation steps for AWCM in the VMware AirWatch Installation Guide (VMware provides this document to you as part of the on-premises installation process).
AWCM simplifies device management by offering the following benefits:
- Enabling secure communication to your back-end infrastructure through the VMware Enterprise Systems Connector.
- Enabling AirWatch Windows Protection Agent real-time communication.
- Removing the need for third party IDs.
- Delivering AirWatch Console commands directly to Android and Windows Rugged devices.
- Enabling the ability for remote control and file management on Android Samsung Approved for Enterprise (SAFE) and Windows Rugged devices.
- Enabling the ability to send remote commands such as device wipe and device lock to macOS and Windows 7 devices.
- Increasing the functionality of internal Wi-Fi only devices by enabling push notification in certain circumstances.