proc_analyzing-single-app-with-mta-cli.adoc

Analyzing a single application

To assess the effort required to migrate a specific application, you can analyze this application individually by using the {ProductFullName} command-line interface (CLI).

The analysis generates a report containing the details of the application migration effort, including potential migration issues. You can use the report to prioritize tasks and estimate the resources needed for the migration.

Note	Extracting the list of dependencies from compiled Java binaries is not always possible during the analysis, especially if the dependencies are not embedded within the binary.

Procedure

1. Optional: List available target technologies for an analysis:

   $ mta-cli analyze --list-targets

2. Run the analysis:

   $ mta-cli analyze --input <path_to_input> --output <path_to_output> --source <source_name> --target <target_name>

   Specify the following arguments:

   • --input: An application to be evaluated.

   • --output: An output directory for the generated reports. mta-cli analyze creates the following analysis reports:

     • analysis.log

     • dependencies.yaml

     • output.yaml

     • shim.log

     • static-report

     • static-report.log

   • --source: A source technology for the application migration, for example, weblogic.

   • --target: A target technology for the application migration, for example, eap8.

3. Access the generated analysis report:

   1. In the output of the mta-cli analyze command, copy a path to the index.html analysis report file:

      Report created: <output_report_directory>/index.html
                	Access it at this URL: file:///<output_report_directory>/index.html

   2. Paste the path to the browser of your choice.

   Alternatively, press Ctrl and click the path to the report file.

Additional resources

• Installing the CLI by using a .zip file

• The mta-cli analyze command options