JBoss EAP XP 6.0 upgrade and migration guide

Use the steps outlined in the JBoss EAP XP 6.0 upgrade and migration guide to prepare, upgrade, and migrate your JBoss EAP XP 5.0 product to the JBoss EAP XP 6.0 product. JBoss EAP XP 6.0 is compatible with only JBoss EAP 8.1. If you operate servers on JBoss EAP 8.0 and you want to install the JBoss EAP XP 6.0 on it, you must first upgrade your JBoss EAP 8.0 instance to JBoss EAP 8.1.

The guide references tools that you can use for the upgrading and migration process. These tools are as follows:

After you successfully upgrade and migrate JBoss EAP XP 5.0 release to JBoss EAP XP 6.0, you can begin to implement any application migrations for your JBoss EAP 8.1 instance.

After you upgrade the JBoss EAP Expansion Pack, you might have to update application code.

For JBoss EAP XP 6.0, some backward compatibility might exist for JBoss EAP XP 5.0 applications. However, if your application uses features that were deprecated or functionality that was removed from JBoss EAP XP 6.0, you might need to make changes to your application code.

Review the following new items before you begin the migration process:

After you have reviewed the listed items, analyze your environment and plan for the upgrade process and migration process. Ensure you back up any applications that you plan to migrate to JBoss EAP XP 6.0.

You can now upgrade your current JBoss EAP XP 5.0 release to JBoss EAP XP 6.0. You can implement any application migrations after the upgrade process.

The JBoss EAP XP 6.0 release includes support for the following MicroProfile 7.0 components:

Before you migrate your application to JBoss EAP XP 6.0 be aware that some features that were available in JBoss EAP XP 5.0.x might be deprecated or no longer supported.

Red Hat removed support for some technologies due to the high maintenance cost, low community interest, and much better alternative solutions.

Ensure that you review the Red Hat JBoss EAP XP 6.0 release notes and the Release notes for Red Hat JBoss Enterprise Application Platform 8.1 for any unsupported and deprecated features.

Use the JBoss Server Migration Tool when updating your server configuration to include the new features and settings of JBoss EAP XP 6.0. You can keep your existing JBoss EAP XP 5.0 server configuration, provided that JBoss EAP XP 6.0 supports the configurations.

The JBoss Server Migration Tool reads your existing JBoss EAP XP 5.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 6.0 configuration.

JBoss EAP XP 6.0 does not include the JBoss Server Migration Tool, so you need to download the tool from the JBoss EAP XP download page.

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 5.0 to JBoss EAP XP 6.0.

The MTA reports output the following information:

You can also use MTA to analyze the code and architecture of your JBoss EAP XP 5.0 applications before you migrate them to JBoss EAP XP 6.0. The MTA rule set for migrating applications from JBoss EAP XP 5.0 to JBoss EAP XP 6.0 reports on XML descriptors, specific application code, and parameters, that you need to replace with alternative configurations when migrating to JBoss EAP XP 6.0.

MicroProfile 7.0 includes updates to all major MicroProfile specifications, and the following which might include API-incompatible changes:

You might need to update your applications to use the latest MicroProfile OpenAPI specification.

When migrating a JBoss EAP XP application’s Maven project to JBoss EAP XP 6.0, you might need to update the pom.xml file due to the following changes:

<dependencyManagement>
   <dependencies>
       <dependency>
           <groupId>org.jboss.bom</groupId>
           <artifactId>jboss-eap-xp-microprofile</artifactId>
           <version>${version.bom}</version>
           <type>pom</type>
           <scope>import</scope>
       </dependency>
   </dependencies>
</dependencyManagement>

<dependencyManagement>
   <dependencies>
       <dependency>
           <groupId>org.jboss.bom</groupId>
           <artifactId>jboss-eap-expansion</artifactId>
           <version>${version.bom}</version>
           <type>pom</type>
           <scope>import</scope>
       </dependency>
   </dependencies>
</dependencyManagement>

<plugin>
   <groupId>org.jboss.eap.plugins</groupId>
   <artifactId>eap-maven-plugin</artifactId>
   <configuration>
       <channels>
           <channel>
               <manifest>
                   <groupId>org.jboss.eap.channels</groupId>
                   <artifactId>eap-8.0</artifactId>
               </manifest>
           </channel>
           <channel>
               <manifest>
                   <groupId>org.jboss.eap.channels</groupId>
                   <artifactId>eap-xp-5.0</artifactId>
               </manifest>
           </channel>
       </channels>
   </configuration>
</plugin>

<plugin>
   <groupId>org.jboss.eap.plugins</groupId>
   <artifactId>eap-maven-plugin</artifactId>
   <configuration>
       <channels>
           <channel>
               <manifest>
                   <groupId>org.jboss.eap.channels</groupId>
                   <artifactId>eap-8.1</artifactId>
               </manifest>
           </channel>
           <channel>
               <manifest>
                   <groupId>org.jboss.eap.channels</groupId>
                   <artifactId>eap-xp-6.0</artifactId>
               </manifest>
           </channel>
       </channels>
   </configuration>
</plugin>

MicroProfile OpenTracing is not supported in JBoss EAP XP 6.0 and is replaced by OpenTelemetry tracing.

To replace MicroProfile OpenTracing with OpenTelemetry Tracing, follow these steps:

MicroProfile Metrics is not supported in JBoss EAP XP 6.0 and is replaced by Micrometer.

To replace MicroProfile Metrics with Micrometer, follow these steps:

MicroProfile Telemetry is the supported metrics system. While you can run multiple metrics systems at the same time (e.g., MicroProfile Telemetry, WildFly Metrics, and Micrometer), this will result in decreased server performance.

Micrometer integration in JBoss EAP XP 6.0 introduces a vendor-neutral observability layer with a reusable API for registering and tracking performance metrics across applications. This extension integrates with Micrometer, allowing deployed applications to access its API and display application-specific metrics alongside the server metrics provided by the extension.

JBoss EAP XP 6.0 introduces support for two Micrometer export options:

These options provide flexibility for integrating with different observability tools and simplify migration for Prometheus-based environments.

To support Prometheus integration, JBoss EAP XP 6.0 includes a Prometheus registry for Micrometer. This addition enables a pull-based scraping option alongside the existing OTLP push path. As a result, applications can expose metrics in a format that is compatible with Prometheus without requiring an external collector-side translation.

The Micrometer subsystem in JBoss EAP XP 6.0 continues to support OTLP (push) export and adds a Prometheus (pull) registry to support Prometheus-based scraping workflows.