Chapter 3. Running the JBoss Server Migration Tool

You can run the JBoss Server Migration Tool in either of the following ways.

  • Interactive mode: This mode, which is the default, allows you to choose exactly which configurations you want to migrate.
  • Non-interactive mode: This mode allows you to run the tool without prompts.
Important

You must stop both the source and the target JBoss EAP servers before you run the JBoss Server Migration Tool.

3.1. Run the JBoss Server Migration Tool in Interactive Mode

By default, the JBoss Server Migration Tool runs interactively. This mode allows you to choose exactly which server configurations you want to migrate.

Note

Interactive mode does not allow you to choose which subsystems to migrate. For information on how to configure the tool at the subsystem or task level, see Configure the Migration Tasks Performed by the JBoss Server Migration Tool.

The following are the basic steps that are performed for a minimal migration. If the server from which you are migrating includes custom configurations, for example deployments, or if it is missing default resources, the tool provides additional prompts.

  1. To run the tool in interactive mode, navigate to the target server installation directory and run the following command, providing the source argument as the path to the source server installation. 

    $ EAP_HOME/bin/jboss-server-migration.sh --source EAP_PREVIOUS_HOME

  2. You are prompted to determine if you want to migrate the source server’s standalone configurations, which are located in the EAP_PREVIOUS_HOME/standalone/configuration/ directory, to the target server’s standalone configurations, which are located in the EAP_HOME/standalone/configuration/ directory. 

    Migrate the source's standalone server?
yes/no? yes

    If you respond with no, standalone server migration is skipped and no standalone server configuration files are migrated.

    If you respond with yes, you see the following prompt. 

    Migrate all configurations?
yes/no? yes

    Respond with yes to migrate all of the source server’s standalone server configuration files.

    Respond with no to receive a prompt for each individual standalone*.xml configuration file.

  3. Next, you are prompted to determine if you want to migrate the source server’s managed domain configurations, which are located in the EAP_PREVIOUS_HOME/domain/configuration/ directory, to the target server’s managed domain configurations, which are located in the EAP_HOME/domain/configuration/ directory. 

    Migrate the source's managed domain?
yes/no? yes

    If you respond with no, managed domain migration is skipped and no managed domain configuration files are migrated.

    If you respond with yes, the tool begins migrating the managed domain content of the source server. A ciphered repository is used to store data, such as deployments and deployment overlays, that are referenced by the source server’s managed domain and host configurations. Because the source and target servers use a similar content repository, the tool simply copies the data from the source server to the target server and prints the results to the console and the server log. 

    INFO  [ServerMigrationTask#397] Migrating domain content found:  [22/caa450a9ba3b84eaf5a15b6da418b92ce6c98e/content, 23/b62a37ba8a4830622bfcdb960280577cc6796e/content]
INFO  [ServerMigrationTask#398] Resource with path /EAP_HOME/domain/data/content/22/caa450a9ba3b84eaf5a15b6da418b92ce6c98e/content migrated.
INFO  [ServerMigrationTask#399] Resource with path /EAP_HOME/domain/data/content/23/b62a37ba8a4830622bfcdb960280577cc6796e/content migrated.

  4. Next, the migration tool scans the source server for managed domain configuration files, prints the results to the console, and provides the following prompt. 

    Migrate all configurations?
yes/no? yes

    Respond with yes to migrate all of the source server’s managed domain configuration files.

    Respond with no to receive a prompt for each individual managed domain configuration file.

  5. Next, the migration tool scans the source server for host configurations files, prints the results to the console, and provides the following prompt. 

    INFO  [ServerMigrationTask#457] Retrieving source's host configurations...
INFO  [ServerMigrationTask#457] /jboss-eap-6.4/domain/configuration/host-master.xml
INFO  [ServerMigrationTask#457] /jboss-eap-6.4/domain/configuration/host-slave.xml
INFO  [ServerMigrationTask#457] /jboss-eap-6.4/domain/configuration/host.xml

Migrate all configurations?
yes/no? yes

    Respond with yes to migrate all of the source server’s host configuration files.

    Respond with no to receive a prompt for each individual host configuration file.

  6. Upon completion, you should see the following message in the server console. 

     Migration Result: SUCCESS

3.2. Run the JBoss Server Migration Tool in Non-interactive Mode

You can run the JBoss Server Migration Tool in non-interactive mode. This mode allows it to run without prompts.

Note

The JBoss Server Migration Tool automatically migrates all subsystem configurations for all server configuration files. For information on how to configure the tool at the subsystem or task level, see Configure the Migration Tasks Performed by the JBoss Server Migration Tool.

  1. To run the tool in non-interactive mode, navigate to the target server installation directory and run the following command, providing the source argument as the path to the source server installation and setting the --interactive or -i argument to false. 

    $ EAP_HOME/bin/jboss-server-migration.sh --source EAP_PREVIOUS_HOME --interactive false

  2. By default, the tool automatically migrates all of the source server’s standalone and managed domain configuration files. However, you can configure the tool’s properties to skip migration of specific configurations. Upon completion, you should see the following message in the server console. 

     Migration Result: SUCCESS