DocumentationExperience Cloud KCS

AEM Forms JEE upgrade guidance for version, OS, JBoss, and platform compatibility

Last update: July 7, 2026

Customers upgrading AEM Forms on JEE — moving to a newer service pack, migrating between RHEL versions, or choosing between 6.5.x and 6.5 LTS — need authoritative confirmation of supported platforms before they proceed. AEM Forms on JEE enforces strict compatibility across the OS, JBoss, Java, and database layers, and the supported combinations live in Adobe’s platform matrix, but need mapping to your specific environment. Skipping that validation risks installing unsupported binaries or committing to an upgrade path that can’t succeed. Confirming your OS, JBoss, and Java combination against the matrix, obtaining the correct installers, and applying the service pack or LTS upgrade in sequence resolves the uncertainty.

Description description

Environments:

  • Adobe Experience Manager Forms on JEE
  • Adobe Experience Manager 6.5 (on-premises)
  • Adobe Experience Manager 6.5 LTS
  • JBoss EAP 7.4.x and JBoss EAP 8
  • Red Hat Enterprise Linux and Windows Server

Issue/Symptoms:

  • There’s uncertainty about which AEM Forms versions support specific OS platforms such as RHEL 8, RHEL 9, and Windows Server 2022.
  • There’s uncertainty about compatible JBoss EAP or Java versions for a specific AEM Forms release, such as JBoss 7.4.22 with SP22, or Java 17 and 21 with LTS.
  • The request is for authoritative confirmation of supported platforms, installer availability, prerequisites, and upgrade sequencing rather than break/fix troubleshooting.

Root cause:

AEM Forms on JEE enforces strict compatibility across the OS, JBoss, Java, and database layers, so combinations need validation before you upgrade or apply a service pack. Adobe documents the supported combinations in its platform matrix, but they need proper interpretation and mapping to your environment. Without confirming supported combinations, you risk installing unsupported binaries or planning an upgrade path that can’t succeed.

Resolution resolution

Follow these steps to resolve the issue:

  1. Identify your current AEM Forms JEE version and platform components. Collect the OS version, JBoss EAP version, Java version, and database type. Confirm them by running java -version, checking the JBoss EAP console version, and running OS release commands such as cat /etc/redhat-release on RHEL.
  2. Determine whether your target is a service pack upgrade or an LTS migration. 6.5 LTS requires Java 17 or 21 and JBoss EAP 8, while 6.5.x service pack upgrades stay on Java 8 or 11 and JBoss 7.4.x. This tells you whether to target 6.5.24 (SP24) or 6.5 LTS.
  3. Validate platform support using the official Supported Platforms Matrix. Confirm your OS (RHEL 8, RHEL 9, or Windows Server 2022) and JBoss version appear in the matrix for your target version. If your platform isn’t listed, select an OS and JBoss version that’s explicitly supported before upgrading.
  4. For OS migrations (RHEL 7 to RHEL 8, or RHEL 8 to RHEL 9), confirm feasibility. RHEL 8 requires SP11 or later, and RHEL 9 supports SP23 and SP24. Match your target OS to the supported versions in the matrix. If your version doesn’t support the target OS, plan an out-of-place migration using a new server.
  5. Download the correct full installer and service pack from Adobe Software Distribution, including the SP23 full installer, the SP24 patch, and the Forms add-ons. File names match patterns such as aemforms_server_6_5_0_jboss_all_unix.tar.gz or adobe-aem-forms-jee-servicepack-6.5.24.0-win-jboss.zip. If the files don’t appear in Software Distribution, confirm your Adobe ID has the correct entitlements in the Admin Console.
  6. Prepare for the upgrade. Back up the CRX directories, GDS, TEMP, and database, and confirm the backups exist with timestamps before you proceed.
  7. Install the new AEM Forms JEE full installer. Start JBoss and confirm that /lc loads. If deployment fails, check the JBoss logs for deployment errors and validate the OS libraries.
  8. Apply the latest service pack (SP24) and Forms add-ons. Install the SP24 patch for JBoss on Linux or Windows, then install the SP24 OSGi components (servlet fragment, service pack, and Forms add-on). Check /lc/system/console/bundles to confirm the bundles stop producing rolling errors. If they don’t, reinstall the servlet fragment or check error.log for missing dependencies.
  9. For JBoss upgrades, verify the required environment variables. Set DISABLE_JDK_SERIAL_FILTER = true when upgrading JBoss EAP 7.4.x, then confirm JBoss starts without serialization errors. If serialization errors persist, confirm the variable is exported correctly in the JBoss startup script.
  10. Validate the upgraded environment. Start JBoss, access /adminui, and test key modules such as PDF Generator, Workbench connectivity, and Reader Extensions. Check the error.log for new stack traces or rolling messages.
recommendation-more-help
experience-cloud-kcs-help-kbarticles