Chapter 3. Running the JBoss Server Migration Tool

Procedure

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.

   $ MIGRATION_TOOL_HOME/bin/jboss-server-migration.sh --source EAP_PREVIOUS_HOME --target EAP_NEW_HOME

   Copy to Clipboard

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_NEW_HOME/standalone/configuration/ directory.

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

   Copy to Clipboard

   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

   Copy to Clipboard

   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_NEW_HOME/domain/configuration/ directory.

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

   Copy to Clipboard

   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_NEW_HOME/domain/data/content/22/caa450a9ba3b84eaf5a15b6da418b92ce6c98e/content migrated.
   INFO  [ServerMigrationTask#399] Resource with path /EAP_NEW_HOME/domain/data/content/23/b62a37ba8a4830622bfcdb960280577cc6796e/content migrated.

   Copy to Clipboard

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

   Copy to Clipboard

   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-8.0/domain/configuration/host-master.xml
   INFO  [ServerMigrationTask#457] /jboss-eap-8.0/domain/configuration/host-slave.xml
   INFO  [ServerMigrationTask#457] /jboss-eap-8.0/domain/configuration/host.xml
   
   Migrate all configurations?
   yes/no? yes

   Copy to Clipboard

   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

   Copy to Clipboard

Procedure

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.

   $ MIGRATION_TOOL_HOME/bin/jboss-server-migration.sh --source EAP_PREVIOUS_HOME --target EAP_NEW_HOME --interactive false

   Copy to Clipboard

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

   Copy to Clipboard