Technical Requirements

You are reading the AEM 6.1 version of Technical Requirements.
This documentation is also available for the following versions:  AEM 6.2  AEM 6.0  AEM 5.6.1  AEM 5.6  CQ 5.5  CQ 5.4 

Adobe supports Adobe Experience Manager (AEM) on the platforms according to the information in this document below.

For any issues that are specifically related to the platform itself, you will need to contact the platform vendor directly.


Depending upon the platform on which you install AEM, there could be different sets of requirements for user management.


To install Adobe Experience Manager you need in minimum:

  • Installed Java Platform, Standard Edition - the Server JRE or JDK in the supported version - see Java Virtual Machines
  • Experience Manager Quickstart file (Standalone JAR or web-application deployment WAR)

Minimum Sizing Requirements

The following are the minimum requirements:

  • 5 GB free disk space in the installation directory
  • 2 GB memory
    Mind that digital asset use cases need more base memory. See installation instructions for details.

You will have to increase these in accordance with your operational expectations. Please see the Hardware Sizing Guidelines for further information.

Support Levels

This document lists the supported client and server platforms for Adobe Experience Manager. Adobe provides several levels of support, both for our recommended configurations and for other configurations.

Recommended Configurations

Adobe recommends these configurations and provides full support as part of the standard software maintenance agreement.

Support Level Description
A: Supported Adobe provides full support and maintenance for this configuration. This configuration is covered by Adobe's quality assurance process.
R: Restricted Support To ensure our customers project success, Adobe provides full support within a restricted support program, which requires that specific conditions are met. R-level support requires a formal customer request and confirmation by Adobe. For more informations, please contact Adobe Customer Care.

Unsupported Configurations

Support Level Description
E: Expected to work The configuration is expected to work, and there are no reports to the contrary.
Z: Not supported The configuration is not supported. Adobe does not make any statements about whether the configuration works, and does not support it.

Supported Platforms

Java Virtual Machines

The application requires only a Java Virtual Machine to run, which is provided by the Java Runtime Environment (JRE) distribution. Generally Adobe recommends using the Java Development Kit (JDK) distribution. Both JRE and JDK distributions are a part of the Java Standard Edition (Java SE).

Adobe Experience Manager operates with the following versions of the Java Virtual Machine (Runtime Environment).


It is recommend to track the Security Bulletins from the Java vendor to ensure the safety and security of production environments and install the latest Java Updates.

Platform Support Level
Oracle SE 8 JRE 1.8.x (64bit) A: Supported
Oracle SE 7 JRE 1.7.x (64bit) (3) A: Supported
Oracle SE 6 JRE 1.6.x Z: Not supported
IBM J9 VM (build 2.8, JRE 1.8.0) Z: Not supported
IBM J9 VM (build 2.6 & 2.7, JRE 1.7.0) (1) A: Supported
IBM J9 VM (build 2.4 & 2.6, JRE 1.6.0) (1) A: Supported
IBM J9 VM (build 2.3, J2RE 1.5.0) Z: Not supported
HP JRE 8.0.x (2) A: Supported
HP JRE 7.0.x (2) A: Supported
HP JRE 6.0.x Z: Not supported
  1. The IBM JRE is only supported on IBM server platforms (AIX), or in conjunction with WebSphere Application Server.
  2. The HP JRE is only supported on HP server platforms (HP-UX).
  3. Oracle Java 7 reached end of life as of May 2015. See this notice from Oracle for more information. Adobe recommends to our customers to use a Java distribution that is actively supported by the manufacturer.


Although Java 7 is supported, customers may experience severe performance issues due to a known bug in Java 7. Please see this knowledge base article for further information.

Storage & Persistence

There are various options to deploy the repository of Adobe Experience Manager. Following a list of supported technologies and storage options.

