Adobe supports Adobe Experience Manager (AEM) on the platforms as detailed in the following information in this document.
For any issues that are specifically related to the platform, contact the platform vendor.
Depending upon the platform on which you install AEM, there could be different sets of requirements for user management.
Minimum requirements for installing Adobe Experience Manager:
Minimum requirements for running Adobe Experience Manager:
For further information, see the Hardware Sizing Guidelines.
This document lists the supported client and server platforms for Adobe Experience Manager. Adobe provides several levels of support, both for recommended configurations and other configurations.
Adobe recommends these configurations and provides full support as part of the standard software maintenance agreement.
|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 information, contact Adobe Customer Care.|
|Z: Not supported||The configuration is not supported. Adobe does not make any statements about whether the configuration works, and does not support it.|
The application requires a Java Virtual Machine to run, which is provided by the Java Development Kit (JDK) distribution.
Adobe Experience Manager operates with the following versions of the Java Virtual Machines:
It is recommended to track the Security Bulletins from the Java vendor to ensure the safety and security of production environments and install the latest Java Updates.
|Azul Zulu OpenJDK 11 - 64bit||A: Supported |
|Azul Zulu OpenJDK 8 - 64bit||A: Supported |
|Oracle Java SE 11 JDK - 64bit||A: Supported  |
|Oracle Java SE 10 JDK||Z: Not supported |
|Oracle Java SE 9 JDK||Z: Not supported |
|Oracle Java SE 8 JDK - 64bit||A: Supported |
|IBM J9 VM - build 2.9, JRE 1.8.0||A: Supported |
|IBM J9 VM - build 2.8, JRE 1.8.0||A: Supported |
Support and distribution of Azul Zulu Builds of OpenJDK, including all maintenance updates of LTS releases will be supported by Adobe directly for all AEM customers making use of the Azul Zulu Builds of OpenJDK, starting with AEM 6.5 SP9 resp. See the Azul Java support for Adobe Experience Manager Q&A for more information.
Oracle has moved to a “Long Term Support” (LTS) model for Oracle Java SE products. Java 9, Java 10, and Java 12 are non-LTS releases by Oracle (see Oracle Java SE support roadmap). To deploy AEM in production environment, Adobe provides support only for the LTS releases of Java. Support and distribution of the Oracle Java SE JDK, including all maintenance updates of LTS releases beyond the end of the public updates, will be supported by Adobe directly for all AEM customers making use of the Oracle Java SE technology until December 2022. See the Oracle Java support for Adobe Experience Manager Q&A for more information.
The IBM JRE is only supported along with WebSphere Application Server.
Oracle Java SE 11 JDK is not supported for Experience Manager Forms.
Various options exist to deploy the repository of Adobe Experience Manager. See the following list for supported technologies and storage options.
|File system with TAR files
|File system with Datastore
|Store binaries in TAR files on file system
||Binaries||Z: Not supported for production|
|Amazon S3||Binaries||A: Supported|
|Microsoft Azure Blob Storage||Binaries||A: Supported|
|MongoDB Enterprise 4.0||Repository||A: Supported
|MongoDB Enterprise 3.6||Repository||Z: Not supported|
|MongoDB Enterprise 3.4||Repository||Z: Not supported|
|IBM DB2 10.5||Repository & Forms Database||R: Restricted Support
|Oracle Database 12c (12.1.x)||Repository & Forms Database||R: Restricted Support|
|Microsoft SQL Server 2016||Forms Database||A: Supported|
|Apache Lucene (Quickstart built-in)||Search Service||A: Supported|
|Apache Solr||Search Service||A: Supported|
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.
To get the most of your AEM deployment with MongoDB, Adobe recommends licensing the MongoDB Enterprise version to benefit from professional support. See Recommended Deployments for more information.
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 want 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 are third-party software and are not included in the AEM licensing package.
To run AEM 6.5 with a supported relational database, a separate support contract with a database vendor is required. Adobe Customer Care will assist qualifying issues related to the usage of relational databases with AEM 6.5.
Most relational databases are currently supported within Level-R on AEM 6.5, which comes with support criteria and a support program as stated in the Level-R description above.
Adobe Experience Manager can run either as a stand-alone server (the quickstart JAR file) or as web application within a third-party application server (the WAR file).
Minimum Servlet API Version required is Servlet 3.1
|Quickstart built-in Servlet Engine (Jetty 9.4)||A: Supported|
|Oracle WebLogic Server 12.2 (12cR2)||Z: Not supported|
|IBM WebSphere Application Server Continuous Delivery (LibertyProfile) with Web Profile 7.0 and IBM JRE 1.8||R: Restricted Support for new contracts
|IBM WebSphere Application Server 9.0 and IBM JRE 1.8||R: Restricted Support for new contracts
|Apache Tomcat 8.5.x||R: Restricted Support for new contracts
|JBoss EAP 7.2.x with JBoss Application Server||Z: Not supported|
|JBoss EAP 7.1.4 with JBoss Application Server||R: Restricted Support for new contracts
|JBoss EAP 7.0.x with JBoss Application Server||Z: Not supported|
Adobe Experience Manager works with the following server platforms for production environments:
|Linux, based on Red Hat distribution||A: Supported
|Linux, based on Debian distribution incl. Ubuntu||A: Supported
|Linux, based on SUSE distribution||A: Supported|
|Microsoft Windows Server 2019
||R: Restricted Support for new contracts|
|Microsoft Windows Server 2016
||R: Restricted Support for new contracts
|Microsoft Windows Server 2012 R2||Z: Not supported|
|Oracle Solaris 11||Z: Not supported|
|IBM AIX 7.2||Z: Not supported|
Adobe Experience Manager is supported running in a virtual machine on cloud computing environments, such as Microsoft Azure and Amazon Web Services (AWS), in compliance with the technical requirements listed on this page, and according to Adobe’s standard support terms.
Adobe recommends using Adobe Managed Services to deploy AEM on Azure or AWS. Adobe Managed Services provides experts with experience and skills of deploying and operating AEM in these cloud computing environments. See additional documentation on Adobe Managed Services.
In all other cases of deploying AEM on Azure or AWS, or any other cloud computing environment, support from Adobe will be contained to the virtual compute environment in compliance with the technical specifications listed on this page. Any reported issue relative to AEM running in any of these cloud environments will need to be reproducible independently from any cloud service specific to the cloud computing environment, unless the cloud service is specifically supported as part of the technical requirements listed on this page, for example Azure Blob storage or AWS S3.
For recommendations on how to deploy AEM on Azure or AWS, outside of Adobe Managed Services, Adobe strongly recommends working directly with the cloud provider or Adobe partners supporting the deployment of AEM in the cloud environment of your choice. The selected cloud provider or partner will be responsible for the sizing specifications, design and implementation of the architecture., to meet your specific performance, load, scalability, and security requirements.
The Dispatcher is the caching and load balancing component. Download the latest Dispatcher version. Experience Manager 6.5 requires Dispatcher version 4.3.2 or higher.
The following web servers are supported for use with Dispatcher version 4.3.2:
|Apache httpd 2.4.x
|Microsoft IIS 10 (Internet Information Server)||A: Supported|
|Microsoft IIS 8.5 (Internet Information Server)||Z: Not supported|
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. If in doubt, ask Adobe for confirmation of the support level related to the respective server product. Following cases:
Dispatcher is not available for Apache 2.4.x for Windows operating systems.
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 AEM user interface is optimized for 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.
Support for browsers with rapid release cycles:
Mozilla Firefox, Google Chrome and Microsoft Edge 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 UI
||Support for Classic UI|
|Google Chrome (Evergreen)||A: Supported||A: Supported|
|Microsoft Edge (Evergreen)||A: Supported||A: Supported|
|Microsoft Internet Explorer 11||Z: Not supported||Z: Not supported|
|Mozilla Firefox (Evergreen)||A: Supported||A: Supported|
|Mozilla Firefox last ESR ||A: Supported||A: Supported|
|Apple Safari on macOS (Evergreen)||A: Supported||A: Supported|
|Apple Safari 11.x on macOS||Z: Not supported||Z: Not supported|
|Apple Safari on iOS 12.x||A: Supported ||Z: Not supported|
|Apple Safari on iOS 11.x||Z: Not supported||Z: Not supported|
Generally, browser support for websites rendered by AEM Sites depends on the implementation of AEM page templates, design and component output, and is therefore in control of the party implementing these parts.
Microsoft Windows 7+
To successfully connect with Microsoft Windows 7+ 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:
Locate the registry subkey:
Add the BasicAuthLevel registry entry to this subkey using a value of 2 or more.
To improve responsivness of the WebDav Client under Windows - see Microsoft Support KB 2445570
This section provides special notes and more detailed information about running Adobe Experience Manager and its add-ons.
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. You can simply specify an IP address using the format that is appropriate to your network type, if necessary.
This means that when an IP address needs to be specified you can select (as required) from:
an IPv6 address
an IPv4 address
a server name
the default case of
localhost will be interpreted for both IPv4 and IPv6 network installations
AEM Dynamic Media is disabled by default. See here to enable Dynamic Media.
With Dynamic Media enabled, the following additional technical requirements apply.
These system requirements only apply if you use Dynamic Media - Hybrid mode; Dynamic Media - Hybrid mode has an embedded image server, which is only certified on certain operating systems.
For Dynamic Media customers who run Dynamic Media - Scene7 mode (that is, dynamicmedia_scene7 runmode), there are no additional system requirements; only the same system requirements as AEM. Dynamic Media - Scene7 mode architecture uses the cloud-based image service and not the service embedded in AEM.
The following hardware requirements are applicable for both Linux and Windows:
If you are using Dynamic Media on Linux, the following prerequisites need to be met:
If the locale is set such that LC_CTYPE is not equal to
en_US.UTF-8, it prevents 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:
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 that you turn off NUMA using the numa=off boot option to avoid the kernel killing these processes.
Server host name must resolve: Ensure that the host name of the server is resolvable to an IP address. If that is not possible, add the fully qualified host name and the IP address to /etc/hosts:
<ip address> <fully qualified hostname>
To use Dynamic Media on Windows, install Microsoft Visual Studio 2010, 2013, and 2015 redistributables for x64 and x86.
For Windows x64:
For Windows x86:
Supported Formats for Conversion to PDF
|Acrobat 2017 classic track latest version||XPS, image formats (BMP, GIF, JPEG, JPG, TIF, TIFF, PNG, JPF, JPX, JP2, J2K, J2C, JPC), HTML, HTM, DWG, DXF, and DWF|
|Microsoft® Office 2016||DOC, DOCX, XLS, XLSX, PPT, PPTX, RTF, and TXT|
|WordPerfect X7||WP, WPD|
|Microsoft® Office Visio 2016
|Microsoft® Publisher 2016
|Microsoft® Project 2016
|OpenOffice 4.1.2||ODT, ODP, ODS, ODG, ODF, SXW, SXI, SXC, SXD, XLS, XLSX, DOC, DOCX, PPT, PPTX,image formats (BMP, GIF, JPEG, JPG, TIF, TIFF, PNG, JPF, JPX, JP2, J2K, J2C, JPC), HTML, HTM, RTF, and TXT|
PDF Generator supports only English, French, German, and Japanese versions of the supported operating systems and applications.
PDF Generator requires 32-bit version of Acrobat 2017 classic track version 17.011.30078 or later to perform the conversion.
PDF Generator supports only the 32-bit Retail version of Microsoft Office Professional Plus and other software required for conversion.
PDF Generator does not support Microsoft Office 365.
PDF Generator conversions for OpenOffice are supported only on Windows and Linux.
The OCR PDF, Optimize PDF, and Export PDF features are supported only on Windows.
A version of Acrobat is bundled with AEM Forms to enable PDF Generator functionality. The bundled version should only be accessed programmatically only with AEM Forms, during the term of the AEM Forms license, for use with AEM Forms PDF Generator. For more information, refer to AEM Forms product description as per your deployment (On-Premise or Managed Services)”
PDF Generator service does not support Microsoft Windows 10.
XMP write-back is supported and enabled for the following platforms and file formats:
Linux (32-bit and 32-bit application support on 64-bit systems). For steps to install 32-bit client libraries, see How to enable XMP extraction and write-back on 64-bit RedHat Linux.
Mac OS X (64-bit)
File Formats: JPEG, PNG, TIFF, PDF, INDD, AI, and EPS.
XMPFilesProcessor process requires library GLIBC_2.14 to work. Use a Linux kernel that contains GLIBC_2.14, for example Linux kernel version 3.1.x. It improves performance for processing assets that contain a large amount of metadata, like PSD files. Using a previous version of GLIBC leads to error in logs starting with
com.day.cq.dam.core.impl.handler.xmp.NCommXMPHandler Failed to read XMP.