Chapter 5. Managing applications with

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.