Chapter 7. Working with Applications

Procedure

1. In Migration 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)
   • Owner (optional)
   • Contributors (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 Migration 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 Migration 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 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 and then click Download CSV template.

Procedure

1. In Migration view, click Migration waves.

2. Click Create new.

   The New migration wave window opens.

3. Enter the following information or select from drop-down lists:

   • Name (optional; if not given, you can use the start and end dates to identify migration waves)
   • Potential start date; it must be later than the current date
   • Potential end date; it 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 a migration wave, click the Options menu ( ) to the right of the migration wave and select Manage applications from the menu.

   The Manage applications window opens. The window 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 and 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.

7. To update a migration wave, select Update from its Options menu (three dots).

   The Update migration wave window opens.

Procedure

1. In 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 instance type (Jira Cloud or Jira Server/Datacenter).
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. To see the status of each individual application of a migration wave, click the Status column.

   A separate Jira issue is created for each application associated with the migration wave. The following fields of each issue are filled in automatically:

   • Title: Migrate <application name>
   • Reporter: Username of the token owner
   • Description: Created by Konveyor