DocumentationExperience Cloud KCS

Migrating Adobe Experience Manager from Red Hat JBoss to Adobe-bundled JBoss

Last update: October 2, 2026

This article outlines the steps and considerations for migrating Adobe Experience Manager (AEM) from Red Hat JBoss to the Adobe-bundled JBoss distribution to ensure a smooth and supported transition.

Description description

Environment

  • Adobe Experience Manager (all supported versions)
  • Existing deployment on Red Hat JBoss
  • Target deployment on Adobe-bundled JBoss

Issue/Symptoms

  • Organizations running Adobe Experience Manager (AEM) on Red Hat JBoss may need to migrate to the Adobe-bundled JBoss distribution for support or compatibility reasons.
  • The migration requires careful planning to preserve all configurations and customizations.
  • Requirement to standardize on the Adobe-bundled JBoss for support or compatibility.
  • Need for a checklist of prerequisites and migration steps.

Cause

Migration is typically required when organizations align with Adobe’s supported JBoss distribution or need to ensure compatibility with future AEM updates.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Review compatibility

    • Confirm that the Adobe-bundled JBoss version is compatible with your current AEM version. Refer to the official AEM documentation for supported versions.

  2. Obtain the Adobe-bundled JBoss package

    • Download the official Adobe-bundled JBoss distribution package for your AEM version from the Adobe Experience League portal or contact Adobe Support if you do not have access.

  3. Backup existing environment

    • Take full backups of your current AEM instance, including the repository, configuration files, and any custom code or integrations.
    • Ensure you have a documented rollback plan in case of migration issues.

  4. Document current configuration

    • Record all custom configurations, JVM options, and deployed modules from your Red Hat JBoss environment.

  5. Prepare the target environment

    • Install the Adobe-bundled JBoss on your target system following the official Adobe installation guide for your AEM version.

  6. Migrate configuration and deployments

    • Apply your documented configurations and deploy custom modules to the new JBoss instance.
    • Validate that all required datasources, security settings, and integrations are correctly configured.

  7. Test the environment

    • Start AEM on the Adobe-bundled JBoss and verify application functionality.
    • Check logs for errors and confirm that all services are running as expected.

  8. Verification

    • Ensure all business-critical features and integrations are functioning as intended before proceeding to production.

For detailed installation and migration instructions, refer to the official Adobe Experience Manager documentation on Experience League.

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