Content Gateway (Linux) Install Overview

Content Gateway (Linux) Install Overview

The following article is intended to assist AirWatch Customers and Agents install, validate and troubleshoot the Linux Content Gateway (SEG).

for more information on an
assisted install. Reach out to
your Account Executive to

Content Gateway (Linux) Install Guide

The install guide is intended to walk users through the preparation, installation and configuration of the Linux Content Gateway.

Pre-Install Requirements Worksheet

Provides a detailed explanation of all general, hardware, software and network requirements for a successful installation of the Linux Content Gateway. Please only reference the tab for the component you wish to install.

Content Gateway (Linux) Install Video

This instructional install video shows the step by step process for installing and validating the Linux Content Gateway.

Install Validation

Provides tests and checks to perform in order to validate that the component has been successfully installed and configured. These should always be performed after a new install or upgrade to confirm functionality.

Content Gateway (Linux) Logs

How to guide for gathering Linux Content Gateway logs. These logs will be needed if you run into any issues with the Linux Content Gateway during or after an install or upgrade. It will also help our support team assist you more quickly if these are provided up front.

Install Troubleshooting

This forum provides resolutions to common issues and error messages that are encountered during a Linux Content Gateway install. Please be sure to gather logs prior to beginning troubleshooting.

Install Validation

The following steps should be performed after a Linux Content Gateway install or On Premise upgrade to confirm that the Content Gateway was installed/updated successfully. If you encounter issues at any point during validation, please proceed to the Content Gateway (Linux) Logs and Install Troubleshooting sections.

Validation Step Actions Expected Results
Step 1 - Ensure Gateway is Enabled Navigate to Groups & Settings > All Settings > Content > Content Gateway "Enable the Content Gateway" is set to enabled.
Step 2 - Content Gateway Test Connection Navigate to Groups & Settings > All Settings > Content > Content Gateway Test connection is successful
Step 3 - Check that Service is Running Go to the server that Content Gateway was installed on and run command sudo service content-gateway status. No errors appear.
Step 4 - Check Installer Log Go to: opt/airwatch/content-gateway/-content-gateway-installer/logs. Go to the bottom and make sure that the log doesn’t show any errors. (One useful command you can use is cat -n | tail –n 20.) Installation completed with no errors.


Feature Validation


The following steps should be performed after a Linux Content Gateway install or On Premise upgrade to confirm Content Gateway feature functionality.

Validation Step Actions Expected Results
Step 1 - Add Repository in Console Navigate to Console > Content > Repositories > Add a Repository. Enter information and check "Access via MAG/Content Gateway". Test connection and save. Test connection succeeds and repository saves.
Step 2 - Access Repository on Device Open the Content Locker on your device and open the Repository. You should see all the file names on your repository within the Content Locker application.
Step 3 - Download File from Content Locker Repository Once you are in the Admin Repository, download a file and open it. File successfully downloads and you are able to open the file

Content Gateway (Linux) Logs

The following article provides information on how and when to collect and verbose logs related to the Linux Content Gateway.

Collecting Logs

Collecting logs from the Content Gateway is an effective way of finding the source of an issue with your Content Gateway. If you are receiving errors when trying to connect to your Content Repository, if content is not pushing down to devices, if your test connection to your Content Gateway is failing, etc. There are many troubleshooting steps you can try before collecting logs but if you are submitting a support ticket the time to resolve the ticket will be much quicker if you include the logs.

Content logs are stored in the native syslog system of Linux. Logs are stored in /var/log/airwatch/content-gateway/ and can be sorted by the following command (as root):
tail -f /var/log/airwatch/content-gateway/content-gateway.log
To verbose, set root level=”warn” to root level=”debug” in /opt/airwatch/content-gateway/conf/logback.xml


sudo service content-gateway start – Starts the service.
sudo service content-gateway stop – Stops the service.
service content-gateway restart – Restarts the service.
sudo service content-gateway status – Shows the status of the service.

Have more questions? Submit a request


Article is closed for comments.