Transformation Advisor Data Collection
The Migration Toolkit for Application Binaries can generate a data collection to be uploaded to IBM Cloud Transformation Advisor, where you can gain application modernization insights including common code discovery, application migration complexities, and estimate development costs as well as produce migration artifacts for containerized environments. Using the --ta action directs the Migration Toolkit for Application Binaries to generate Transformation Advisor compatible files which allow Transformation Advisor to report on runtime modernization for moving from traditional WebSphere to Liberty and to assist with operational modernization by producing migration artifacts to deploy your workloads in OpenShift and other Kubernetes environments. Using the Migration Toolkit for Application Binaries allows you to start gathering data before you have Transformation Advisor installed. For more information on Transformation Advisor, see IBM Cloud Transformation Advisor.
A Transformation Advisor data collection consists of one or more zip archives containing all the data needed for Transformation Advisor to provide insights on applications and related shared libraries. These archives include the analysis, inventory, and evaluation reports in both HTML and JSON formats as well as the relevant configuration files. The reports are produced for WebSphere Liberty, Open Liberty, and WebSphere traditional base in containers migration targets.
When using the --ta action, the only required parameter is the binaryInputPath, which is an absolute or relative path to a WebSphere traditional installation directory, an application binary file, or a directory that contains application binary files outside of a WebSphere installation environment. If the binaryInputPath points to a WebSphere traditional installation, server configuration is generated which is included in the Transformation Advisor set of migration artifacts.
When a WebSphere traditional installation is specified, use the --profile option to specify a comma-separated list of the profiles to scan. If no profile is specified, the default profile is scanned.
When scanning a single application or folder of applications outside of a WebSphere traditional installation, the --sourceAppServer and --sourceJava options are required.
It is recommended to identify your custom application class packages with the --includePackages option. By doing so, you avoid scanning Java EE and third-party packages which should not affect your migration effort. If no --includePackages or --excludePackages options are specified, the tool excludes Java EE and some third-party packages by default. These packages are identified as scan options near the beginning of the generated reports.
java -jar binaryAppScanner.jar --help --ta
The following examples demonstrate different ways to generate Transformation Advisor data collections using the command options.