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.
The Migration Toolkit team is proud to announce enhancements to our binary scanner for your compiled application - the
Migration Toolkit for Application Binaries!
So what does it do, you ask?
The tool generates four kinds of reports in two possible formats - HTML or JSON. The tool also generates a Liberty configuration file in XML format.
The Application Migration Report is a consolidated migration report that contains the content of the Application Evaluation Report, the Application Inventory Report, the Detailed Migration Analysis Report, and the Liberty configuration. The beginning of the report contains a technology evaluation summary, which indicates which IBM platforms support the technologies used by the application, and a rule severity summary that shows how many rules and rule results are flagged for each rule severity. The default report shows migration results for migrating from WebSphere Application Server V8.5.5 and Java SE 6 to Liberty and Java SE 8. You should modify the source and target options to fit your migration scenario. The Application Migration Details section of the report contains a section corresponding to each of the individual actions.
The Application Evaluation Report identifies the Java EE programming models in the application and provides a recommendation for the right-fit IBM WebSphere Application Server edition.
The Application Inventory Report contains a high-level inventory of the content and structure of each application, plus information about potential deployment problems and performance considerations. The report includes a dashboard that reports the number and types of archives found. The counts of Java Servlets, JSP files, JPA entities, EJB beans, and web services are reported per application as well as in an overall summary. For each archive, the Java EE module type and version are included. And for utility JAR files, the contained packages are reported up to and including the third sub-package.
The Detailed Migration Analysis Report highlights any Java SE, Java EE programming model, and WebSphere API differences between versions of WebSphere Application Server traditional, and between WebSphere traditional and Liberty. The report also highlights differences when migrating from JBoss, WebLogic, and Apache Tomcat Application Servers to WebSphere traditional or Liberty. The report offers advice and potential solutions to assess the ease of moving applications to Liberty or to newer versions of WebSphere traditional. It also informs you of any Java EE specification implementation differences that could affect your applications. If you are moving an application to a cloud platform, the report offers additional advice, suggestions, and best practices to ensure that the application runs correctly in those environments.
The Liberty configuration file is generated and includes all of the application required features needed in a Liberty server based on scanning each application binary. The configuration file includes additional resource configuration for applications migrating from a WebSphere traditional environment. Use the generated
server.xml file to configure your Liberty server by copying the content or use the
include element to include it in the server configuration.
Who is it for?
Since this command-line tool does not require Eclipse, it is perfect for both administrators and developers using other IDEs. It is also great for evaluating applications whose source code has been misplaced or simply lost.
How do I use the Migration Toolkit for Application Binaries?
The tool is an executable JAR file with one required parameter, the
binaryInputPath, which is an absolute or relative path to a binary file or a directory that contains binary files. Run commands from the
wamt directory in your Migration Toolkit for Application Binaries installation. For a complete list of supported actions, run the following command:
java -jar binaryAppScanner.jar --help
Generating the Application Migration Report
For a complete list of supported options for the consolidated migration report, run the following command:
java -jar binaryAppScanner.jar --help --allTo display the HTML report, run the following command:
java -jar binaryAppScanner.jar <binaryInputPath> --all
Generating the Application Inventory Report
For a complete list of supported options for application inventory, run the following command:
java -jar binaryAppScanner.jar --help --inventoryTo display the HTML report, run the following command:
java -jar binaryAppScanner.jar <binaryInputPath> --inventory
Generating the Detailed Migration Analysis Report
For a complete list of supported options for detailed migration analysis, run the following command:
java -jar binaryAppScanner.jar --help --analyzeTo display the default report, an HTML report for a migration from WebSphere Application Server traditional V8.5.5 to Liberty, run the following command:
java -jar binaryAppScanner.jar <binaryInputPath> --analyze
The report gives details about which rules were flagged for your application binaries. For each flagged result, the report lists the affected file along with the match criteria, the method name if applicable, and the line number if available. Line numbers are only available for results that occur within a method body.
Generating the Application Technology Evaluation Report
For a complete list of supported options for evaluating your application, run the following command:
java -jar binaryAppScanner.jar --help --evaluateTo display the HTML report, run the following command:
java -jar binaryAppScanner.jar <binaryInputPath> --evaluate
To output the report to a file, additionally specify the
--output parameter with or without a filename. For example, the following command outputs the report to an HTML file with the default name of TechnologyReport.html in the specified directory:
java -jar binaryAppScanner.jar <binaryInputPath> --output=/myReports
Generating the Liberty configuration file
For a complete list of supported options for configuration generation, run the following command:
java -jar binaryAppScanner.jar --help --generateConfigTo generate the WebSphere configuration files, run the following command:
java -jar binaryAppScanner.jar <binaryInputPath> --generateConfig
Use these files to configure your Liberty server by copying the content to the Liberty server.xml file, or use the <include> element to include it in the server configuration.
So what are you waiting for? Give it a try!
See the IBM Developer learning path Modernizing applications to use WebSphere Liberty to discover all the application modernization tools available with WebSphere Hybrid Edition.
Also, check out the other articles in the app modernization blog series.
---------------
Trademark
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
#ApplicationModernization#appmigration#Featured-area-1#Featured-area-1-home#migration#migrationtoolkit#WebSphereLiberty