Platform Description Support Level
File System (1) Repository Microkernel (TAR files) A: Supported
File System (1) To store binaries A: Supported
MongoDB Enterprise 2.6 (2) Repository Microkernel
A: Supported
MongoDB Enterprise 3.0 (2)(3) Repository Microkernel A: Supported
IBM DB2 10.5  Repository Microkernel R: Restricted Support
Oracle Database 12c Repository Microkernel R: Restricted Support
MySQL 5.5 Repository Microkernel E: Expected to work
Amazon S3 To store binaries A: Supported
Apache Solr To use as internal search engine A: Supported
  1. 'File System' includes block storage that is POSIX compliant. This includes network storage technology. Mind that file system performance might vary and influences the overall performance. It is recommended to load test AEM in combination with the network/remote file system.
  2. MongoDB Sharding is not supported in AEM.
  3. MongoDB Storage Engine WiredTiger is supported only.


See Deploying Communities for additional information regarding the AEM Communities capability.


MongoDB is third-party software and is not included in the AEM licensing package. For more information see the MongoDB licensing policy page.

In order to get the most of your AEM deployment, Adobe recommends licensing the MongoDB Enterprise version in order to benefit from professional support.

The license includes a standard replica set, which is composed of one primary and two secondary instances that can be used for either the author or the publish deployments.

In case you wish to run both author and publish on MongoDB, two separate licenses need to be purchased.

Adobe Customer Care will assist qualifying issues related to the usage of MongoDB with AEM.

For more information, see the MongoDB for Adobe Experience Manager page.


Supported relational databases as listed above is third-party software and is not included in the AEM licensing package. 

In order to run AEM 6.1 with a supported relational database, it is required that you have a separate support contract with a database vendor directly. Adobe Customer Care will assist qualifying issues related to the usage of relational databases with AEM 6.1.

Please note, that all relational databases are currently supported within Level-R on AEM 6.1, which comes with support criterias and a support program as stated in the Level-R description above.

Servlet Engines / Application Servers

Adobe Experience Manager can run either as a standalone server (the quickstart JAR file) as web application within a third party application server (the WAR file).

Minimum Servlet API Version required: 2.5

Platform Support Level
Quickstart built-in Servlet Engine (Jetty 9.2) A: Supported
Oracle WebLogic Server 12.1 (12c) A: Supported (1)
Oracle WebLogic Server 10.3.6, 10.3.5 (11g) Z: Not supported
IBM WebSphere Application Server 8.5.5 A: Supported
IBM WebSphere Application Server 8.5 A: Supported
IBM WebSphere Application Server 8 A: Supported
IBM WebSphere Application Server 7 Z: Not supported
IBM WebSphere Application Server 6.1 Z: Not supported
Apache Tomcat 8 A: Supported (2)
Apache Tomcat 7 E: Expected to work (2)
Apache Tomcat 6 Z: Not supported
JBoss EAP 6.3.0 with JBoss Application Server 7.4 A: Supported
JBoss EAP 6.2.0 with JBoss Application Server 7.3 A: Supported
JBoss EAP 6.1.0 with JBoss Application Server 7.2
A: Supported
JBoss Application Server 7.1 E: Expected to work
JBoss Application Server 5 Z: Not supported
  1. AEM Forms supports only Oracle WebLogic 12.1.3.
  2. AEM forms does not support Apache Tomcat.

Server Operating Systems

Adobe Experience Manager works with the following server platforms:

