Configure a pull service relay server using a Linux FTP, FTPS, or SFTP server for use with product provisioning and staging. The pull service must be installed before you integrate the server with the AirWatch Console.
An FTP, FTPS, or SFTP server. AirWatch recommends using FTP or FTPS servers, as SFTP is not a standardized format.
- Linux-based servers must run either CentOS or SLES 11 SP3.
- Java 8+ must be installed on Linux-based servers.
- The relay server requires network access between the server (in-store, distribution center, etc.) and to the AirWatch SaaS environment.
- Each server requires disk storage of 2 MB for the pull server installer as well as storage space for all the content pulled to the server.
To create a Linux-based pull relay server, follow the steps detailed below:
- Configure an FTP, FTPS, or SFTP server. You must create an FTP user with read/write/delete permissions for both the directory and the files used in the relay server. This FTP user is must have a username and password for authentication. Note the home directory of the user for use in configuring the pull service.
- Navigate to Groups & Settings > All Settings > System > Enterprise Integration > Pull Service Installers .
- Download the Linux Pull Service Installer and the Configuration file onto the server using your preferred server management system.
Open the XML config file and update the IP Address with your console server FQDN, for example, cn274.awmdm.com.
<endPointAddress>https://[endpoint URL]/contentpull /</endPointAddress>
In the command prompt, enter:
Alternatively, enter the following command to silently install:
sudo ./LinuxPullServerInstaller.bin -I silent
- Navigate to Devices > Staging & Provisioning > Relay Servers > Undiscovered Pull Relay Servers. If you have configured the FTP, FTPS, or SFTP server correctly, it will display on this screen. If you do not see your server, check your configuration settings.
- Configure the relay server as a pull relay server in the AirWatch Console. See Configure a Relay Servers for more details.
The installer looks for the PullserviceInstaller.config file in the installer execution directory. If the file is missing, the installer prompts you to let you know the file is missing.