Procedure

1. In the Administration view, click Proxy.
2. Enable the HTTP proxy or HTTPS proxy switch to enable the proxy connection.

3. Enter the following information:

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

Procedure

1. In the Migration view, click Custom migration targets.
2. Click Create new.
3. Enter the name and description of the target.

4. Click the Provider drop-down menu and choose the language provider.

   Important

   Support for the Python and Node.js language providers is available as a Technology Preview only.

5. In the Image section, upload an image file for the target’s icon. The file can be in either the PNG or JPEG format, up to 1 MB. If you do not upload any file, a default icon is used.

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

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

   • If you selected Retrieve from a repository, complete the following steps:

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

7. Click Create.

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

1. Create Stakeholder groups. Note that by default, no stakeholder groups are defined.
2. Create Job functions. The job function attribute classifies stakeholders and provides a list of default values that can be expanded.
3. Create Stakeholders.

Procedure

1. Create a stakeholder group:

   1. In the Migration view, click Controls.
   2. Click Stakeholder groups.
   3. Click Create new.

   4. Enter the following information:

      • Name
      • Description
      • Member(s)
   5. Click Create.

2. Create a new job function:

   1. In the Migration view, click Controls.
   2. Click Job functions.
   3. Click Create new.
   4. In the Name text box, enter a job function title.
   5. Click Create.

3. Create a new stakeholder:

   1. In the Migration view, click Controls.
   2. Click Stakeholders.
   3. Click Create new.

   4. Enter the following information:

      • Email
      • Name
      • Job function. Note that you can create custom functions .
      • Stakeholder group
   5. Click Create.

Procedure

1. In the Migration view, click Controls.
2. Click Business services.
3. Click Create new.

4. Enter the following information:

   • Name
   • Description
   • Owner
5. Click Create.

1. Create tag categories.
2. Create tags.

Procedure

1. Create a tag category:

   1. In the Migration view, click Controls.
   2. Click Tags.
   3. Click Create tag category.

   4. Enter the following information:

      • Name
      • Rank: The order in which the tags appear on the applications.
      • Color
   5. Click Create.

2. Create a tag:

   1. In the Migration view, click Controls.
   2. Click Tags.
   3. Click Create tag.

   4. Enter the following information:

      • Name
      • Tag category
   5. Click Create.

Procedure

1. In Administration view, click Credentials.
2. Click Create new.

3. Enter the following information:

   • Name
   • Description (optional)

4. In the Type list, select Basic Auth (Jira) or Bearer Token (Jira):

   • If you selected Basic Auth (Jira), complete the following steps:

     1. In the Email field, enter your email.

     2. In the Token field, depending on the specific Jira configuration, enter either your token generated on the Jira site or your Jira login password.

        Note

        To obtain a Jira token, you need to log in to the Jira site.

     3. Click Save.

        The new credential appears on the Credentials page.

   • If you selected Bearer Token (Jira), complete the following steps:

     1. In the Token field, enter your token generated on the Jira site.

     2. Click Save.

        The new credential appears on the Credentials page.

5. Optional: To edit the credential, click Edit.

Procedure

1. In Administration view, under Issue Management, click Jira.
2. Click Create new.

3. In the New instance window, enter the following information:

   • Name of the instance
   • URL of the web interface of your Jira account
   • Select either the Jira Cloud or Jira Server/Data center instance type from the list

   • Select credentials from the list

     Note

     If you selected Jira Cloud as an instance type, only Basic Auth credentials are displayed in the list.

     If you selected Jira Server/Data center as an instance type, both Basic Auth and Token Bearer credentials are displayed.

     Choose the type that is appropriate for the particular configuration of your Jira server or data center.

4. By default, a connection cannot be established with a server with an invalid certificate. To override this restriction, enable the Enable insecure communication switch.

5. Click Create.

   The new connection instance appears on the Jira configuration page.

Procedure

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

