Remote File Storage (RFS) and Content Rendering Engine (CRE) for Linux Install Overview

Remote File Storage and Content Rendering Engine (Linux) Install Overview

The following article is intended to assist AirWatch Customers and Agents install, validate and troubleshoot Linux Remote File Storage (RFS) and Content Rendering Engine (CRE).

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

RFS/CRE (Linux) Install Guide

The install guide is intended to walk users through the preparation, installation and configuration of the Linux Remote File Storage and Content Rendering Engine.

Pre-Install Requirements Worksheet

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

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.

RFS/CRE (Linux) Logs

How to guide for gathering RFS/CRE logs. These logs will be needed if you run into any issues with the RFS/CRE 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 an RFS/CRE install. Please be sure to gather logs prior to beginning troubleshooting.



Install Validation


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

Validation Step Actions Expected Results
Step 1 - Ensure Services are Running on Server Go to your RFS server and run the following commands depending on where you installed each service:
RFS:
$ sudo service AirWatchRfs status
CRE:
$ sudo service cre status
Services appear as started.
Step 2 - Ensure Remote Storage and Content Viewer is enabled and active. Navigate to Groups & Settings > All Settings > Content > Remote Storage. Also under Content go to Content Viewer to ensure that is enabled. Both pages are configured and the "Active" icon is green.
RFS_Linux_1.jpg

Feature Validation


The following steps should be performed after an RFS/CRE install or On Premise upgrade to confirm RFS/CRE functionality.

Validation Step Actions Expected Results
Step 1 - Add Files to Self Service Portal Navigate to Groups & Settings > All Settings > Content > Personal Content and ensure that Personal Content is enabled with a storage quota. Log into the Self Service portal and add any file into the portal. The file saves to SSP successfully.
RFS_Linux_3.jpg
RFS_Linux_4.jpg
Step 2 - Check RFS Desination Folder for Files/Folders Navigate to your server where you directed the files to be stored. Check for files and folders. The folder should have files with long strings of characers. This indicates AirWatch has started placing files here.
RFS_Linux_5.jpg
Step 3 - Try to render a file in the Self Service Portal Login to your Self Service Portal and select a file within the portal that has been uploaded through RFS. File renders successfully within the Self Service Portal
RFS_Linux_6.jpg

RFS/CRE (Linux) Logs


The following article provides information on how and when to collect and verbose logs related to Linux RFS and CRE.

Collecting Logs


Collecting Logs from the RFS and CRE servers are extremely important for the installation process. If any issues arise during the installation, the logs will reveal what failed so you can begin to troubleshoot. The logs also often reveal issues when content does not render correctly in the Self Service Portal. There are a few 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 for the component you are having issues with.

RFS and CRE have important default directories that store their install logs, server logs and configuration files.

RFS LOGS:
Post Installation Log: “/opt/airwatch/rfs/_ RemoteFileStorage_ installation/Logs/”
View log summaries of all installed components and any install errors.
Server Logs: “/var/log/airwatch/rfs”
View log files for Files and Tokens through vi editor in Linux or through WinSCP.

CRE LOGS:
Post Installation Log: “/opt/airwatch/cre/_ ContentRenderingEngine/Logs/”
View log summaries of all installed components and any install errors.
Server Logs: “/var/log/airwatch/cre”
View server log files through vi editor in Linux or through WinSCP.

Setting Logging Levels

Set FRS Files Log Level:
1. Create a backup of the logback.xml for the RFS Files Service in “/opt/airwatch/rfs/rfs-files#.#/conf/” on the RFS server (#.# is the version of RFS).
cp logback.xml logback.backup
2. Edit the file on using the Linux vi editor or on WinSCP:
3. Change the logging level to “debug” for both the logger and root XML attributes and save the changes.
4. Restart the files service after saving changes with "sudo service AirWatchRfs restart"

Set RFS Tokens Log Level:
1. Create a backup of the logback.xml for the RFS Tokens service in “/opt/airwatch/rfs/rfs-tokens#.#/conf/” on the RFS server ( #.# is the version of RFS).
cp logback.xml logback.backup
2. Edit the logback.xml file on using the Linux vi editor or on WinSCP:
3. Change the logging level to “debug” for both the logger and root XML attributes and save the changes.
4. Restart the tokens service after saving changes with "sudo service AirWatchRfs restart"

Set CRE Log Level:
1. Access the airwatch.json for the cre service in “/opt/airwatch/cre/configuration/”
cp airwatch.json airwatch.backup
2. Edit the airwatch.json file on using the Linux vi editor or on WinSCP:
3. pdate the default log level to “debug” and save changes
4. Restart the cre service after saving changes with "sudo service cre restart"

Have more questions? Submit a request

0 Comments

Article is closed for comments.