Chapter 3. Application Migration

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.