3. Under Basic information, enter the following fields:

   • Name: A unique name for the new application.
   • Description: A short description of the application (optional).
   • Business service: A purpose of the application (optional).
   • Manual tags: Software tags that characterize the application (optional, one or more).
   • Owner: A registered software owner from the drop-down list (optional).
   • Contributors: Contributors from the drop-down list (optional, one or more).
   • Comments: Relevant comments on the application (optional).

4. Click Source Code and enter the following fields:

   • Repository type: Git or Subversion.

   • Source repository: A URL of the repository where the software code is saved.

     • For Subversion: this must be either the URL to the root of the repository or a fully qualified URL which (optionally) includes the branch and nested directory. When fully qualified, the Branch and Root path must be blank.

   • Branch: An application code branch in the repository (optional).

     • For Git: this may be any reference; commit-hash, branch or tag.
     • For Subversion: this may be a fully qualified path to a branch or tag, for example, branches/stable or tags/stable. This must be blank when the Source repository URL includes the branch.

   • Root path: A root path inside the repository for the target application (optional).

     • For Subversion: this must be blank when the Source Repository URL includes the root path.

   NOTE: If you enter any value in either the Branch or Root path fields, the Source repository field becomes mandatory.

5. Optional: Click Binary and enter the following fields:

   • Group: The Maven group for the application artifact.
   • Artifact: The Maven artifact for the application.
   • Version: A software version of the application.
   • Packaging: The packaging for the application artifact, for example, JAR, WAR, or EAR.

   NOTE: If you enter any value in any of the Binary section fields, all fields automatically become mandatory.

6. Click Create. The new application appears in the list of defined applications.

7. Optional: Change the application settings by clicking Edit next to the application name:

   1. Make the required adjustments.
   2. Click Save.
   Note

   After editing an application, MTA recreates the language discovery and technology discovery tasks. For more information, see Displaying automated tasks.

Procedure

1. In the Application Inventory, hover over the application name to display the automated tasks.

2. Display the application tags:

   1. Click on the application’s row entry. A side pane opens.
   2. Click the Tags tab. The tags attached to the application are displayed.

Procedure

1. Download a CSV template for importing application lists:

   1. In the Migration 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.
   5. Click Download CSV template.
2. Add the list of applications to the .csv import file. Ensure the file contains all the required information in the required format.
3. In the Migration view, click Application Inventory.
4. Click the Options menu ( ).
5. Click Import.
6. Select the desired file and click Open.
7. Optional: Select Enable automatic creation of missing entities. This option is selected by default.

Verification

1. Verify that the import has completed and check the number of accepted or rejected rows.

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

   Important

   Accepted rows might 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 defined as 2.

Procedure

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

Procedure

1. Optional: Identify the application that does not have credentials assigned to it:

   1. In the Migration view, display the list of applications by clicking Application inventory.
   2. Hover over the application name that does not have credentials assigned to it. The application discovery tasks fail for such applications.
2. In the Administration view, click Credentials.

3. Set the default credentials:

   1. Click the Options menu ( ) to the right of the credential you want to set as default.

   2. Click Set as default.

      Alternatively, you can set default credentials directly when creating Maven or source code credentials. For more information, see the following procedures:

      • Configuring Maven credentials
      • Configuring source control credentials

Verification

1. In the Migration view, display the list of applications by clicking Application inventory.
2. Hover over the application name that does not have credentials assigned to it. Because you set default credentials, the application discovery tasks are restarted.

Procedure

1. In the Migration view, click Migration waves.
2. Click Create new. The New migration wave window opens.

3. Enter the following information:

   • Name (optional). If you do not provide a name, the migration wave can be identified by its start and end dates.
   • Potential start date. This date must be later than the current date.
   • Potential end date. This date must be later than the start date.
   • Stakeholders (optional)
   • Stakeholder groups (optional)
4. Click Create. The new migration wave appears in the list of existing migration waves.

