Red Hat SummitChapter 2. Tools for migrating from JBoss EAP XP 3.0 or 4.0 servers to JBoss EAP XP 5.0 servers
You can choose one of the following tools to upgrade and migrate your JBoss EAP XP 3.0 or 4.0 product to the JBoss EAP XP 5.0 product:
- Migration Toolkit for Applications (MTA)
- JBoss Server Migration Tool
2.1. 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 5.0. You can keep your existing JBoss EAP XP 3.0 or 4.0 server configuration, provided that JBoss EAP XP 5.0 supports the configurations.
The JBoss Server Migration Tool reads your existing JBoss EAP XP 3.0 or 4.0 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 for your JBoss EAP XP 5.0 configuration.
JBoss EAP XP 5.0 does not include the JBoss Server Migration Tool, so you need to download the tool from the JBoss EAP XP download page.
2.2. 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 or 4.0 to JBoss EAP XP 5.0.
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 or 4.0 applications before you migrate them to JBoss EAP XP 5.0. The MTA rule set for migrating applications from JBoss EAP XP 3.0 or 4.0 to JBoss EAP XP 5.0 reports on XML descriptors, specific application code, and parameters, that you need to replace with alternative configurations when migrating to JBoss EAP XP 5.0.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}