IBM Application Runtimes Come for answers. Stay for best practices. All we’re missing is you. Join / Log in Ask a question
Use Case : Migrate enterprise java application from IBM WebSphere Application server (Traditional) to IBM WebSphere Liberty.
Do I need to use these tools in order? or combine 2 or 3 tools together? or specific tools for specific task, if so some details? or Just one tool for all?
please advance thanks for your valuable time and help...
Hi, you need to understand what the tools do and how many applications you are going to migrate to Liberty.
Mono2Micro is not necessary for migration. It is paid tool and is used to divide an application into microservices. You can do this as part of your migration.
The Cloud Transformation Advisor is a paid tool that has a central repository to analyze application from cells and individual applications. It can show the compatibilities, what will need to be fixed or updated and give suggestions, and migration paths, including the server.xml for liberty. If this is installed the other tools are not necessary.
Migration Toolkit for Application Binaries is a standalone tool used to analyze applications (ear/war) files. It will give information for that application and provide information about technologies used by the application, possible problems, information on how to potential fix them and a base Liberty configuration. The configuration does not include everything that is needed since it has no context of its environment like the TA above has based on configuration. If you run this you do not need anything else, unless you want the configuration from tWAS to Liberty, which is available in the Configuration Migration Tool.
WebSphere Application Migration Toolkit is an Eclipse tool that analyzes the source code of an application and provides information like the the Migration Toolkit for Application Binaries.
The Configuration Migration Toolkit takes a tWAS configuration and converts it into a Liberty configuration. This is usually used in conjunction with the Application Migration Toolkit.
This page gives a good description for each of the current migration tools: WebSphere Migration Knowledge Collection: Migrating to Liberty. The IBM WebSphere Migration Discovery Tool and the IBM WebSphere Configuration Migration Tool are no longer in service because their functionally has been incorporated into IBM Cloud Transformation Advisor (TA). The IBM Migration Toolkit for Application Binaries (binary scanner) and TA have the same capabilities for config migration from tWAS to Liberty.
To migrate a single application, I would recommend starting with the binary scanner to generate a migration report. This report will give you information about what changes are required to migrate to Liberty. There are three ways to do this: download and run the binary scanner jar, generate a Liberty readiness report in the tWAS Admin Console, or use the tWAS wsadmin migration commands. The latter two methods do not require any additional software, and they are built-in functionalities of tWAS.
Yup! You right.
Hlo, you need to understand what the tools do and how many applications you are going to migrate to Liberty.