5. To assign applications to the migration wave, click the Options menu ( ) to the right of the migration wave and select Manage applications.

   The Manage applications window opens that displays the list of applications that are not assigned to any other migration wave.

6. Select the checkboxes of the applications that you want to assign to the migration wave.

7. Click Save.

   Note

   The owner and the contributors of each application associated with the migration wave are automatically added to the migration wave’s list of stakeholders.

8. Optional: To update a migration wave, select Update from the migration wave’s Options menu ( ). The Update migration wave window opens.

Procedure

1. In the Migration view, click Migration waves.
2. Click the Options menu ( ) to the right of the migration wave for which you want to create Jira issues and select Export to Issue Manager. The Export to Issue Manager window opens.
3. Select the Jira Cloud or Jira Server/Datacenter instance type.
4. Select the instance, project, and issue type from the lists.
5. Click Export. The status of the migration wave on the Migration waves page changes to Issues Created.
6. Optional: To see the status of each individual application of a migration wave, click the Status column.
7. Optional: To see if any particular application is associated with a migration wave, open the application’s Details tab on the Application inventory page.

Procedure

1. In the MTA user interface, select the Migration view.
2. Click Application inventory in the left menu bar. A list of the available applications appears in the main pane.
3. Select the application you want to assess.
4. Click the Options menu ( ) at the right end of the row and select Assess from the drop-down menu.
5. From the list of available questionnaires, click Take for the desired questionnaire.

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

   Note

   You can also add Stakeholder Groups or Stakeholders in the Controls pane of the Migration view. For more information, see Configuring a migration toolkit for applications instance.

7. Click Next.
8. Answer each Application assessment question and click Next.
9. Click Save to review the assessment and proceed with the steps in Reviewing an application.

Procedure

1. In the Migration view, click Application inventory.
2. Select the application you want to review.

3. Review the application by performing either of the following actions:

   • Click Save and Review while assessing the application. For more information, see Assessing an application.
   • Click the Options menu ( ) at the right end of the row and select Review from the drop-down list.
4. Click Proposed action and select the action.
5. Click Effort estimate and set the level of effort required to perform the assessment with the selected questionnaire.
6. In the Business criticality field, enter how critical the application is to the business.
7. In the Work priority field, enter the application’s priority.
8. Optional: Enter the assessment questionnaire comments in the Comments field.

9. Click Submit review.

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

Procedure

1. In the Migration view, click Reports. The aggregated assessment report for all applications is displayed.

2. Depending on your scenario, perform one of the following actions:

   • Display a report on the data from a particular questionnaire:

     1. Select the required questionnaire from a drop-down list of all questionnaires in the Current landscape pane of the report. By default, all questionnaires are selected.
     2. In the Identified risks pane of the report, sort the displayed list by application name, level of risk, questionnaire, questionnaire section, question, and answer.

   • Display a report for a specific application:

     1. Click the link in the Applications column in the Identified risks pane of the report. The Application inventory page opens. The applications included in the link are displayed as a list.

     2. Click the required application. The Assessment side pane opens.

        • To see the assessed risk level for the application, open the Details tab.
        • To see the details of the assessment, open the Reviews tab.

Procedure

1. In the Migration view, click Controls.
2. Click the Tags tab.
3. Click Create tag.
4. In the Name field in the opened dialogue, enter a unique name for the tag.
5. Click the Tag category field and select the category tag to associate with the tag.
6. Click Create.

7. Optional: Edit the created tag or tag category:

   • Edit the tag:

     1. In the list of tag categories under the Tags tab, open the list of tags in the desired category.
     2. Select Edit from the drop-down menu and edit the tag name in the Name field.
     3. Click the Tag category field and select the category tag to associate with the tag.
     4. Click Save.

   • Edit the tag category:

     1. Under the Tags tab, select a defined tag category and click Edit.
     2. Edit the tag category’s name in the Name field.
     3. Edit the category’s Rank value.
     4. Click the Color field and select a color for the tag category.
     5. Click Save.