Platform Support Level
Microsoft Windows Server 2012 R2 A: Supported
Microsoft Windows Server 2012 A: Supported
Microsoft Windows Server 2008 R2 A: Supported
Microsoft Windows Server 2008 Z: Not supported
Oracle Solaris 11 A: Supported with limitations (3,5)
Oracle Solaris 10 A: Supported with limitations (3,5)
RedHat Linux Kernel 2.6 and 3.x (1) A: Supported
HP-UX 11i v1-3 A: Supported with limitations (2,3,4,5)
IBM AIX 7.1 A: Supported with limitations (2,3,5)
IBM AIX 6.1 A: Supported with limitations (2,3,5)
SUSE Linux Enterprise Server 12 A: Supported
SUSE Linux Enterprise Server 11 A: Supported
Apple OS X Server E: Expected to work (6)
  1. Linux Kernel 2.6 and 3.x includes derivatives from Red Hat distribution, including Red Hat Enterprise Linux, CentOS, Oracle Linux and Amazon Linux.
  2. Please see the section Support for XMP metadata write-back
  3. No support for Dynamic Media Imaging. Dynamic Media Video is supported.
  4. No support for XFA based adaptive forms, XFA to PDF and/or HTML conversion (Experience Manager Forms), and AEM forms add-on features.
  5. No support for Advanced Raw file transformation (Experience Manager Assets)
  6. Not supported in production environment for AEM Forms.

Virtual & Cloud Computing Environments

Adobe Experience Manager running in virtual machines in the cloud computing environments is supported in compliance with Adobe's support policy for all other system components (operating system, JVM, application server, etc).

For example, Experience Manager works with virtual machines in the following cloud computing environments, similar to the deployment on other virtual servers or dedicated servers:

  • Amazon EC2
  • Rackspace Cloud
  • VMware vCloud

Dispatcher Platforms (Web Servers)

The Dispatcher is the caching and load balancing component. Download the latest Dispatcher version from Adobe PackageShare. Experience Manager 6.1 requires Dispatcher version 4.1.10 or higher.


Please make sure to run Dispatcher version 4.1.11 or higher if you want to make use of Client Context on AEM 6.1

The following web servers are supported for use with a Dispatcher version 4.1.10:

Platform Support Level
Apache httpd 2.4.x A: Supported (1)
Apache httpd 2.2 A: Supported (1) (2)
Apache httpd 2.0 Z: Not Supported
Apache httpd 1.3.x Z: Not Supported
Microsoft IIS 8.5 (Internet Information Server) A: Supported
Microsoft IIS 8.0 (Internet Information Server) A: Supported
Microsoft IIS 7.5 (Internet Information Server) A: Supported
Microsoft IIS 7 (Internet Information Server) Z: Not Supported
Microsoft IIS 6 (Internet Information Server) Z: Not Supported
Oracle iPlanet Web Server 7 A: Supported

(1) Web servers built on the basis of Apache httpd source code will have the same level of support as the version of httpd on which it is based only in the following cases:

  • The HTTP server was built using only official Apache source distributions, or
  • The HTTP server was delivered as part of the operating system on which it is running.

Examples: IBM HTTP Server, Oracle HTTP Server

If in doubt, please ask Adobe for confirmation of the support level related to the respective server product.

Dispatcher is not available for Apache 2.4.x for Windows operating systems.

(2) Adobe will drop support for Apache httpd 2.2 after Dec 2017, and recommends to upgrade to Apache httpd 2.4. In case you stay with Apache 2.2 beyond Dec 2017, it is recommended to use a Linux distribution that commits to Apache 2.2 security updates. The latest dispatcher release of 2017 for Apache 2.2 will still be available for download until end of 2018.

Supported Client Platforms

Supported Browsers for Authoring User Interface

The Adobe Experience Manager user interface works with the following client platforms. All browsers are tested with the default set of plug-ins and add-ons.

The user interface is optimized to be used on larger screens (typically notebooks and desktop computers) and tablet form factor (such as Apple iPad or Microsoft Surface). The phone form factor is not supported.


User interface performance

The authoring user experience highly depends on the ability for the web browser to execute JavaScript in a performant way. Browser vendors made big progress in the last few years to improve the performance of web browsers. It is therefore recommended to use current browser versions for a good content authoring experience.


Support for browsers with rapid release cycles:

Mozilla Firefox and Google Chrome release updates every few months. Adobe is committed to provide updates for Adobe Experience Manager to maintain the support level as stated below with upcoming versions of these browsers.

