Chapter 2. Tools for migrating from JBoss EAP XP 3.0.x servers to JBoss EAP XP 4.0.0 servers You can choose one of the following tools to upgrade and migrate your JBoss EAP XP 3.0.x product to the JBoss EAP XP 4.0.0 product: JBoss EAP XP manager Migration Toolkit for Applications (MTA) JBoss Server Migration Tool 2.1. Using the JBoss EAP XP manager to upgrade JBoss EAP XP JBoss EAP XP manager is an executable jar file that you can download from the Product Downloads page. Use the JBoss EAP XP manager to upgrade from JBoss EAP XP 3.0.x to JBoss EAP XP 4.0.0. Note You can't upgrade from JBoss EAP XP 2.0.0 to JBoss EAP XP 4.0.0 using the JBoss EAP XP manager. This is because JBoss EAP XP 2.0.0 can only be installed on JBoss EAP 7.3, whereas JBoss EAP XP 3.0.0 and JBoss EAP XP 4.0.0 require JBoss EAP 7.4. Use the JBoss Server Migration Tool to upgrade from JBoss EAP XP 2.0.0 to JBoss EAP XP 4.0.0. Prerequisites You have downloaded and applied JBoss EAP 7.4.3 patch. For more information, see Patching JBoss EAP using the management CLI . You have JBoss EAP XP 3.0.x installed. For more information, see Installing JBoss EAP XP 3.0.x on JBoss EAP 7.4.x . You have applied the latest patch on your JBoss EAP XP 3.0.x server. Procedure Verify that your server is on the correct patch and has JBoss EAP XP 3.0.x installed. Important Make sure that you see jboss-eap-xp-3.0 patch stream in the output. Use the upgrade command to upgrade JBoss EAP XP 3.0.x to JBoss EAP XP 4.0.0. Accept the support policy prompt by entering yes 2.2. Use the JBoss Server Migration Tool to migrate your server configurations Use the JBoss Server Migration Tool when updating your server configuration to include the new features and settings of JBoss EAP XP 4.0.0. You can keep your existing JBoss EAP XP 3.0.x server configuration, provided that JBoss EAP XP 4.0.0 supports the configurations. The JBoss Server Migration Tool reads your existing JBoss EAP XP 3.0.x server configuration files and adds any new required subsystems to these files. The tool also updates 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 servers in a managed domain for your JBoss EAP XP 4.0.0 configuration. JBoss EAP XP 4.0.0 includes the JBoss Server Migration Tool, so you do not need to download a file and install the tool. Issue the jboss-server-migration script, which is located in the EAP_HOME/bin directory, to start the tool. Additional resources For more information about how to configure and run the JBoss Server Migration Tool, see Running the JBoss Server Migration Tool in the Using the JBoss Server Migration Tool guide. 2.3. Use the Migration Toolkit for Applications to analyze applications for migration The Migration Toolkit for Applications (MTA) includes extensible and customizable rule-based tools that simplify migration of Jakarta applications. You can use the toolkit to analyze an application's APIs, technologies, and architectures. The toolkit provides reports for the application you plan to migrate from JBoss EAP XP 3.0.x to JBoss EAP XP 4.0.0. You can use MTA to analyze standard JBoss EAP applications and bootable JAR applications. The MTA reports output the following information: Detailed explanations of all required migration changes. Whether the change is mandatory or optional. Whether the change is complex or simple. Links to code that requires a migration update. Hints and links to information for helping you complete the required migration changes. An estimate of the level of effort for each migration issue found and the total estimated effort to migrate the application . You can also use MTA to analyze the code and architecture of your JBoss EAP XP 3.0.x applications before you migrate them to JBoss EAP XP 4.0.0. The MTA rule set for migrating applications from JBoss EAP XP 3.0.x to JBoss EAP XP 4.0.0 reports on XML descriptors, specific application code, and parameters, that you need to replace with alternative configurations when migrating to JBoss EAP XP 4.0.0. Additional resources For information about the bootable JAR, see About the bootable JAR in the Using MicroProfile with JBoss EAP XP 4.0.0 guide. For more information about the Migration Toolkit for Applications to analyze your JBoss EAP XP 3.0.x applications, see the Product documentation for Migration Toolkit for Applications . For more information about using Migration Toolkit for Applications with the management CLI, see Run the CLI in the Migration Toolkit for Applications CLI Guide . For more information about using Migration Toolkit for Applications with the management console, see Using the Web Console to Analyze Applications in the Migration Toolkit for Applications Web Console Guide . 2.4. Upgrades from JBoss EAP 7.3 and earlier JBoss EAP XP 4.0.0 is only supported on JBoss EAP 7.4. If you operate servers on JBoss EAP 7.3 or earlier and want to use JBoss EAP XP, upgrade the servers to JBoss EAP 7.4. Complete any necessary migration before attempting to install JBoss EAP XP. Additional resources For information about migrating your server configuration, see Server Configuration Changes in the Migration Guide .

Commands:
java -jar jboss-eap-xp-manager.jar status --jboss-home= <path_to_eap> Starting JBoss EAP XP manager (4.0.0.Final-SNAPSHOT). You are currently on JBoss EAP XP 3. Enabled patch streams and their cumulative patch ids: - Patch stream: 'JBoss EAP'; Cumulative patch id: 'jboss-eap-7.4.3.CP'` - Patch stream: 'jboss-eap-xp-3.0'; Cumulative patch id: 'jboss-eap-xp-3.0.0.CP' Available commands in this state are: [remove, patch-apply]
java -jar jboss-eap-xp-manager.jar upgrade --jboss-home= <path_to_eap>