Procedure

1. In the Migration view, click Application inventory.
2. In the row of the required application, click Edit ( ). The Update application window opens.
3. Select the desired tags from the Select a tag(s) drop-down list.
4. Click Save.

Procedure

1. In the Migration view, click Application inventory.
2. Click the name of the required application. A side pane opens.
3. Click the Tags tab. The tags attached to the application are displayed.

Procedure

1. Open the MTA web console.
2. In the left menu, click Archetypes.
3. Click Create new archetype.

4. In the form that opens, enter the following information for the new archetype:

   • Name: A name of the new archetype (mandatory).
   • Description: A description of the new archetype (optional).
   • Criteria Tags: Tags that associate the assessed applications with the archetype (mandatory). If criteria tags are updated, the process to calculate the applications, which the archetype is associated with, is triggered again.
   • Archetype Tags: Tags that the archetype assesses in the application (mandatory).
   • Stakeholder(s): Specific stakeholders involved in the application development and migration (optional).
   • Stakeholders Group(s): Groups of stakeholders involved in the application development and migration (optional).
5. Click Create.

Procedure

1. Open the MTA web console.
2. Select the Migration view and click Archetype.
3. Click the Options menu ( ) and select Assess from the drop-down menu.
4. From the list of available questionnaires, click Take to select the desired questionnaire.
5. In the Assessment menu, answer the required questions.
6. Click Save.

Procedure

1. Open the MTA web console.
2. Select the Migration view and click Archetype.
3. Click the Options menu ( ) and select Review from the drop-down menu.
4. From the list of available questionnaires, click Take to select the desired assessment questionnaire.
5. In the Assessment menu, answer the required questions.
6. Select Save and Review. You will automatically be redirected to the Review tab.

7. Enter the following information:

   • Proposed Action: Proposed action required to complete the migration or modernization of the archetype.
   • Effort estimate: The level of effort required to perform the modernization or migration of the selected archetype.
   • Business criticality: The level of criticality of the application to the business.
   • Work Priority: The archetype’s priority.
8. Click Submit review.

Procedure

1. In the Migration view, click Analysis Profiles.
2. Click Create new to open the Create Analysis Profile window.
3. Enter a unique name for the configuration profile in the Profile Details page.
4. Click Next to go to the Configure analysis section. You can configure the analysis source, target platforms, and the scope of the dependency analysis.

5. Select the Analysis source 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 must 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 in Set targets 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 that you want to analyze manually. If you choose this option, type the file name and click Add.
   • Exclude packages. If you toggle this option on, type the name of the package and click Add.
10. Click Next.

11. In Advanced, you can attach 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:

    • Additional target labels
    • Additional source labels
    • Excluded rules labels. Rules with these labels are not processed. Add or delete as needed.
13. Click Next.
14. In Review, verify the analysis parameters.

15. Click Save.

    MTA saves the analysis profile on the Analysis Profiles page.

Procedure

1. In the Migration view, click Custom migration targets.
2. Click Create new.
3. Enter the name and description of the target.

4. Click the Provider drop-down menu and choose the language provider.

   Important

   Support for the Python and Node.js language providers is available as a Technology Preview only.

5. In the Image section, upload an image file for the target’s icon. The file can be in either the PNG or JPEG format, up to 1 MB. If you do not upload any file, a default icon is used.

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

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

   • If you selected Retrieve from a repository, complete the following steps:

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

7. Click Create.

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

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. In the Mode section, select Use analysis profile.

6. Select a pre-configured profile from the list for running an analysis.

   Note

   If the architect deletes a target profile, MTA also automatically deletes the analysis profile associated with the target profile.

7. Click Next

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

   Note

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

9. Enable enhanced analysis details.
10. Click Next.
11. In Review, verify the analysis parameters.

12. Click Run.

    The analysis status is Scheduled as MTA downloads the image for the container. When MTA downloads the image, 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.

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

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

