Use cases and migration paths for Migration Toolkit for Applications

Ease the adoption of Red Hat OpenShift or Red Hat Application Foundations with the Migration Toolkit for Applications. With containerization-readiness, source-code analysis, and project management capabilities this tool can help your organization benefit from faster, safer legacy application modernization.

MTA

Use cases and migration paths

Application inventory

The application inventory is the entry point and natural integration interface for all tools within the migration toolkit for applications. It enables organizations to manage their portfolio in a centralized fashion and, from there, classify applications and launch any actions that might be related to them, such as analysis and assessments.

On its own, the application inventory provides a way to rationalize an organization's application portfolio through an extensible tagging model that allows the classification of applications in multiple dimensions. The tool comes with a series of curated tags related to typical aspects of application development, such as the programming languages, operating systems, or databases it consumes. Users can extend it however they want to accommodate concepts like the custom corporate framework used to develop an application. 

The application inventory also lets users group applications by the business service they belong to as well as provides a way to manage dependencies between applications.

Assessment

The assessment module helps organizations evaluate their application portfolio to determine the suitability of containerization and enable adoption leads to make informed decisions on the migration strategy for each application or application type. This is achieved via a questionnaire-driven approach, covering all essential topics related to technology and application lifecycle management.

Based on the responses, the tool can detect any potential risks that might prevent an application from running in containers, providing insight to help the project lead select the best migration strategy for each case. The adoption team can also add information about the estimated effort to migrate the application and assign priority based on the business criticality.

Migration waves management

The migration waves module enables project managers and architects to break the portfolio into different waves and execute the adoption effort in an iterative fashion, grouping applications to be migrated on a specified schedule. In combination with the integration with Atlassian Jira, Migration waves can also be used to keep track of the progress of the overall migration project.

Analysis module’s migration paths 

The analysis module in the migration toolkit for applications is an extensible and customizable rule-based capability that simplifies the migration and modernization of Java applications.

The tool examines application artifacts, including project source directories and application archives, then produces an HTML report highlighting areas needing changes.

We've summarized the most commonly used migration paths in the following table.

 

 

Source platform

Targets
Migration to JBoss EAP 7 & 8OpenShift (cloud readiness)OpenJDK
11, 17, & 21
Jakarta EE 9Camel 3 & 4Spring Boot in Red Hat RuntimesQuarkusOpen LibertyAzure App Service for EAP apps
Oracle WebLogic Server

-

-

-

-

-

-

IBM WebSphere Application Server

-

-

-

-

-

JBoss EAP 4

✘ [1]

-

-

-

-

-

-

JBoss EAP 5

-

-

-

-

-

-

JBoss EAP 6

-

-

-

-

-

-

JBoss EAP 7

-

-

-

-

-

Thorntail

✔ [2]

-

-

-

-

-

-

-

-

Oracle JDK

-

-

-

-

-

-

-

Camel 2

-

-

-

-

-

-

Camel 3

-

-

-

-

-

-

-

-

Spring Boot

-

-

-

-

Any Java application

-

-

-

-

-

-

-

Any Java EE application

-

-

-

-

-

-

-

[1] Although the migration toolkit for applications does not currently provide rules for this migration path, Red Hat Consulting can assist with migration from any source platform. 
[2] Requires JBoss Enterprise Application Platform expansion pack 2 (EAP XP 2)