Content Management Improvements in AirWatch 8.3


 AirWatch 8.3 includes numerous improvements to Content Management.  These improvements fall under the four categories below and are further expanded on in each section:

  • Expanded Content Management APIs
  • Increased upload capacity
  • Streamlined configuration
  • Remote File Storage for Windows

Expanded Content Management APIs

AirWatch 8.3 will introduce expanded Content Management APIs, particularly around the use of personal content.  This will allow 3rd party applications to leverage content without requiring the use of the AirWatch SDK.  Additionally, it can simplify the user experiencing by not requiring a switch between Content Locker and 3rd party apps to manage personal content.  APIs in AirWatch 8.3 will allow users to:

  • Add content
  • Move content
  • Delete content
  • Share content (and folders)

API Access can be configured in the AirWatch Console by navigating to Settings > System > Advanced > REST API > General.  An API key should be generated with the Account Type set to Enrollment User to leverage the personal content APIs.

Additionally, personal content should be enabled in the AirWatch Console by navigating to Settings > Content > Personal Content.  On this page, make sure Personal Content is set to Enabled, as well as Folder Sharing and Link Sharing, as needed.

More information regarding the use of AirWatch APIs can be found by navigating to https://{Console_URL}/api/help, for your AirWatch Console environment.  

Increased upload capacity

AirWatch 8.3 introduces the ability to upload files that are larger than 2 GB.  Due to limitations with IIS on Windows Servers, this functionality is limited to Linux-based implementations of Remote File Storage (RFS).  File sizes greater than 2 GB are supported with the following requirements:

  • Personal Content is enabled with RFS (not with content stored in the AirWatch DB directly or local file storage).
  • RFS is installed on Linux (this functionality is not supported on Windows Servers due to IIS limitations)
  • If a Content Gateway is utilized, it is Linux-based (Windows MAG or Content Gateway are not supported)
  • Personal Content is uploaded via a Desktop (using Self Service Portal or the Sync Client).

If these requirements are met, AirWatch will be able to upload files directly to RFS without needing to utilize IIS on any of the intermediate servers.  This way, upload performance will be improved, and there is an increased capacity of file sizes up to 8 GB.

Streamlined configuration

In order to streamline configuration in the AirWatch Console and to allow for more customizable installation, in AirWatch 8.3 the AirWatch Tunnel and Content Gateway installers have been separated.  Thus, customers using only one of these features only need to configure and install that one.  Additionally, customers heavily utilizing these features can install them on separate servers for higher bandwidth and high-availability.  These components can still be installed on the same server if desired.

The Content Gateway will now be enabled and configured in the AirWatch Console under Settings > Content > Content Gateway.  If the AirWatch Tunnel and Content Gateway are to be configured and installed on the same server, it is recommended to installed/upgrade the AirWatch Tunnel first, particularly in the initial upgrade to the 8.3 versions of these components.


Remote File Storage for Windows

AirWatch 8.3 will reintroduce support for a Windows-based RFS installed.  RFS 2.3 provides improved scalability and performance to previous versions of RFS. While the Linux-based installer remains the recommended approach for new RFS configurations, this will allow a significant update to Windows-only environments with older versions of RFS. 

Have more questions? Submit a request


Article is closed for comments.