To install Adobe Experience Manager you need:
Adobe supports Experience Manager on the following platforms according to the information listed below.
For any issues that are specifically related to the platform itself you will need to contact the platform vendor directly.
- 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)
If you are using Dynamic Media, you also need to meet the requirements outlined in the Dynamic Media Prerequisites section.
The following are the minimum requirements:
- 4 GB free disk space in the installation directory
- 1.5 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.
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.
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.|
In previous releases, Adobe used three different support levels for the fully supported configurations (A,B,C). Currently the supported platforms are all on level A.
Adobe cannot guarantee that the configuration works as expected, and support for these configurations is not included in the standard software maintenance agreement.
|D: Validated, optional support available.||This configuration has been validated by Adobe or a third party, or it is or has been in productive use. This platform is only sporadically tested by Adobe or third parties. Adobe offers optional platform support service agreements for this configuration.|
|E: Expected to work||The configuration is expected to work, and there are no reports to the contrary. Adobe offers optional platform support service agreements for this configuration.|
|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 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.
|Oracle SE 8 JRE 1.8.x||Z: Not supported|
|Oracle SE 7 JRE 1.7.x||A: Supported|
|Oracle SE 6 JRE 1.6.x||Z: Not supported|
|Oracle SE 5 JRE 1.5.x||Z: Not supported|
|IBM J9 VM (build 2.6, JRE 1.7.0)||A: Supported|
|IBM J9 VM (build 2.4 & 2.6, JRE 1.6.0)||A: Supported|
|IBM J9 VM (build 2.3, J2RE 1.5.0)||Z: Not supported|
|HP JRE 7.0.x||A: Supported|
|HP JRE 6.0.x||A: Supported|
|HP JRE 5.0.x||Z: Not supported|
- The IBM JRE is only supported on IBM server platforms (AIX), or in conjunction with WebSphere Application Server.
- The HP JRE is only supported on HP server platforms (HP-UX).
There are various options to deploy the repository of Adobe Experience Manager. Following a list of supported technologies and storage options.
|File System (1)||Repository Microkernel (TAR files)||A: Supported|
|File System (1)||to store binaries||A: Supported|
|MongoDB 2.6||Repository Microkernel
|Amazon S3||to store binaries||A: Supported|
|Apache Solr||to use as internal search engine||A: Supported|
- '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.
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
For production use, Adobe offers optional support for these platforms:
|Quickstart built-in Servlet Engine (Jetty 8.1)||A: Supported|
|Oracle WebLogic Server 12.1 (12c)||A: Supported|
|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 7||D: Validated|
|Apache Tomcat 6||Z: Not supported|
|JBoss Application Server 7.1||A: Supported|
|JBoss Application Server 5||Z: Not supported|
|Jetty 7-9||E: Expected to work|
Adobe Experience Manager works with the following server platforms:
|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,6)|
|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 11||E: Expected to work|
|Apple OS X Server||D: Validated (6)|
- Linux Kernel 2.6 and 3.x includes derivatives from Red Hat distribution, including Red Hat Enterprise Linux, CentOS, Oracle Linux and Amazon Linux.
- Please see the section Support for XMP metadata write-back
- No support for Dynamic Media Imaging. Dynamic Media Video is supported.
- No support for XFA based adaptive forms, XFA to PDF and/or HTML conversion (Experience Manager Forms), and AEM forms add-on features.
- No support for Advanced Raw file transformation (Experience Manager Assets)
- Not supported for AEM forms.
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
- Microsoft Azure Virtual Machines
- Rackspace Cloud
- VMware vCloud
The Dispatcher is the caching and load balancing component. Download the latest Dispatcher version from Adobe PackageShare. Experience Manager 6 requires Dispatcher version 4.1.7 or higher.
The following web servers are supported for use with a Dispatcher version 4.1.7:
|Apache httpd 2.4||A: Supported (1)|
|Apache httpd 2.2||A: Supported (1)|
|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.
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.
User interface performance
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 Internet Explorer 11||A: Supported||A: Supported|
|Microsoft Internet Explorer 10||A: Supported||A: 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 31||A: Supported||A: Supported|
|Mozilla Firefox 24 (ESR) (3)||A: Supported||A: Supported|
|Google Chrome 36+||A: Supported||A: Supported|
|Apple Safari 7.0 (OS X)
||A: Supported||A: Supported|
|Apple Safari 6.0 (OS X)||A: Supported||A: Supported|
|Apple Safari 7.0 (iOS) (5)||Z: Not supported||A: Supported|
|Apple Safari 6.0 (iOS) (4)(5)||Z: Not supported||A: Supported|
- (3) Mozilla Firefox 24 are Extended Support Releases. Learn more about this on mozilla.org
- (4) There is no native support of file upload in iOS 5; support for this starts with iOS 6. Therefore AEM supports file upload starting from iOS 6.
- (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
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.
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:
- 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, 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 http://18.104.22.168:4502
- a server name
for example, http://www.yourserver.com:4502
- the default case of localhost will be interpreted for both IPv4 and IPv6 network installations
for example, http://localhost:4502
With dynamic media enabled, the system also has additional technical requirements.
Dynamic Media is enabled by default. You can explicity disable 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)
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, the Microsoft Visual Studio redistributable must be installed. The redistributable can be found at: http://www.microsoft.com/en-us/download/details.aspx?id=13523.
- 10.9.x and later
- Only supported for trial and demo purposes
- No support for XFA based adaptive forms, XFA to PDF and/or HTML conversion (Experience Manager Forms), and AEM forms add-on features.
XMP write-back is supported and enabled for the following platforms and file formats:
- Linux (32bit, needs 32bit application support on 64bit systems)
- Windows Server
- Oracle Solaris
- Mac OS X
Please read the Copyright, Licenses and Disclaimers page for all details.