Browser Support for Classic UI
Support for Touch-optimized UI
Microsoft Edge (7) (7)
Microsoft Internet Explorer 11 A: Supported A: Supported
Microsoft Internet Explorer 10 A: Supported Z: Not supported
Microsoft Internet Explorer 9 A: Supported A: Supported
Microsoft Internet Explorer 8 A: Supported (6), (7) Z: Not supported
Microsoft Internet Explorer 7 Z: Not supported Z: Not supported
Microsoft Internet Explorer 6 Z: Not supported Z: Not supported
Mozilla Firefox 47+ A: Supported A: Supported
Mozilla Firefox 45 (ESR) (3) A: Supported A: Supported
Mozilla Firefox 38 (ESR) (3) Z: Not supported Z: Not supported
Google Chrome 51+ A: Supported A: Supported
Apple Safari 9.0 (OS X) A: Supported A: Supported
Apple Safari 8.0 (OS X) A: Supported A: Supported
Apple Safari 7.0 (OS X)
A: Supported A: Supported
Apple Safari 6.0 (OS X) Z: Not supported Z: Not supported
Apple Safari on iOS 9.x (5) Z: Not supported  
Apple Safari on iOS 8.x (5) Z: Not supported A: Supported
Apple Safari on iOS 7.x (5) Z: Not supported A: Supported
Apple Safari on iOS 6.x (5) Z: Not supported Z: Not supported
  • (3) Extended Support Release of Firefox Learn more about this on
  • (5) support for Apple iPad and Apple iPad mini
  • (6) Microsoft Internet Explorer 8 has a known issue, which leads to a growing memory consumption. It is recommended to use a newer browser version.
  • (7) No support for AEM Forms add-on


Microsoft Internet Explorer 9 is not supported for the user administration interface of AEM, including Adobe’s identity management system.

Supported Browsers for Websites

Generally, the browser support level for sites is depending on the implementation of the templates, design and component output, and therefore in control of the party implementing these parts.

Exceptions are mentioned below:

Components of AEM Forms Add-on

The components provided in the AEM Forms Add-on (Adaptive forms and HTML5 forms components) support the browsers as mentioned in the section "Supported Browsers for Authoring User Interface" above with following amendments:

  • Support for Apple iPad 5.1.1 and later with Apple Safari 5.1.
  • Support for Google Android 4.0 and later with Chrome for Android.
  • No support for Android default browser.
  • No support for Microsoft Internet Explorer 6, 7 and 8.
  • Support for Microsoft Surface Pro 2 with Microsoft Internet Explorer 11.

WebDAV Clients

Windows Vista, Windows 7, Windows 8

Note: On Windows Vista, Service Pack 2 of Windows Vista is required to connect AEM using WebDAV.

To successfully connect with Windows Vista, Windows 7 and 8 to an AEM instance that is not secured with SSL, basic authentication over unsecured network must be enabled in Windows. This requires a change in the Windows Registry of the WebClient:

  1. Locate the registry subkey:
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
  2. Add the BasicAuthLevel registry entry to this subkey using a value of 2 or more.

See Microsoft Support KB 841215.

To improve responsivness of the WebDav Client under Windows - see Microsoft Support KB 2445570

Additional Platform Notes

This section provides special notes and more detailed information about running Adobe Experience Manager and its add-ons.

IPv4 and IPv6

All elements of Adobe Experience Manager (Instance, Dispatcher) can be installed in both IPv4 and IPv6 networks.

Operation is seamless as no special configuration is required, when needed you can simply specify an IP address using the format that is appropriate to your network type.

This means that when an IP address needs to be specified you can select (as required) from:

  • an IPv6 address
    for example http://[ab12::34c5:6d7:8e90:1234]:4502
  • an IPv4 address
    for example
  • a server name
    for example,
  • the default case of localhost will be interpreted for both IPv4 and IPv6 network installations
    for example, http://localhost:4502

