Host internal applications on your network with an external application repository and manage the applications with AirWatch. AirWatch uses Windows File Share protocols to make externally hosted applications available to user devices. Communication is secure because on-premise deployments must use the Content Gateway for Windows to transfer data from the on-premise network to AirWatch.

  1. Configure and use the Content Gateway for Windows to secure communications between your network and AirWatch if you have an on-premise deployment.

    For information on configuring the Content Gateway, see the AirWatch Content Management Enterprise Integration Solution Overview.

  2. Enter the credentials for the external app repository so AirWatch can direct device users to the internal applications on your network in the external app repository. AirWatch supports one set of credentials to authenticate to repositories that require it. If you have multiple repositories set up on the Content Gateway, use a common set of credentials, if your repositories require authentication.

    See Enable the External App Repository.

  3. Enter the location of internal applications on the external app repository using a link.

    See Configure Internal Application From External Repositories.

For a list of the supported components for the use of this feature, see Supported Components for External App Repositories.

Difference Between External App Repositories and File Storage Systems in VMware AirWatch

The service that facilitates the connection for sending and receiving applications on an external app repository is different than the one for a file storage system.

  • External App Repository - The Content Gateway facilitates the connection for the device to get the application from the external app repository when the console initiates the deployment.
  • File Storage - The Devices Services server facilitates the connection for the device to get the application from the file storage system when the console initiates the deployment.