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 23.0.0.3 release focuses on the use of automated fixes using 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 23.0.0.3?
WebSphere traditional to Liberty Automated Fixes via Recipes
The Migration Toolkit for Application Binaries now supports automated source code migrations when moving from WebSphere traditional to Liberty. Applications flagged with WebSphere to Liberty rules provide a new section in the produced HTML and JSON reports for running OpenRewrite recipes to automate code changes for issues flagged by the binary scanner. The generated recipe configuration can be run using Maven or Gradle, depending on the preferred build platform.
Every rule correlated with a recipe for automating the code fix will have an icon next to the severity icon to designate it has an automated fix.
New JDBC Configuration Migration
New rules were added to flag use of DataStoreHelper APIs in an application. Additionally, support for migrating WebSphere Application Server configuration for DataStoreHelpers, XML bindings and JDBC Exception Mappings was added. More JDBC Configuration is now detected in WebSphere configuration environments and added to the generated server.xml configuration.