Technical Requirements

Adobe supports (AEM) Adobe Experience Manager on the platforms as detailed in the following information in this document.

For any issues that are related to the platform, contact the platform vendor.

Prerequisites

Minimum requirements for installing Adobe Experience Manager:

• Installed Java™ Platform, Standard Edition JDK, or other supported Java™ Virtual Machines
• Experience Manager Quickstart file (Stand-alone 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

For further information, see the Hardware Sizing Guidelines.

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, Java™ 10, and Java™ 12 are non-LTS releases by Oracle (see Oracle Java™ SE support roadmap). To deploy AEM in a 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, is supported by Adobe directly for all AEM customers that use the Oracle Java™ SE technology. See the Java™ support policy for Adobe Experience Manager.
   Important: Oracle Java™ 11 is supported until September 2026 at a minimum. Support for Oracle Java™ 17 is in preparation.

2. The IBM® JRE is only supported along with WebSphere® Application Server.

3. Azul Zulu OpenJDK LTS versions are supported for on-premises AEM deployments starting with version 6.5 SP9. Support and distribution of the Azul Zulu JDK LTS versions must be licensed directly from Azul by Adobe customers.

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. Includes network storage technology. Mind that file system performance might vary and influences the overall performance. Load test AEM with the network/remote file system.
2. MongoDB Enterprise versions 4.2 and 4.4 require AEM 6.5 SP9 as a minimum.
3. MongoDB Sharding is not supported in AEM.
4. MongoDB Storage Engine WiredTiger is supported only.
5. Supported for AEM Forms upgrade customers. Not supported for new installations.
6. Applicable AEM Forms only:
   • Removed support for Oracle Database 12c and added support for Oracle Database 19c.
   • Removed support for Microsoft® SQL Server 2016 and added support for Microsoft® SQL Server 2019.

Servlet Engines / Application Servers

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

The minimum Servlet API Version required is Servlet 3.1

1. Recommended for deployments with AEM Forms.
2. Starting AEM 6.5 deployments on application servers moves to Restricted Support. Existing customers can upgrade to AEM 6.5 and keep using application servers. For new customers, it comes with support criteria and a support program as stated in the Level-R description above.
3. Applicable AEM Forms only:
   • Removed support for JBoss® EAP 7.1.4 and added support for JBoss® EAP 7.4.10.

Server Operating Systems

Adobe Experience Manager works with the following server platforms for production environments:

1. Linux® Kernel 2.6, 3. x, 4. x, and 5. 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, Red Hat® Enterprise Linux® 7, Red Hat® Enterprise Linux® 8, and Red Hat® Enterprise Linux® 9.
2. AEM Forms is supported on Ubuntu 20.04 LTS.
3. Linux® distribution supported by Adobe Managed Services.
4. Microsoft® Windows production deployments are supported for customers upgrading to 6.5 and for non-production usage. New deployments are on-request for AEM Sites and Assets.
5. AEM Forms is supported on Microsoft® Window Server without the Support-Level R restrictions.
6. AEM Forms removed support for Microsoft® Windows Server 2016.

Virtual & Cloud Computing Environments

Adobe Experience Manager is supported running in a virtual machine on cloud computing environments. These environments include as Microsoft® Azure and Amazon Web Services (AWS), running in compliance with the technical requirements listed on this page, and according to Adobe’s standard support terms.

For a cloud-native environment, review the latest offering from the AEM product line: Adobe Experience Manager as a Cloud Service. See Adobe Experience Manager as a Cloud Service Documentation for details.

Adobe also offers 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 is contained to the virtual compute environment. That virtual environment must be run in compliance with the technical specifications listed on this page. Any reported issue relative to AEM running in any of these cloud environments must be reproducible independently from any cloud service specific to the cloud computing environment. That is, unless the cloud service is 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 recommends working directly with the cloud provider. Or, working with Adobe partners supporting the deployment of AEM in the cloud environment of your choice. The selected cloud provider or partner is 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.5 requires Dispatcher version 4.3.2 or higher.

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

1. Web servers built based on the Apache httpd source code have as much 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. The 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 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 the control of the party implementing these parts.

WebDAV Clients

Microsoft® Windows 7+

When connecting with Microsoft® Windows 7+ to an AEM instance that is not secured with SSL, basic authentication over an unsecured network must be enabled in Windows. It 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.

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

When an IP address must be specified, you can select (as required) from the following:

• 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 is interpreted for both IPv4 and IPv6 network installations. For example, https://localhost:4502

Requirements for AEM Dynamic Media Add-on

AEM Dynamic Media is disabled by default. See here to enable Dynamic Media.

With Dynamic Media enabled, the following additional technical requirements apply.

Hardware

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

• Intel Xeon® or AMD® Opteron CPU with at least four cores
• At least, 16 GB of RAM

Linux®

If you are using Dynamic Media on Linux®, the following prerequisites must be met:

• Red Hat® 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, install Microsoft® Visual Studio 2010, 2013, and 2015 redistributable for x64 and x86.

For Windows x64:

• Get Microsoft® Visual Studio 2010 redistributable at https://www.microsoft.com/en-us/download/details.aspx?id=26999
• Get Microsoft® Visual Studio 2013 redistributable at https://www.microsoft.com/en-us/download/details.aspx?id=40784
• Get Microsoft® Visual Studio 2015 redistributable at https://www.microsoft.com/en-us/download/details.aspx?id=48145

For Windows x86:

• Get Microsoft® Visual Studio 2010 redistributable at https://www.microsoft.com/en-us/download/details.aspx?id=26999
• Get Microsoft® Visual Studio 2013 redistributable at https://www.microsoft.com/en-in/download/details.aspx?id=40769
• Get Microsoft® Visual Studio 2015 redistributable 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

Software support for PDF Generator

Requirements for AEM Forms Designer

• Microsoft® Windows® 2016 Server, Microsoft® Windows® 2019 Server, or 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
• Microsoft Visual C++ 2019 (VC 14.28 or greater) 32-bit runtime

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 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 Red Hat® Linux®.

  • Windows Server

  • macOS X (64-bit)

• File Formats: JPEG, PNG, TIFF, PDF, INDD, AI, and EPS.

Requirements for AEM Assets to process metadata-heavy assets on Linux®

The XMPFilesProcessor process requires the 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.