The WebSphere Application Server Migration tools are a set of tools that can be used to quickly analyze, inventory, and evaluate applications for a variety of application modernization scenarios. The WebSphere Application Server Migration Toolkit (also known as the source scanner) is used to analyze application source and the Migration Toolkit for Application Binaries (binary scanner) is used to analyze application binaries.
The binary scanner is a command-line tool that helps you quickly evaluate your application binaries for rapid deployment on Liberty or newer versions of WebSphere traditional. The tool identifies the Java EE programming models in the application and recommends the right-fit IBM® WebSphere Application Server edition. The tool can also highlight any Java SE, Java EE programming model, and WebSphere API differences. When migrating from WebSphere traditional, it can also help to migrate the configuration that is used by your application. For more information, see my What is the Migration Toolkit for Application Binaries? blog post.
The source scanner is an Eclipse-based plugin that allows you to easily make any required changes to your source code. It runs the same set of rules as the binary scanner based on your source and target application server, Java EE level, and Java SE level against your application source files. Where possible, the tool has quick fixes that you can use to automatically make changes to your code. For more information, see our Migrating to Liberty documentation.
What's new in the 21.0.01 release of the binary scanner?
Java SE 15 Migration
The --targetJava=java14 non-LTS (Long-Term-Support) option was deprecated and replaced with the --targetJava=java15 non-LTS option. Setting --targetJava=java15 includes migration rules for every Java SE release since Java 11. Java SE 15 is a non-LTS Java version. To migrate to an LTS Java version, migrate to Java SE 11 using the --targetJava=java11 option.
Application Security Configuration Migration Updates
WebSphere traditional security role bindings along with standalone and federated LDAP security configuration can now be migrated to WebSphere traditional wsadmin scripts (support was added for Liberty server.xml in 20.0.0.4). Additionally, if an application was using security configuration defined in a security domain, that configuration is now migrated.
Archive Checksum Algorithm changed from MD5 to SHA256
All Java archive files now have an SHA256 checksum associated with them for help tracking duplicates within an application.
Added Open Liberty to the Technology Evaluation Report
To help with evaluating what platform can support a certain application, Open Liberty has been added to the technology evaluation report that is produced when the --all or --evaluate options are specified.
To try out the new features, download the 21.0.0.1 release of the binary scanner today!
What's new in the 21.0.01 release of the source scanner?
Java SE 15 Migration
The Java SE 14 non-LTS (Long-Term-Support) option was deprecated and replaced with the Java SE 15 non-LTS option. Setting Java SE 15 as the migration target includes migration rules for every Java SE release since Java 11. Note, Java SE 15 is a non-LTS Java version. To migrate to an LTS Java version, migrate to Java SE 11.
Added Support for Migration to Open Liberty
Open Liberty is now supported as a target and source application server. Open Liberty has also been added to the technology evaluation report.
To try out the new features, download the 21.0.0.1 release of the source scanner today!
#ApplicationModernization#appmigration#Featured-area-2#Featured-area-2-home#migrationtoolkit#WebSphereLiberty#whatsnew