Chapter 1. Red Hat JBoss Enterprise Application Platform migration overview As a system administrator, you can upgrade from Red Hat JBoss Enterprise Application Platform 7 to Red Hat JBoss Enterprise Application Platform 8.0. This guide covers new features available in the release, deprecated and unsupported features, and any necessary application and server configuration updates to maintain consistent behavior. It also provides information about tools that can help with the migration, such as Migration Toolkit for Runtimes , which simplifies migration of Java applications, and the JBoss Server Migration Tool , which updates the server configuration. After successfully deploying and running JBoss EAP 8.0, you can upgrade individual components to use the new functions and features of JBoss EAP 8.0. Note If you want to migrate from older releases of JBoss EAP, you must first migrate to JBoss EAP 7.4. For more information, see JBoss EAP 7.4 Migration Guide . 1.1. Understanding migrations and upgrades This section provides explanations and guidelines for upgrading and patching JBoss EAP, including major upgrades, minor updates, and cumulative patches. 1.1.1. Major upgrades in JBoss EAP A major upgrade or migration is necessary when an application is moved from one major release to another, such as from JBoss EAP 7 to JBoss EAP 8.0. Applications that comply with the Jakarta EE 8 specification, contain proprietary code, or use deprecated APIs might require modifications to their application code to run on JBoss EAP 8.0. The introduction of Jakarta EE 10 involves changes in Java package names and other aspects that require adjustments to Jakarta EE application code for compatibility with JBoss EAP 8.0. Additionally, the server configuration has changed in JBoss EAP 8.0 and requires migration. This type of migration is addressed in this guide. 1.1.2. Minor updates in JBoss EAP Minor Updates in JBoss EAP are point releases that provide bug fixes, security fixes, and new features. The changes made in each point release are documented in the Release notes for Red Hat JBoss Enterprise Application Platform 8.0 . Use the JBoss Server Migration Tool to automatically upgrade from one point release to another, for example from JBoss EAP 7.0 to JBoss EAP 7.1. For more information, see Using the JBoss Server Migration Tool . 1.1.3. Cumulative patches in JBoss EAP JBoss EAP periodically provides cumulative patches that contain bug and security fixes. Cumulative patches increment the release by the last digit, for example, upgrading from version 7.1.0 to 7.1.1. 1.2. Use of <EAP_HOME> variable In this document, the <EAP_HOME> variable denotes the path to the JBoss EAP installation. Replace this variable with the actual path to your JBoss EAP installation. Note <EAP_HOME> is not an environment variable. Use the JBOSS_HOME environment variable in scripts. Depending on the installation option you choose to install JBoss EAP, you can locate the installation directory or the default path as follows: If you installed JBoss EAP by using the archive installation method, the installation directory is the jboss-eap-8.0 directory where you extracted the archive. If you installed JBoss EAP by using the RPM installation method, the installation directory is the /opt/rh/eap8/root/usr/share/wildfly/ . If you installed JBoss EAP by using the installer application, the default path for <EAP_HOME> is USD{user.home}/EAP-8.0.0 : For Red Hat Enterprise Linux and Oracle Solaris: /home/ USER_NAME /EAP-8.0.0/ For Microsoft Windows: C:\Users\ USER_NAME \EAP-8.0.0\ If you installed and configured the JBoss EAP server by using the Red Hat CodeReady Studio installer application, the default path for <EAP_HOME> is USD{user.home}/devstudio/runtimes/jboss-eap : For Red Hat Enterprise Linux: /home/ USER_NAME /devstudio/runtimes/jboss-eap/ For Microsoft Windows: C:\Users\ USER_NAME \devstudio\runtimes\jboss-eap or C:\Documents and Settings\ USER_NAME \devstudio\runtimes\jboss-eap\ Note If you set the Target runtime to 8.0 or a later runtime version in Red Hat CodeReady Studio, your project is compatible with the Jakarta EE 10 specification.

Commands: