Technical Requirements

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 itself, please contact the platform vendor directly.

Prerequisites

Minimum requirements for installing Adobe Experience Manager:

• Installed Java Platform, Standard Edition JDK, or other supported Java Virtual Machines
• Experience Manager Quickstart file (Standalone JAR or web-application deployment WAR)

Minimum Sizing Requirements

Minimum requirements for running Adobe Experience Manager:

• 5 GB free disk space in the installation directory
• 2 GB memory

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 recommended configurations and other configurations.

Supported Configurations

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

Unsupported Configurations

Supported Platforms

Java Virtual Machines

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:

1. Oracle has moved to a “Long Term Support” (LTS) model for Oracle Java SE products. Java 9 and 10 are non-LTS releases by Oracle (see Oracle Java SE support roadmap). Adobe will only provide support for LTS releases of Java to run AEM in production.

2. The IBM JRE is only supported in conjunction with WebSphere Application Server.

3. 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. See the Oracle Java support for Adobe Experience Manager Q&A for more information.

Storage & Persistence

Various options exist to deploy the repository of Adobe Experience Manager. See the following list for supported technologies and storage options.

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.
4. Not supported for AEM Forms.
5. MongoDB Enterprise 3.6 is supported starting with AEM version 6.4.2.0.
6. Support for MongoDB 3.4 has reached end of life (EOL), while MongoDB 3.6 is expected to reach EOL on April 30th, 2021. Please note that Adobe will only be providing support for AEM product related issues going forward.

Servlet Engines / Application Servers

Adobe Experience Manager can run either as a standalone 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, but below Servlet 4.0.

1. Not supported for AEM Forms.

Server Operating Systems

Adobe Experience Manager works with the following server platforms:

1. Linux Kernel 2.6, 3.x and 4.x includes derivatives from Red Hat distribution, including Red Hat Enterprise Linux, CentOS, Oracle Linux and Amazon Linux. AEM Forms add-on features are only supported on CentOS 7 and Red Hat Enterprise Linux 7.
2. AEM Assets: Please see the section Support for XMP metadata write-back
3. AEM Assets: No support for Dynamic Media Imaging. Dynamic Media Video is supported.
4. AEM Forms is supported only on Ubuntu 16.04 LTS.
5. AEM Assets: No support for Raw file transformation
6. AEM Forms: No support for production environment
7. AEM Assets: No support for enhanced PDF Rasterizer
8. AEM Forms: Not supported

Virtual & Cloud Computing Environments

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. Please check out our 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, we strongly recommend 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.

Dispatcher Platforms (Web Servers)

The Dispatcher is the caching and load balancing component. Download the latest Dispatcher version. Experience Manager 6.4 requires Dispatcher version 4.3.1 or higher.

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

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. If in doubt, please ask Adobe for confirmation of the support level related to the respective server product. Following cases:

   1. The HTTP server was built using only official Apache source distributions, or
   2. The HTTP server was delivered as part of the operating system on which it is running. Examples: IBM HTTP Server, Oracle HTTP Server

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

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 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.

1. Extended Support Release of Firefox Learn more about this on mozilla.org
2. support for Apple iPad

Supported Browsers for Websites

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.

WebDAV Clients

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:

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. You can simply specify an IP address using the format that is appropriate to your network type, if neccessary.

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

• an IPv6 address

  for example https://[ab12::34c5:6d7:8e90:1234]:4502

• an IPv4 address

  for example https://123.1.1.4:4502

• a server name

  for example, https://www.yourserver.com:4502

• the default case of localhost will be interpreted for both IPv4 and IPv6 network installations

  for example, http://localhost:4502

Requirements for AEM Dynamic Media Add-on

AEM Dynamic Media is disabled by default. See Enabling Dynamic Media.

With Dynamic Media enabled, the following additional system requirements apply:

Hardware

The following hardware requirements apply to both Linux and Windows operating systems:

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

Linux

Using Dynamic Media on Linux requires the following prerequisites:

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

Windows

• Microsoft Windows Server 2016
• 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 for x64 and x86 must be installed.

x64

• The Microsoft Visual Studio 2010 redistributable can be found at https://www.microsoft.com/en-us/download/details.aspx?id=13523
• The Microsoft Visual Studio 2013 redistributable can be found at https://www.microsoft.com/en-us/download/details.aspx?id=40784
• The Microsoft Visual Studio 2015 redistributable can be found at https://www.microsoft.com/en-us/download/details.aspx?id=48145

x86

• The Microsoft Visual Studio 2010 redistributable can be found at https://www.microsoft.com/en-in/download/details.aspx?id=5555
• The Microsoft Visual Studio 2013 redistributable can be found at https://www.microsoft.com/en-in/download/details.aspx?id=40769
• The Microsoft Visual Studio 2015 redistributable can be found at https://www.microsoft.com/en-us/download/details.aspx?id=52685

MacOS

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

Requirements for AEM Forms PDF Generator

Requirements for AEM Forms Designer

• Microsoft® Windows® 2012 Server R2, Microsoft® Windows® 2016 Server, Microsoft® Windows® 2019 Server, Microsoft® Windows® 10
• 1 GHz or faster processor with support for PAE, NX, and SSE2.
• 1 GB of RAM for 32-bit or 2 GB of RAM for 64-bit OS
• 16 GB disk space for 32-bit or 20 GB disk space for 64-bit OS
• Graphics memory - 128 MB of GPU (256 MB recommended)
• 2.35 GB of available hard-disk space
• 1024 X 768 pixels or greater monitor resolution
• Video hardware acceleration (optional)
• Acrobat Pro DC, Acrobat Standard DC, or Adobe Acrobat Reader DC
• Administrative privileges to install Designer

Requirements for AEM Assets XMP metadata write-back

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

Operating Systems

• Linux (32-bit, needs 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.

• Windows Server

• Oracle Solaris

• Mac OS X (64-bit)

File Formats

• JPEG
• PNG
• TIFF
• PDF
• INDD
• AI
• EPS

Requirements for AEM Screens Player

The AEM Screens Player Version 3.3.x supports following operating systems:

• Microsoft Windows 10 Enterprise LTSB
• Google Chome OS 62+
• Google Android 5.1.1 with updated Android System WebView Version 52+
• Apple iOS 10.3+
• Apple macOS 10.12+