Chapter 9. Analyzing applications with MTA

Procedure

1. In the Migration view, click Application inventory.
2. Select an application that you want to analyze.
3. Review the credentials assigned to the application.
4. Click Analyze.

5. Select the Analysis mode from the list:

   • Binary
   • Source code
   • Source code and dependencies
   • Upload a local binary. This option only appears if you are analyzing a single application. If you chose this option, you are prompted to Upload a local binary. Either drag a file into the area provided or click Upload and select the file to upload.
6. Click Next.

7. Select one or more target options for the analysis:

   • Application server migration to either of the following platforms:

     • JBoss EAP 7
     • JBoss EAP 8
   • Containerization
   • Quarkus
   • OracleJDK to OpenJDK

   • OpenJDK. Use this option to upgrade to either of the following JDK versions:

     • OpenJDK 11
     • OpenJDK 17
     • OpenJDK 21
   • Linux. Use this option to ensure that there are no Microsoft Windows paths hard-coded into your applications.
   • Jakarta EE 9. Use this option to migrate from Java EE 8.
   • Spring Boot on Red Hat Runtimes
   • Open Liberty
   • Camel. Use this option to migrate from Apache Camel 2 to Apache Camel 3 or from Apache Camel 3 to Apache Camel 4.
   • Azure App Service
8. Click Next.

9. Select one of the following Scope options to better focus the analysis:

   • Application and internal dependencies only.
   • Application and all dependencies, including known Open Source libraries.
   • Select the list of packages to be analyzed manually. If you choose this option, type the file name and click Add.
   • Exclude packages. If you choose this option, type the name of the package and click Add.
10. Click Next.

11. In Advanced, you can attach additional custom rules to the analysis by selecting the Manual or Repository mode:

    • In the Manual mode, click Add Rules. Drag the relevant files or select the files from their directory and click Add.

    • In the Repository mode, you can add rule files from a Git or Subversion repository.

      Important

      Attaching custom rules is optional if you have already attached a migration target to the analysis. If you have not attached any migration target, you must attach rules.

12. Optional: Set any of the following options:

    • Target
    • Source(s)
    • Excluded rules tags. Rules with these tags are not processed. Add or delete as needed.

    • Enable automated tagging. Select the checkbox to automatically attach tags to the application. This checkbox is selected by default.

      Note

      Automatically attached tags are displayed only after you run the analysis. You can attach tags to the application manually instead of enabling automated tagging or in addition to it.

      Note

      Analysis engines use standard rules for a comprehensive set of migration targets. However, if the target is not included, is a customized framework, or the application is written in a language that is not supported, for example, Ruby, you can add custom rules by skipping the target selection in the Set Target tab and uploading custom rule files in the Custom Rules tab. Only custom rule files that are uploaded manually are validated.

13. Click Next.
14. In Review, verify the analysis parameters.

15. Click Run.

    The analysis status is Scheduled as MTA downloads the image for the container to execute. When the image is downloaded, the status changes to In-progress.

    Note

    Analysis takes minutes to hours to run depending on the size of the application and the capacity and resources of the cluster.

    Note

    MTA relies on Kubernetes scheduling capabilities to determine how many analyzer instances are created based on cluster capacity. If several applications are selected for analysis, by default, only one analyzer can be provisioned at a time. With more cluster capacity, more analysis processes can be executed in parallel.

16. Optional: To track the status of your active analysis task, open the Task Manager drawer by clicking the notifications button.

    Alternatively, hover over the application name to display the pop-over window.

17. When analysis is complete, to see its results, open the application drawer by clicking on the application name.

Procedure

1. In the Migration view, click Application inventory.
2. Click on the application row to open the application drawer.
3. Click the Reports tab.
4. Click View analysis details for the activity log of the analysis.

5. Optional: For issues and dependencies found during the analysis, click the Details tab in the application drawer and click Issues or Dependencies.

   Alternatively, open the Issues or Dependencies page in the Migration view.

Procedure

1. Navigate to Advanced under Application analysis.
2. Select Options.
3. Check Enhanced advanced analysis details.
4. Run an analysis.

5. Access unmatched rules:

   1. Navigate to Reports in the side drawer.
   2. Click View analysis details, which opens the YAML/JSON format log view.
   3. Select the issues.yaml file.

   4. For each ruleset, there is an unmatched section that lists the rule IDs that do not find matching rules.

      

Procedure

1. In Administration view, click General.
2. Toggle the Allow reports to be downloaded after running an analysis. switch.
3. Go to the Migration view and click Application inventory.
4. Click on the application row to open the application drawer.
5. Click the Reports tab.

6. Click either the HTML or YAML link:

   • By clicking the HTML link, you download the compressed analysis-report-app-<application_name>.tar file. Extracting this file creates a folder with the same name as the application.
   • By clicking the YAML link, you download the uncompressed analysis-report-app-<application_name>.yaml file.