Dynamic Media Add-on Prerequisites

With dynamic media enabled, the system also has additional technical requirements.

Dynamic Media is disabled by default. You can enable Dynamic Media.


The following hardware requirements are applicable for both Linux and Windows:

  • Intel Xeon or AMD Opteron CPU with at least 4 cores
  • 16GB of RAM minimum


If you are using Dynamic Media on Linux, the following prerequisites need to be met: 

  • RedHat Enterprise 5 or CentOS 5.5 and later with latest fix patches
  • 64-bit Operating System
  • Swapping disabled (recommended)
  • SELinux disabled (See note that follows)


If the locale is set such that LC_CTYPE is not equal to en_US.UTF-8, it will prevent dynamic media from working. To see what its value is type "locale" at the command prompt. If it not set to that, then set the LC_CTYPE environment variable to the empty string by typing "export LC_CTYPE=" before running AEM.


Disabling SELinux: Image Serving does not work with SELinux turned on. This option is enabled by default. To remedy this issue, edit the /etc/selinux/config file and change the SELinux value from:

SELINUX=enforcing to SELINUX=disabled


NUMA Architecture: Systems with processors featuring AMD64 and Intel EM64T are typically configured as non-uniform memory architecture (NUMA) platforms, which means that the kernel constructs multiple memory nodes at boot-time rather than constructing a single memory node.

The multiple node construct can result in memory exhaustion on one or more of the nodes before other nodes become exhausted. When memory exhaustion happens the kernel can decide to kill processes (for example, the Image Server or Platform Server) even though there is available memory.

Therefore, Adobe recommends that if you are running such a system you turn off NUMA using the numa=off boot option to avoid the kernel killing these processes.


Hostname of server must be resolvable: Make sure that the hostname of the server is resolvable to an IP address. If that is not possible, please add the fully qualified hostname and the IP address to/etc/hosts:

<ip address> <fully qualified hostname>


  • Microsoft Windows Server (2008 R2, 2012, 2012 R2)
  • Swap space equal to at least twice the amount of physical memory (RAM)

To use Dynamic Media on Windows, Microsoft Visual Studio 2010, 2013, and 2015 redistributables must be installed.


  • 10.9.x and later
  • Only supported for trial and demo purposes

Software support for AEM Forms PDF Generator

AEM Forms PDF Generator supports only English, French, German, and Japanese versions of the supported operating systems and applications.

In addition:

  • PDF Generator is not supported on Windows 2008 R1. PDF Generator on Windows requires Windows 2008 R2 SP1 and later.
  • PDF Generator requires Acrobat DC to perform the conversion.
  • AEM forms on JEE supports only 32-bit editions of supported software.
  • The OCR PDF (Searchable PDF), Optimize PDF, and Export PDF features are supported only on Microsoft Windows.
  • The HTML2PDF service is supported on SUSE Linux Enterprise Server 11 and Red Hat Enterprise Linux Server & AP 6.


Supported Formats for Conversion to PDF

Adobe® Acrobat® DC Pro

XPS, image formats (BMP, GIF, JPEG, JPG, TIF, TIFF, PNG, JPF, JPX, JP2, J2K, J2C, JPC), HTML, HTM, DWG, DXF, and DWF

Microsoft® Office 2013 DOC, DOCX, XLS, XLSX, PPT, PPTX, RTF, and TXT

Microsoft® Office 2010


Microsoft® Project 2010


OpenOffice 3.4


OpenOffice 3.3


XMP metadata write-back Prerequisites

XMP write-back is supported and enabled for the following platforms and file formats:

Operating Systems

  • Linux (32bit, needs 32bit application support on 64bit systems)
  • Windows Server
  • Oracle Solaris
  • Mac OS X
File Formats
  • JPEG
  • PNG
  • TIFF
  • PDF
  • INDD

Copyright, Licenses and Disclaimers

Please read the Copyright, Licenses and Disclaimers page for all details.