1. Open the application view by clicking on the application name.

2. Click the Reports tab to download the results in HTML or YAML.

   Note

   You can download the report if the MTA Administrator has enabled the option to download reports after running an analysis on the General configuration page in the Administration view.

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.

Procedure

1. In the Migration view, click Task Manager.
2. Click the Options menu ( ) for the selected task.

3. Click Task details.

   Alternatively, click on the task status in the Status column.

Procedure

1. In the Migration view, click Task Manager.
2. Click the Options menu ( ) for the selected task.

3. Depending on your scenario, complete one of the following steps:

   • To enable Preemption for the task, select Enable preemption.
   • To disable Preemption for the task with enabled Preemption, select Disable preemption.

Procedure

1. In the MTA user interface, select the Administration working mode.
2. Click Source platform in the left menu bar to go to the Source platforms page.
3. Click Create new platform. The Create new platform dialog appears.

4. In the form, enter the following information:

   1. Name: A unique name for the source platform (CF) instance.
   2. Type: Select source platform from the drop down menu. For example, Cloud Foundry.
   3. URL: API URL of the source platform. For example, the API URL of CF platform.
   4. Credentials: Select the name of the Source Control credentials that you configured for the source platform.

5. Click Create.

   The source platform instance is created. A source platform instance can be linked with one or more applications.

Procedure

1. In the MTA user interface, select the Administration view.
2. Click Source platforms in the navigation menu to go to the Source platforms page.
3. Select a source platform on the Source platforms page.
4. Click the Options menu ( ) of a source platform.

5. Click Discover applications to open the Discover applications window.

   The discovery process imports all or selected applications deployed in the source platform instance to the Applications Inventory page on MTA.

6. Optional: Click +Add a name to enter one application per text field and repeat the process to add more than one application. For example, app-a.
7. Optional: Click +Add a space to enter one space per text field and repeat the process to add more than one space. For example, space1.

8. Click +Add an organization to enter at least one organization per text field and repeat the process to add more than one organization. For example, org1.

   Note

   For a CF instance, the application names field can contain glob expressions (globs), for example, app*.

9. Click Next to review the configuration.

10. Click Discover applications.

    This action triggers an application import task.

11. Close the Discover applications window.
12. Optional: Hover over the source platform name to check the status of the application import task and click the application import task to view the task details in YAML format.

Procedure

1. In the MTA user interface, select the Migration view.
2. Click the Options menu ( ) near Analyze.

3. Click Discover applications to open the Discover applications window.

   The discovery process imports all or selected applications that are deployed in the source platform instance to the Applications Inventory page on MTA.

4. Select the source platform name from the drop-down list for application discovery.
5. Click Next to navigate to the Filters.
6. Optional: Click +Add a name to enter one application per text field and repeat the process to add more than one application. For example, app-a.
7. Optional: Click +Add a space to enter one space per text field and repeat the process to add more than one space. For example, space1.

8. Click +Add an organization to enter at least one organization per text field and repeat the process to add more than one organization. For example, org1.

   Note

   For a CF instance, the application names field can contain globs. For example, app*.

9. Click Next to review the configuration.

10. Click Discover applications.

    This action triggers an application import task.

11. Close the Discover applications window.
12. Optional: Click the application import task to check the status of the task and to view the task details in YAML format.

Procedure

1. In the MTA user interface, select the Migration mode.
2. On the Application Inventory page, click the edit icon ( ) in an application. The Update application dialog appears.

3. Enter the following information in the form:

   1. Click Source platform and enter the following fields:

      1. Source platform: Select a source platform instance.

      2. Source platform coordinates: Configure the source platform coordinates in either way:

         1. Enter the source platform coordinates in the fields. For example, name and space for a CF instance.

         2. Enable the source platform coordinates to enter application coordinates in JSON. For example, a CF instance coordinates can be:

            {
                "name": ["example-app"],
                "space": ["example-space"]
            }

      3. name: Type the name of the application.
      4. space: Configure the CF space in which the app is deployed in the source platform.
