Procedure

1. In the OpenShift Container Platform web console, click Operators → OperatorHub.
2. Use the Filter by keyword field to search for MTA.
3. Click the Migration Toolkit for Applications Operator and then click Install.
4. On the Install Operator page, click Install.
5. Click Operators → Installed Operators to verify that the MTA Operator appears in the openshift-mta project with the status Succeeded.
6. Click the MTA Operator.

7. Under Provided APIs, locate Tackle, and click Create Instance.

   The Create Tackle window opens in Form view.

8. Review the CR settings. The default choices should be acceptable, but make sure to check the system requirements for storage, memory, and cores.

9. If you prefer to work directly with the YAML file, click YAML view and review the CR settings that are listed in the spec section of the YAML file.

   The most commonly used CR settings are listed in this table:

   Table 3.2. Tackle CR settings

   Name	Default	Description
   cache_data_volume_size	100 GiB	Size requested for the cache volume; ignored when rwx_supported=false
   cache_storage_class	Default storage class	Storage class used for the cache volume; ignored when rwx_supported=false
   feature_auth_required	True	Flag to indicate whether keycloak authorization is required (single user/“noauth”)
   feature_isolate_namespace	True	Flag to indicate whether namespace isolation using network policies is enabled
   hub_database_volume_size	5 GiB	Size requested for the Hub database volume
   hub_bucket_volume_size	100 GiB	Size requested for the Hub bucket volume
   hub_bucket_storage_class	Default storage class	Storage class used for the bucket volume
   keycloak_database_data_volume_size	1 GiB	Size requested for the Keycloak database volume
   pathfinder_database_data_volume_size	1 GiB	Size requested for the Pathfinder database volume
   maven_data_volume_size	100 GiB	Size requested for the Maven m2 cache volume; deprecated in MTA 6.0.1
   rwx_storage_class	NA	Storage class requested for the Tackle RWX volumes; deprecated in MTA 6.0.1
   rwx_supported	True	Flag to indicate whether the cluster storage supports RWX mode
   rwo_storage_class	NA	Storage class requested for the Tackle RW0 volumes
   rhsso_external_access	False	Flag to indicate whether a dedicated route is created to access the MTA managed RHSSO instance

   Example YAML file

   kind: Tackle
   apiVersion: tackle.konveyor.io/v1alpha1
   metadata:
     name: mta
     namespace: openshift-mta
   spec:
     hub_bucket_volume_size: "25Gi"
     maven_data_volume_size: "25Gi"
     rwx_supported: "false"

10. Edit the CR settings if needed, and then click Create.
11. In Administrator view, click Workloads → Pods to verify that the MTA pods are running.
12. Access the user interface from your browser by using the route exposed by the mta-ui application within OpenShift.

13. Use the following credentials to log in:

    • User name: admin
    • Password: Passw0rd!
14. When prompted, create a new password.

Procedure

1. In the Administrator view, click Proxy.
2. Toggle HTTP proxy or HTTPS proxy to enable the proxy connection.

3. Enter the following information:

   • Proxy host
   • Proxy port
4. Optional: Toggle HTTP proxy credentials or HTTPS proxy credentials to enable authentication.
5. Click Insert.

1. Create stakeholder groups
2. Create job functions
3. Create stakeholders

1. Create tag types
2. Create tags

Procedure

1. In Development 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 Developers view.

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

Procedure

1. In Development view, click Application inventory.
2. Select the application with the completed assessment to copy.
3. Click the Options menu at the right of the selected application.
4. Select Copy assessment or Copy assessment and review.
5. Select the application(s) to which you want to apply the completed assessment.
6. Click Copy.

Procedure

1. In Development 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, set Custom rules by typing a name or by searching and clicking Add Rules.

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.

      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

      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 Development view, click Application inventory.
2. Expand the application with a completed analysis.
3. Click Report.
4. Click the dependencies or source links.
5. Click the tabs to review the report.

Procedure

1. In Developer view, click Application Inventory.
2. Click Create new.

3. Enter the following information or choose from a list:

   • Name
   • Description (optional)
   • Business service (optional)
   • Tags (optional; one or more)
   • Comments (optional)
4. Click the arrow to the left of Source Code.

5. Enter the following information or choose from a list:

   • Repository type
   • Source repository
   • Branch
   • Root path
6. Click the arrow to the left of Binary.

7. Enter the following information:

   • Group
   • Artifact
   • Version
   • Packaging
8. Click Create.

Procedure

1. In Developer view, click Application inventory.
2. Click the Analysis tab.
3. Click the Options menu to the right of Analyze and select Manage credentials.
4. Select one credential each from the Source credentials list and from the Maven settings list.
5. Click Save.

Procedure

1. Review the import file to ensure it contains all the required information in the required format.
2. In Developer view, click Application Inventory.
3. Click the Options menu to the right of Review.
4. Click Import.
5. Browse to the desired file and click Open.
6. Optional: Select Enable automatic creation of missing entities. By default, this option is selected.
7. Verify the import has completed and check the number of rows accepted or rejected.

8. Review the imported applications by clicking the arrow to the left of the checkbox.

   Important

   Rows accepted may not match the number of applications in the Application inventory list because some rows are dependencies. To verify, check the Record Type column of the CSV file for applications defined as 1 and dependencies as 2.

Procedure

1. In Developer view, click Application inventory.
2. Click the Options menu to the right of Review.
3. Click Manage imports to open the Application imports page.
4. Click the Options menu to the right of Import and then click Download CSV template.