The WebSphere Application Server Migration Tools can be used to analyze the contents of an application and determine what changes are needed to migrate to Liberty, a new version of WebSphere, or a new version of Java, among other migration destinations. The 24.0.0.2 release focuses on support for Java 21 as a target, with the use of automated fixes by recipes with the Migration Toolkit for Application Binaries. The OpenRewrite open source project rewrite-liberty contains recipes that automate the source code changes and are run in Maven or Gradle environments when moving from WebSphere traditional to Liberty. Download the new release of the migration tools today and give them a try!
Information about how to use our tools can be found in the WebSphere Application Server Migration Toolkit documentation. For an overview of the application modernization process, see the Modernizing applications to use WebSphere Liberty learning path.
What are the migration tools?
The Migration Toolkit for Application Binaries (binary scanner) is a command line tool for analyzing application binaries. After scanning the application, it produces a report with configuration information, technologies required by the application, a list of necessary code changes for migration, configuration to include recipes for automated code changes and a view of the contents within the archive. This report can be generated in multiple formats, and you can use different parameters to filter information that you would like to be included. More information about the binary scanner can be found in the What is the Migration Toolkit for Application Binaries? blog post.
The WebSphere Application Server Migration Toolkit (source scanner) is stabilized and future investments will be focused on an IDE-agnostic solution for application analysis using the Migration Toolkit for Application Binaries and automated source code fixes (referred to as quick fixes in Eclipse) via recipes that are run through Maven and Gradle build invocations. The source scanner analyzes source code directly within your development environment and uses the same set of rules as the binary scanner to flag code changes that will be necessary for your migration. When possible, automatic code changes (quick fixes) are available. More information about the source scanner can be found in the What is the WebSphere Application Migration Toolkit? blog post.
What's new in version 24.0.0.2?
Java SE 21 Rule Additions
Setting --targetJava=java21 for an Analysis scan runs new rules in the scan for migrating to Java SE 21. Java SE 21 is a Long Term Supported Java version.
Java SE 11, 17, 21 and EclipseLink Automated Fixes Additions
The Migration Toolkit for Application Binaries supports automated source code fixes on the command line for moving to several Java and JavaEE versions. More automated fixes were added to support migration to Java 11, 17, 21 and EclipseLink. The binary scanner now includes automated code fixes for moving to Java version 7, 8, 9, 11, 17, 21, Jakarta EE 9, and Jakarta EE 10. See Detailed Migration Analysis Report for instructions on performing application analysis and reviewing the several available rules with automated fixes. The report also provides the Automated Fix Configuration section that contains the config of all supported automated fixes. These include over 100 automated code fixes covering several versions of Java in addition to the many existing Liberty automated code fixes (rewrite-liberty).
Improved Migration Support for OpenJPA to EclipseLink
The WebSphere Application Server JPA 2.1 implementation is based on the EclipseLink implementation. Prior to JPA version 2.1 the OpenJPA implementation was used. More support was added to ease this migration effort with scanning and automated fixes.
Additional Configuration Migration to Liberty
Support for migrating additional WebSphere Application Server Configuration for MQ.
Support
Bug and field support fixes were added to this release.