Chapter 3. Tools to Assist in Migration

3.1. Use Red Hat Application Migration Toolkit to Analyze Applications for Migration

Red Hat Application Migration Toolkit (RHAMT) is an extensible and customizable rule-based set of tools that helps simplify migration of Java applications. It analyzes the APIs, technologies, and architectures used by the applications you plan to migrate and provides detailed migration reports for each application. These reports provide the following information.

  • Detailed explanations of the migration changes needed
  • Whether the reported change is mandatory or optional
  • Whether the reported change is complex or trivial
  • Links to the code requiring the migration change
  • Hints and links to information about how to make the required changes
  • An estimate of the level of effort for each migration issue found and the total estimated effort to migrate the application

You can use RHAMT to analyze the code and architecture of your JBoss EAP 6 applications before you migrate them to JBoss EAP 7. The RHAMT rule set for migration from JBoss EAP 6 to JBoss EAP 7 reports on XML descriptors and specific application code and parameters that need to be replaced by an alternative configuration when migrating to JBoss EAP 7.

For more information about how to use Red Hat Application Migration Toolkit to analyze your JBoss EAP 6 applications, see the Red Hat Application Migration Toolkit Getting Started Guide.

3.2. Use the JBoss Server Migration Tool to Migrate Server Configurations

The JBoss Server Migration Tool is the preferred method to update your server configuration to include the new features and settings in JBoss EAP 7 while keeping your existing configuration. The JBoss Server Migration Tool reads your existing JBoss EAP server configuration files and adds configurations for any new subsystems, updates the existing subsystem configurations with new features, and removes any obsolete subsystem configurations.

You can use the JBoss Server Migration Tool to migrate standalone servers and managed domains for the following configurations.

Migrating to JBoss EAP 7.2

The JBoss Server Migration Tool ships with JBoss EAP 7.2, so there is no separate download or installation required. This tool supports migration from JBoss EAP 6.4 and later to JBoss EAP 7.2. You run the tool by executing the jboss-server-migration script located in the EAP_HOME/bin directory. For more information about how to configure and run the tool, see Using the JBoss Server Migration Tool.

It is recommended that you use this version of the JBoss Server Migration Tool to migrate your server configuration to JBoss EAP 7.2 as this version of the tool is supported.

Migrating from WildFly to JBoss EAP

If you want to migrate from the WildFly server to JBoss EAP, you must download the latest binary distribution of the JBoss Server Migration Tool from the JBoss Server Migration Tool GitHub repository. This open source, standalone version of the tool supports migration from several versions of the WildFly server to JBoss EAP. For information about how to install and run this version of the tool, see the JBoss Server Migration Tool User Guide.

Important

The binary distribution of the JBoss Server Migration Tool is not supported. If you are migrating from a previous release of JBoss EAP, it is recommended that you use this supported version of the tool to migrate your server configuration to JBoss EAP 7.2 instead.