WebSphere Application Server & Liberty

What's new in the WebSphere Migration Tools 21.0.0.3?

By Ralph Sanders posted Fri September 03, 2021 02:21 PM

  

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.  In this post we will explore the new features in the 21.0.0.3 release.  Information about how to use our tools can be found in the online WebSphere Application Server Migration Toolkit documentation.  We will no longer be releasing documentation in PDF format.  For an overview of the application modernization process, see the Modernizing applications to use WebSphere Liberty learning path.

 

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, a list of necessary code changes for migration, 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 an Eclipse plugin for analyzing source code directly within your development environment.  The source scanner 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 Migrating to Liberty blog post.

 

What's new in the 21.0.0.3 release of the binary scanner?

 

User-Defined Rules

The binary scanner now allows for user-defined analysis rules to detect scenarios specific to your application migration. The user-defined rules are written in XML files. The rule files are grouped together in an XML list file and then specified using the --userRuleLocation parameter.

 

By default, the binary scanner runs the built-in rules in addition to the user-defined rules. The binary scanner also allows for running only the user-defined rules, forgoing the built-in rules, by specifying the --userRulesOnly parameter in the command. This parameter must be used with --userRuleLocation.  More information about user-defined rules can be found in the User-defined Rules in the Migration Toolkit for Application Binaries blog post.

This is an example of a report with a user-defined rule.

New Option for Generating Separate Reports

In addition to the existing consolidated report, the binary scanner now supports producing all report files separately with a single command. To do this, specify the --all-separate-reports action parameter. This parameter will generate Technology Evaluation, Detailed Migration Analysis, Inventory, and Configuration reports in their own files. 

This is an example of the terminal output after generating separate reports.

 

New Java SE 16 Deprecation Rules

To help users moving to the latest Java versions, we have added rules for new deprecations to our Java SE 16 migration scenario. 

This is an example of a new Java SE 16 Deprecation Rule.

 

What's new in the 21.0.0.3 release of the source scanner?

 

New Java SE 16 Deprecation Rules

To help users moving to the latest Java versions, we have added rules for new deprecations to our Java SE 16 migration scenario.

This is an example of a Java SE 16 Deprecation rule.

 

#appmigration#whatsnew#ApplicationModernization#migrationtoolkit#WebSphereLiberty​​​​


#Featured-area-2
#Featured-area-2-home
0 comments
378 views

Permalink