DocumentationExperience Cloud KCS

Migrating AEM Forms from Red Hat JBoss to Adobe-bundled JBoss

Last update: October 26, 2026

This article outlines how to migrate Adobe Experience Manager (AEM) Forms from a Red Hat JBoss installation to the Adobe-bundled JBoss environment and resolve common migration issues.

Description description

Environment

Adobe Experience Manager (AEM) Forms (all versions)

Issue/Symptoms

Organizations using AEM Forms on Red Hat JBoss may need to migrate to the Adobe-bundled JBoss environment. Migration can lead to configuration mismatches and deployment issues, particularly with datasource settings, credential store aliases, and application deployment.

During migration from Red Hat JBoss to Adobe-bundled JBoss, the following issues can occur:

  • Datasource configuration errors due to mismatched credential store aliases.
  • Incorrect SQL Server connection URL syntax, such as using ::1433 instead of :1433.
  • Deployment status issues for required EAR files.
  • Configuration Manager’s Verify Server Connection step fails with HTTP 401 or HTTP 404 errors when accessing the Configuration Manager startup URL.
  • Errors such as RMServiceEJBHelper ClassNotFoundException or DSC invocation errors occur after startup.

Cause

Migration can expose configuration mismatches, such as credential store aliases and connection URL syntax, and missing resources required by Configuration Manager. Address these issues to ensure a successful migration and operational environment.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Prepare for migration by backing up your existing Red Hat JBoss environment and all relevant configuration files, and documenting all custom configurations, datasources, and deployed applications.
  2. Install the Adobe-bundled JBoss environment for AEM Forms by following the official Adobe documentation for your version.
  3. Migrate datasource configurations by updating the datasource configuration files to reference the correct credential store aliases. If the Adobe migration script creates new aliases, ensure your datasources reference these aliases, or add the required alias to your credential store with the correct database password. Correct any SQL Server connection URL syntax errors and ensure the port is specified as :1433, not ::1433.
  4. Deploy application components by starting JBoss using the appropriate command for your configuration file and environment. Manually deploy the required EAR files and verify that all deployments show status OK.
  5. Validate database connectivity by testing all configured datasources and confirming successful connections.
  6. Verify the server and application status by accessing the AEM Forms admin UI and checking that all bundles are active on the /lc/system/console/bundles page. Use Configuration Manager to run the Verify Server Connection step. If you encounter HTTP 401 or HTTP 404 errors at the Configuration Manager startup URL, confirm that the resource exists and that the repository path is correct. If the resource is missing but DSC components are already deployed and active, this may not impact current implementations. The issue may resolve after the next patch installation and a full Configuration Manager run.
  7. Address remaining errors by investigating any ClassNotFoundException or DSC invocation errors, reviewing the logs, and ensuring all required components are deployed.

Verify migration success by confirming that all services are running, bundles are active, and database connections are successful.

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