Chapter 6. Managing applications with MTA You can use the Migration Toolkit for Applications (MTA) user interface to perform the following tasks: Add applications Assign application credentials Import a list of applications Download a CSV template for importing application lists Create application migration waves Create Jira issues for migration waves MTA user interface applications have the following attributes: Name (free text) Description (optional, free text) Business service (optional, chosen from a list) Tags (optional, chosen from a list) Owner (optional, chosen from a list) Contributors (optional, chosen from a list) Source code (a path entered by the user) Binary (a path entered by the user) 6.1. Adding a new application You can add a new application to the Application Inventory for subsequent assessment and analysis. Tip Before creating an application, set up business services, check tags and tag categories, and create additions as needed. Prerequisites You are logged in to an MTA server. Procedure In the Migration view, click Application Inventory . Click Create new . 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). 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. 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. Click Create . The new application appears in the list of defined applications. Automated Tasks After adding a new application to the Application Inventory , you can set your cursor to hover over the application name to see the automated tasks spawned by adding the application. The language discovery task identifies the programming languages in the application. The technology discovery task identifies specific technologies in the application. The tasks automatically add appropriate tags to the application, reducing the effort involved in manually assigning tags to the application. After these tasks are complete, the number of tags added to the application will appear under the Tags column. To view the tags: Click on the application's row entry. A side pane opens. Click the Tags tab. The tags attached to the application are displayed. You can add additional tags manually as needed. When MTA analyzes the application, it can add additional tags to the application automatically. 6.2. Editing an application You can edit an existing application in the Application Inventory and re-run an assessment or analysis for this application. Prerequisites You are logged in to an MTA server. Procedure In the Migration view, click Application Inventory . Select the Migration working mode. Click Application Inventory in the left menu bar. A list of available applications appears in the main pane. Click Edit ( ) to open the application settings. Review the application settings. For a list of application settings, see Adding an application . If you changed any application settings, click Save . Note After editing an application, MTA re-spawns the language discovery and technology discovery tasks. 6.3. Assigning credentials to an application You can assign credentials to one or more applications. Procedure In the Migration view, click Application inventory . Click the Options menu ( ) to the right of Analyze and select Manage credentials . Select one credential from the Source credentials list and from the Maven settings list. Click Save . 6.4. Importing a list of applications You can import a .csv file that contains a list of applications and their attributes to the Migration Toolkit for Applications (MTA) user interface. Note Importing a list of applications does not overwrite any of the existing applications. Procedure Review the import file to ensure it contains all the required information in the required format. In the Migration view, click Application Inventory . Click the Options menu ( ). Click Import . Select the desired file and click Open . Optional: Select Enable automatic creation of missing entities . This option is selected by default. Verify that the import has completed and check the number of accepted or rejected rows. 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 . 6.5. Downloading a CSV template You can download a CSV template for importing application lists by using the Migration Toolkit for Applications (MTA) user interface. Procedure In the Migration view, click Application inventory . Click the Options menu ( ) to the right of Review . Click Manage imports to open the Application imports page. Click the Options menu ( ) to the right of Import . Click Download CSV template . 6.6. Creating a migration wave A migration wave is a group applications that you can migrate on a given schedule. You can track each migration by exporting a list of the wave's applications to the Jira issue management system. This automatically creates a separate Jira issue for each application of the migration wave. Procedure In the Migration view, click Migration waves . Click Create new . The New migration wave window opens. Enter the following information: Name (optional). If the name is not given, you can use the start and end dates to identify migration waves. 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) Click Create . The new migration wave appears in the list of existing migration waves. 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. Select the checkboxes of the applications that you want to assign to the migration wave. 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. Optional: To update a migration wave, select Update from the migration wave's Options menu ( ). The Update migration wave window opens. 6.7. Creating Jira issues for a migration wave You can use a migration wave to create Jira issues automatically for each application assigned to the migration wave. 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 Note You cannot delete an application if it is linked to a Jira ticket or is associated with a migration wave. To unlink the application from the Jira ticket, click the Unlink from Jira icon in the details view of the application or in the details view of a migration wave. Prerequisites You configured Jira connection. For more information, see Creating and configuring a Jira connection . Procedure In the Migration view, click Migration waves . 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. Select the Jira Cloud or Jira Server/Datacenter instance type. Select the instance, project, and issue type from the lists. Click Export . The status of the migration wave on the Migration waves page changes to Issues Created . Optional: To see the status of each individual application of a migration wave, click the Status column. Optional: To see if any particular application is associated with a migration wave, open the application's Details tab on the Application inventory page.

Commands: