Chapter 6. Assessing and analyzing applications

Procedure

1. In Migration view, click Application inventory.

2. Select the application you want to assess.

   Note

   Only one application can be assessed at a time.

3. Click Assess.

4. Select Stakeholders and Stakeholder groups from the lists to track who contributed to the assessment for future reference.

   Note

   You can add Stakeholder Groups or Stakeholders on the Controls screen of Migration view.

5. Click Next.
6. Answer each question and then click Next.
7. Click Save and Review to view the assessment.

Procedure

1. In Migration view, click Application inventory.

2. Select the application you want to review.

   Note

   Only one application can be reviewed at a time.

3. Click Review.
4. Select Proposed action and Effort estimate from the lists. Set Business criticality and Work priority.

5. Click Submit review.

   The fields from Review are now populated on the Application details page.

Procedure

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

6. Select the Analysis mode from the list. Valid options are:

   • Binary.
   • Source code.
   • Source code and dependencies.
   • Upload a local binary. This option only appears if you are analyzing a single application.
7. If you choose Upload a local binary, a window opens and you are prompted to Upload a local binary. Either drag and drop a file into the area provided or click Upload and then select the file to upload.
8. Click Next.

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

   • Application server migration to:

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

   • OpenJDK - upgrades to one of the following JDK versions:

     • OpenJDK 11
     • OpenJDK 17
   • Linux - ensures there are no Microsoft Windows paths hard-coded into your applications
   • Jakarta EE 9 - for migrating from Java EE 8 to Jakarta EE 9
   • Spring Boot on Red Hat Runtimes
   • Open Liberty
   • Camel - for migrating from Apache Camel 2 to Apache Camel 3

   • Azure

     • Azure App Service
10. Click Next.

11. 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 name and click Add.
12. Click Next.

13. In Advanced, you can attach additional custom rules to the analysis. Select Manual or Repository.

    Note

    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.

    • In Manual mode, click Add Rules. Then either drag and drop the relevant files or select them from their directory and click Add.
    • In Repository mode, you can add rule files from a Git or Subversion repository.

14. Set any of the following options, if needed:

    • Target
    • Source(s)
    • Excluded rules tags: Rules with these tags are not processed. Add or delete as needed.
    • Enable transaction report: Select the checkbox to generate a DIVA report that displays the call stack, which executes operations on relational database tables.

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

      Note

      The Transactions report is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

      Note

      Note that the 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, but if the target is not included or is a customized framework, custom rules can be added. Custom rules files are validated.

15. Click Next.
16. In Review, verify the analysis parameters.

17. Click Run.

    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.

    Tip

    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.

18. When analysis is complete, you can click the Report link to see the results of the analysis.

Procedure

1. In Administration view, click Custom migration targets.
2. Click Create new.
3. Fill in the name and description of the target.
4. In the Image section, upload an image file for the target’s icon. The file can be in either PNG or JPEG format, up to 1 MB. If you do not upload any file, a default icon is used.

5. In the Custom rules section, select either Upload manually or Retrieve from a repository.

   • If you have selected Upload manually, upload or drag and drop the required rule files from your local drive.

   • If you have selected Retrieve from a repository, proceed as follows:

     1. Choose Git or Subversion.
     2. Fill in Source repository, Branch and Root path.
     3. If the repository requires credentials, enter them in the Associated credentials field.

6. Click Create.

   The new migration target appears on the Custom migration targets page. It can now be used by non-admin users in Migration view.

Procedure

1. In Migration view, click Application inventory.
2. Expand the application with a completed analysis.
3. Click Reports.
4. Click the dependencies or source links.
5. Click the tabs to review the report.