Oracle JDK licensing verification for Adobe Experience Manager

Licensing ambiguity can occur when teams need to confirm whether Oracle Java used to run the application is already covered or requires separate licensing. The uncertainty commonly extends to supported JDK versions, approved download sources, and whether Java use outside the application changes the licensing position.

Description description

Environment

  • Product: Adobe Experience Manager On-Premise, Adobe Experience Manager as a Cloud Service
  • Version: 6.5

Issue/Symptoms

  • Uncertainty from ITAM, procurement, or compliance teams about Oracle Java SE licensing requirements
  • Questions about whether Oracle Java requires a separate license
  • Confusion about supported JDK versions such as JDK 8 or JDK 11
  • Questions about approved download sources such as Adobe portal or Oracle site
  • Licensing ambiguity without any runtime errors

Cause

This issue occurs because Oracle Java licensing for AEM depends on the deployment model (On-Prem or Cloud), which often creates confusion. Adobe includes Oracle Java usage for AEM when the binaries come from approved sources, but this isn’t always clearly understood. Confusion also occurs because OpenJDK isn’t supported for AEM Forms on JEE.

Resolution resolution

To fix this issue, follow these steps:

  1. Identify the AEM deployment model by confirming whether the environment runs AEM 6.5 On-Premise or AEM as a Cloud Service and request the details if they are not available.
  2. Verify the installed Java version on each AEM server by running: java -version
  3. Confirm the output includes Oracle Java details such as Java™ SE Runtime Environment or Oracle Corporation.
  4. Compare the installed Java version with the supported versions listed in official technical requirements documentation and confirm it matches exactly with the supported tables.
  5. Confirm licensing coverage. Oracle Java is included in the Adobe license when used only for AEM (On-Prem or Cloud). If shared with non-AEM applications, separate Oracle licensing may be required.
  6. Check the JDK download source and confirm it was downloaded from the Adobe Software Distribution Portal or from Oracle for supported versions only.
  7. Validate upgrade plans by confirming the target JDK version is supported before upgrading (for example, JDK 11.0.28 for AEM 6.5.23).

Note

Contact Adobe Support if you cannot identify the Java version, the JDK is not listed as supported, compliance teams need written confirmation, or Java runs outside AEM.

recommendation-more-help
experience-cloud-kcs-help-kbarticles