Chapter 2. Before You Begin

The target server contains the JBoss EAP Migration Tool and includes the latest bug fixes for the tool. You can use the JBoss EAP Migration Tool to migrate from one minor release of JBoss EAP to another minor release.

Before the migration process, you must ensure the JBoss EAP Migration Tool receives the latest JBoss EAP updates to prevent re-introducing bugs that might already be fixed for the tool. You can update the tool by applying the latest JBoss EAP updates to the target server.

For example, if you want to migrate your existing source server configuration from JBoss EAP 6.4 to JBoss EAP 7.2 then you must apply the latest JBoss EAP Migration Tool updates to JBoss EAP 7.2 before you can run the tool. Otherwise, after you migrate from JBoss EAP 6.4 to JBoss EAP 7.2, you might introduce issues to the new source server configuration.

Because the JBoss Server Migration Tool creates the configuration files based on the configuration of a previous release, it is intended to be run on a clean and unconfigured target server installation. The JBoss Server Migration Tool creates a backup of the target server’s configuration files by appending .beforeMigration to the file names. It then creates totally new configuration files for the target server using the source server’s configuration files, and migrates the configuration to run in target server configuration.

The JBoss Server Migration Tool provides the ability to configure logging, reporting, and the execution of migration tasks. By default, when you run the JBoss Server Migration Tool in non-interactive mode, it migrates the entire server configuration. You can configure the JBoss Server Migration Tool to customize logging and reporting output. You can also configure it to skip any part of the configuration that you do not want to migrate.

For instructions on how to configure properties to control the migration process, see Configuring the JBoss Server Migration Tool.