Configure a relay server by configuring an FTP, FTPS, or SFTP file server and integrating it with AirWatch.

Important:

If you use the pull service to create a pull-based relay server, you must give SYSTEM full access to the home directory. This allows the pull service to store and remove files from the directory.

Requirements

  • An FTP, FTPS, or SFTP server
  • You must create an FTP user with a home directory. This user must have 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.

While SFTP servers are supported by AirWatch, the Zebra Rapid Deployment Client does not support SFTP servers for use with barcode staging.

Procedure

  1. Navigate to Devices > Staging & Provisioning > Relay Servers > List View and select Add.

  2. Complete the General fields:
    Setting Description
    Name Enter a name for the relay server.
    Description Enter a description for the relay server.
    Relay Server Type ID

    Select either Push or Pull as the relay server method.

    Push – This method is typically used in on-premises deployments. The AirWatch Console pushes content and applications contained in the product or staging to the relay server.

    Pull – This method is typically used in SaaS deployments. A web-based application stored in the relay server pulls content and applications contained in the product or staging from the AirWatch Console through an outbound connection.

    For more information on installing a pull server, see Pull Relay Server Configuration.

    Restrict Content Delivery Window

    Enable to limit content delivery to a specific time window.

    Provide a Start Time and End Time based on the relay server time.

    Assignment
    Managed By

    Select the organization group that manages the relay server.

    If you want to use the FTP(S) server for Barcode Enrollment only and not for Product Provisioning, remove all assigned organization groups under the Production Server section.

    Staging Server

    Assign the organization groups that use the relay server as a staging server.

    A staging server only works for the staging process involving the Rapid Deployment Client.

    Production Server

    Assign the organization groups that use the relay server as a production server.

    A production server works with any device with the proper agent installed on it.

    Device Connection
    Protocol

    This is the information the device uses to authenticate with the FTP(s) server when downloading apps and content.

    FTP, FTPS, or SFTP as the Protocol for the relay server.

    If using FTPS, your FTPS server must have a valid SSL certificate. Configure the SSL certificate on the FTPS server.

    Port

    Select the port established for your server.

    Important:

    The ports you configure when you create your FTP, FTPS, or SFTP server must be the same ports you enter when creating a relay server in the AirWatch Console.

    User

    Enter the server username.

    Password Enter the server password.
    Path

    Enter the path for the server.

    This path must match the home directory path of the ftp user. For example, if the ftp user's home directory is C:\ftp\home\jdoe, the path entered into this field must be C:\ftp\home\jdoe.

    Passive Mode Enable to force the client to establish both the data and command channels.
    Verify Server

    Enable to ensure the connection is trusted and there are no SSL errors. Use only if you use FTPS servers.

    If left unchecked, then the certificate used to encrypt the data can be untrusted and data can still be sent.

  3. For a push server, select the Console Connection tab and complete the fields. This is the information that the AirWatch Console uses to authenticate with the FTP(S) server when pushing apps and content. The fields are typically identical to the Device Connection tab.

    For a pull server, select the Pull Connection tab and complete the fields:

    Settings Descriptions
    Pull Local Directory Enter the local directory path for the server.
    Pull Discovery Text

    Enter the IP addresses or the MAC addresses of the server. Separate each address with commas.

    IP addresses use periods as normal but MAC addresses do not use any punctuation in this form.

    Pull Frequency Enter the frequency in minutes that the pull server should check with the AirWatch Console for changes in the product.
  4. Press the Test Connection button to test your Console Connection to the server. Each step of the connection is tested and the results are displayed to help with troubleshooting connection issues.

    Press the Export button on the Test Connection page to export the data from the test as a .csv file.

  5. Select Save.