Deciding between Pull & Push Relay Servers for rugged device management

What is a Relay Server?

For those organizations with rugged devices who want to, for instance, take advantage of one single scan to enroll, manage, and provision those devices, a Relay Server should be deployed on the internal network. The purpose of the Relay Server, which is simply a FTP/FTPS server, is to provide fast, inexpensive data connections over the WLAN where, usually, the rugged device has no internet access.

A Relay Server is required for both barcode scan staging and on-demand staging. A Relay Server is not required for either side-load staging or web enrollment. For more information on the AirWatch Relay Server, view the reference sheet here.

Push vs. Pull Relay Server

The AirWatch Relay Server can be configured in a Pull or Push configuration, depending on the deployment model.  More information about each of these configurations is given below.

Pull Relay Server pulls content from AirWatch based on certain variables established in the server configuration. In this configuration a connection between the Console Server and the FTP is only established when the FTP reaches out to the Console. A web-based application stored in the Relay Server pulls content and applications contained in the product or staging from the AirWatch Admin Console through an outbound connection. This is the configuration usually recommended for SaaS AirWatch deployments.

Push Relay Server will push content from AirWatch to devices when ever it is published. This means an active connection between the Console Server and the FTP is always required to be maintained. Whenever a change is detected, the relevant content is pushed to the FTP by the Console Server. No extra installation is required on the FTP server if you are making use of the Push configuration. This is the configuration usually recommended for on-premise AirWatch deployments.

Have more questions? Submit a request


Article is closed for comments.