4. Click Save and close the Update application dialog.

1. Click anywhere on the application row to open the application details view.
2. Click the Platform tab to verify the source platform coordinates that you configured.
3. Enable the JSON switch for the source platform coordinates to check the coordinates in JSON format.

Procedure

1. In the MTA user interface, select the Migration working view.

2. On the Application Inventory page, you can retrieve configuration for one or more applications:

   • Retrieve configuration for a single application:

     1. Select an application and click the Options menu ( ).
     2. Click Retrieve Configurations.

   • Retrieve configurations for multiple applications:

     1. Select the target applications or click the Select all option ( ).
     2. Click the Options menu near Analyze at the top and click Retrieve Configurations.
3. You can review the read-only configurations in the Retrieve Configurations dialog and click Retrieve. MTA triggers a task to retrieve configuration for each application.

Verification

1. Click an application row to open the application details view and click the Platform tab.
2. Review the discovery manifest with the retrieved configuration and download the JSON configuration, if necessary.

Procedure

1. In the Administration view, click Generators.

   On the Generators page, you can create, edit, and delete generators.

2. Click Create new generator.

3. Configure the following fields:

   1. In the Name field in the opened dialog, enter a unique name for the generator.
   2. Select Helm as the generator.

   3. Click Template repository to expand the section.

      1. Select a Repository type from Git or Subversion.
      2. Optional: Enter the URL of your repository that contains the Helm templates.
      3. Optional: Enter the Branch of your repository.
      4. Optional: Enter the Root path of your repository.
      5. Select the credentials to access your repository if it is private.

   4. Optional: Click Values and enter the new value for an attribute in the discovery manifest as a key-value pair.

      During asset generation, the generator overrides the value of the matching attribute in the discovery manifest with the value you enter.

   5. Optional: Click Parameters to enter parameters and their default values as a key-value pair.

      Parameter fields require user input before the template can generate assets.

      Note

      During template instantiation, parameters take precedence over values, and values take precedence over the configurations present in the discovery manifest.

4. Click Save. You can click anywhere on the generator row to open the details view that shows the generator configuration details, parameters, and values.

Procedure

1. In the Migration view, click Archetypes.

2. Click the Options menu ( ) of an archetype, and select Manage target profiles.

   The Target profiles for <archetype-name> appears.

3. Click Create new target profile.
4. In the Name field in the opened dialogue, enter a unique name for the target profile.
5. Click the Tag category field and select the category tag to associate with the tag.
6. Select specific generators and click the right arrow to move the generator from the Available generators list to the Chosen generators list.
7. (Optional) Select an analysis profile for the application from the list. You can download this profile configuration from the MTA CLI only if you select the profile from this list.
8. Click Create.

9. You can click on the archetype row to open the archetype detail view where the target profiles for the archetype are listed.

   Note

   If you delete a target profile, MTA also automatically deletes the analysis profile associated with the target profile.

Procedure

1. In the Migration view, click Applications.
2. Click the edit icon ( ) to update an imported application.

3. In the Update application dialog, click Asset repository and configure the following details:

   1. Select the Asset repository type from Git or Subversion.
   2. Enter the asset repository URL in the Asset repository field.
   3. Enter the Branch of your repository.
   4. Enter the Root path of your repository.
4. Click Save and close the Update application dialog.
5. Click Manage Credentials from the Options menu ( ) of the application.
6. Select the asset repository credential on the Manage Credentials dialog and close the dialog.

Procedure

1. In the Migration view, click Applications.
2. Click the Options menu ( ) of an application.
3. Click Generate assets to open the Generate assets dialog.
4. Select a target profile and click Next.
5. Click the toggle button to open the JSON view where you can enter the parameter values.
6. Click Next to review the configurations to generate assets.

7. Click Generate assets.

   You can view the generated assets in the asset repository that you configured.