Chapter 2. Preparing for migration to JBoss EAP 8.0 As a system administrator, you need to plan the migration to JBoss EAP 8.0. This upgrade is essential for improved performance, enhanced security, and increased stability of Java applications. JBoss EAP 8.0 provides backward compatibility for JBoss EAP 7 applications. However, if your application uses features that JBoss EAP 8.0 has deprecated or removed, you might need to modify your application code. The JBoss EAP 8.0 release introduces several changes that might impact your application deployment. To ensure a successful migration, conduct research and planning before attempting to migrate your application. Before beginning the migration process, follow these initial steps: Familiarize yourself with the features of Jakarta EE 10 . Review features of JBoss EAP 8.0 . Review the JBoss EAP getting started material . Ensure a seamless migration process by backing up your data and reviewing server state . Streamline your installation process by migrating JBoss EAP with RPM installation . Improve manageability and automation by migrating JBoss EAP as a service . After becoming familiar with the feature changes, the development materials, and the tools that can assist your migration efforts, evaluate your applications and server configuration to determine the necessary changes for running them on JBoss EAP 8.0. 2.1. Review the Jakarta EE 10 features Jakarta EE 10 introduces numerous enhancements that simplify the development and deployment of feature-rich applications in both private and public clouds. It incorporates new features and the latest standards such as HTML5, WebSocket, JSON, Batch, and Concurrency Utilities. Updates include Jakarta Persistence 3.1, Jakarta RESTful Web Services 3.1, Jakarta Servlet 6.0, Jakarta Expression Language 5.0, Java Message Service 3.1. Jakarta Server Faces 4.0, Jakarta Enterprise Beans 4.0, Contexts and Dependency Injection 2.0, and Jakarta Bean Validation 3.0. Additional resources Jakarta EE Platform 10 2.2. Review the features of JBoss EAP 8.0 JBoss EAP 8.0 includes upgrades and improvements over releases. For the complete list of new features introduced in JBoss EAP 8.0, see New features and enhancements in the Release notes for Red Hat JBoss Enterprise Application Platform 8.0 on the Red Hat Customer Portal. Before migrating your application to JBoss EAP 8.0, note that some features from releases may no longer be supported or have been deprecated due to high maintenance costs, low community interest, or availability of better alternatives. For a complete list of deprecated and unsupported features in JBoss EAP 8.0, see Unsupported, deprecated, and removed functionality in the Release notes for Red Hat JBoss Enterprise Application Platform 8.0 on the Red Hat Customer Portal. 2.3. Review the JBoss EAP Getting Started material This section explains the key components of the JBoss EAP Getting Started material, providing a concise overview of essential information to help you start with JBoss EAP. Review the JBoss EAP Getting Started Guide for essential information on: Downloading and installing JBoss EAP 8.0 to set up your environment effectively. Downloading and installing JBoss Tools to improve your development environment. Important JBoss Tools is a community project and is not supported by Red Hat. Please reference the community website for assistance with setting up and running your instance of JBoss Tools. To download JBoss Tools, see JBoss Tools Downloads . Configuring Maven for your development environment and managing project dependencies. Downloading and running the quick-start example applications that come with the product. Additional resources Developing applications using JBoss EAP 2.4. Back up your data and review server state This section emphasizes the need to back up data, review server state, and handle potential issues before migrating your application. By safeguarding deployments, managing open transactions, and assessing timer data, you can ensure a smooth migration. Consider the following potential issues before you start the migration: The migration process might remove temporary folders. Make sure you backup any deployments within the data/content/ directory before migrating. Later, restore the data after completion to avoid server failure due to missing content. Before migration, handle open transactions and delete the data/tx-object-store/ transaction directory. Review the persistent timer data in data/timer-service-data before proceeding with the migration to determine its applicability post-upgrade. Before the upgrade, check the deployment-* files in that directory to identify which timers are still in use. Make sure to back up the current server configuration and applications before you start the migration. 2.5. Migrate JBoss EAP with RPM installation The migration advice in this guide also applies to migrating RPM installations of JBoss EAP, but you might need to alter some steps, such as how to start JBoss EAP to suit an RPM installation compared to an archive or the jboss-eap-installation-manager installation. Important It is not supported to have more than one RPM-installed instance of JBoss EAP on a single Red Hat Enterprise Linux server. Therefore, it is recommended to migrate the JBoss EAP installation to a new machine when migrating to JBoss EAP 8.0. Additional resources Installing JBoss EAP by using the RPM installation method 2.6. Migrate JBoss EAP as a service If you run JBoss EAP 7 as a service, review the updated configuration instructions for JBoss EAP 8.0 in the Red Hat JBoss Enterprise Application Platform Installation Methods . 2.7. Migrate a cluster If you run a JBoss EAP cluster, follow the instruction in the Upgrading a cluster section in the JBoss EAP 7.4 Patching and Upgrading Guide .

Commands: