User Interface Guide

Migration Toolkit for Applications 7.3

Use the Migration Toolkit for Applications user interface to group your applications into projects for analysis.

Red Hat Customer Content Services

Abstract

This guide describes how to use the Migration Toolkit for Applications user interface to accelerate large-scale application modernization efforts across hybrid cloud environments on Red Hat OpenShift.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Chapter 1. Introduction

1.1. About the User Interface Guide

This guide is for architects, engineers, consultants, and others who want to use the Migration Toolkit for Applications (MTA) user interface to accelerate large-scale application modernization efforts across hybrid cloud environments on Red Hat OpenShift. This solution provides insight throughout the adoption process, at both the portfolio and application levels: inventory, assess, analyze, and manage applications for faster migration to OpenShift via the user interface.

1.2. About the Migration Toolkit for Applications

What is the Migration Toolkit for Applications?

Migration Toolkit for Applications (MTA) accelerates large-scale application modernization efforts across hybrid cloud environments on Red Hat OpenShift. This solution provides insight throughout the adoption process, at both the portfolio and application levels: inventory, assess, analyze, and manage applications for faster migration to OpenShift via the user interface.

In MTA 7.1 and later, when you add an application to the Application Inventory, MTA automatically creates and executes language and technology discovery tasks. Language discovery identifies the programming languages used in the application. Technology discovery identifies technologies, such as Enterprise Java Beans (EJB), Spring, etc. Then, each task assigns appropriate tags to the application, reducing the time and effort you spend manually tagging the application.

MTA uses an extensive default questionnaire as the basis for assessing your applications, or you can create your own custom questionnaire, enabling you to estimate the difficulty, time, and other resources needed to prepare an application for containerization. You can use the results of an assessment as the basis for discussions between stakeholders to determine which applications are good candidates for containerization, which require significant work first, and which are not suitable for containerization.

MTA analyzes applications by applying one or more rulesets to each application considered to determine which specific lines of that application must be modified before it can be modernized.

MTA examines application artifacts, including project source directories and application archives, and then produces an HTML report highlighting areas needing changes.

How does the Migration Toolkit for Applications simplify migration?

The Migration Toolkit for Applications looks for common resources and known trouble spots when migrating applications. It provides a high-level view of the technologies used by the application.

MTA generates a detailed report evaluating a migration or modernization path. This report can help you to estimate the effort required for large-scale projects and to reduce the work involved.

1.3. About the user interface

The user interface for the Migration Toolkit for Applications allows a team of users to assess and analyze applications for risks and suitability for migration to hybrid cloud environments on Red Hat OpenShift.

Use the user interface to assess and analyze your applications to get insights about potential pitfalls in the adoption process, at both the portfolio and application levels as you inventory, assess, analyze, and manage applications for faster migration to OpenShift.

Chapter 2. User interface views

The Migration Toolkit for Applications (MTA) user interface has two views:

Administration view
Migration view

In Administration view, administrators can configure the instance environment, work with credentials and repositories, define HTTP and HTTPS proxies, create custom migration targets, manage issues, and add custom assessment questionnaires.

In Migration view, all authorized users can review reports, add applications for assessment and analysis. perform application assessments and analyses, create migration waves, view issues that could potentially impact migration, view the status of analysis and discovery tasks through Task Manager. The permissions of the different user roles — administrators, architects, and migrators — vary in this view.

Chapter 3. Installing the Migration Toolkit for Applications user interface

You can install the Migration Toolkit for Applications (MTA) user interface on all Red Hat OpenShift cloud services and Red Hat OpenShift self-managed editions.

Important

To be able to create MTA instances, you must first install the MTA Operator.

The MTA Operator is a structural layer that manages resources deployed on OpenShift, such as database, front end, and back end, to automatically create an MTA instance.

3.1. Persistent volume requirements

To successfully deploy, the MTA Operator requires 2 RWO persistent volumes (PVs) used by different components. If the rwx_supported configuration option is set to true, the MTA Operator requires an additional 2 RWX PVs that are used by Maven and the hub file storage. The PVs are described in the following table:

Table 3.1. Required persistent volumes
Name	Default size	Access mode	Description
`hub database`	`10Gi`	RWO	Hub database
`hub bucket`	`100Gi`	RWX	Hub file storage; required if the `rwx_supported` configuration option is set to `true`
`keycloak postgresql`	`1Gi`	RWO	Keycloak back end database
`cache`	`100Gi`	RWX	Maven m2 cache; required if the `rwx_supported` configuration option is set to `true`

3.2. Installing the Migration Toolkit for Applications Operator and the user interface

You can install the Migration Toolkit for Applications (MTA) and the user interface on Red Hat OpenShift versions 4.18, 4.17, 4.16.

Prerequisites

4 vCPUs, 8 GB RAM, and 40 GB persistent storage.
Any cloud services or self-hosted edition of Red Hat OpenShift on versions 4.18, 4.17, 4.16.
You must be logged in as a user with cluster-admin permissions.

For more information, see OpenShift Operator Life Cycles.

Procedure

In the Red Hat OpenShift web console, click Operators → OperatorHub.
Use the Filter by keyword field to search for MTA.
Click the Migration Toolkit for Applications Operator and then click Install.
On the Install Operator page, click Install.
Click Operators → Installed Operators to verify that the MTA Operator appears in the openshift-mta project with the status Succeeded.
Click the MTA Operator.
Under Provided APIs, locate Tackle, and click Create Instance.
The Create Tackle window opens in Form view.
Review the custom resource (CR) settings. The default choices should be acceptable, but make sure to check the system requirements for storage, memory, and cores.

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`	`100Gi`	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`	`10Gi`	Size requested for the Hub database volume
`hub_bucket_volume_size`	`100Gi`	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`	`1Gi`	Size requested for the Keycloak database volume
`keycloak_sso_req_passwd_update`	`true`	If the flag is set to `true`, users are required to update their password after their first login.
`pathfinder_database_data_volume_size`	`1Gi`	Size requested for the Pathfinder database volume
`maven_data_volume_size`	`100Gi`	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
`analyzer_container_limits_cpu`	`1`	Maximum number of CPUs the pod is allowed to use
`analyzer_container_limits_memory`	`1Gi`	Maximum amount of memory the pod is allowed to use. You can increase this limit if the pod displays `OOMKilled` errors.
`analyzer_container_requests_cpu`	`1`	Minimum number of CPUs the pod needs to run
`analyzer_container_requests_memory`	`1Gi`	Minimum amount of memory the pod needs to run
`ui_container_limits_cpu`	`500m`	Maximum number of CPUs the UI pod resource is allowed to use
`ui_container_limits_memory`	`800Mi`	Maximum amount of memory the UI pod resource is allowed to use. You can increase this limit if the pod displays `OOMKilled` errors.
`ui_container_requests_cpu`	`100m`	Minimum number of CPUs the UI pod resource needs to run
`ui_container_requests_memory`	`350Mi`	Minimum amount of memory the UI pod resource needs to run
`provider_java_container_limits_cpu`	`1`	Maximum number of CPUs the Java provider resource is allowed to use
`provider_java_container_limits_memory`	`2Gi`	Maximum amount of memory the Java provider resource is allowed to use. You can increase this limit if the pod displays `OOMKilled` errors.
`provider_java_container_requests_cpu`	`1`	Minimum number of CPUs the Java provider resource needs to run
`provider_java_container_requests_memory`	`2Gi`	Minimum amount of memory the Java provider resource needs to run

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"

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"

Copy to Clipboard

Edit the CR settings if needed, and then click Create.
In Administration view, click Workloads → Pods to verify that the MTA pods are running.
Access the user interface from your browser by using the route exposed by the mta-ui application within OpenShift.
Use the following credentials to log in:
- User name: admin
- Password: Passw0rd!
When prompted, create a new password.

3.2.1. Eviction threshold

Each node has a certain amount of memory allocated to it. Some of that memory is reserved for system services. The rest of the memory is intended for running pods. If the pods use more than their allocated amount of memory, an out-of-memory event is triggered and the node is terminated with a OOMKilled error.

To prevent out-of-memory events and protect nodes, use the --eviction-hard setting. This setting specifies the threshold of memory availability below which the node evicts pods. The value of the setting can be absolute or a percentage.

Example of node memory allocation settings

Node capacity: 32Gi
--system-reserved setting: 3Gi
--eviction-hard setting: 100Mi

The amount of memory available for running pods on this node is 28.9 GB. This amount is calculated by subtracting the system-reserved and eviction-hard values from the overall capacity of the node. If the memory usage exceeds this amount, the node starts evicting pods.

3.3. Red Hat Build of Keycloak

The MTA 7.3.0 uses Red Hat Build of Keycloak (RHBK) instance for user authentication and authorization.

The MTA operator manages the RHBK instance and configures a dedicated realm with necessary roles and permissions.

MTA-managed RHBK instance allows you to perform advanced RHBK configurations, such as adding a provider for User Federation or integrating identity providers. To access the RHBK Admin Console, enter the URL https://<_route_>/auth/admin in your browser by replacing < route > with the MTA web console address.

Example:

MTA web console: https://mta-openshiftmta.example.com/
RHBK Admin console: https://mta-openshiftmta.example.com/auth/admin

The admin credentials for RHBK are stored in a secret file named mta-keycloak-rhbk in the namespace where MTA is installed.

To retrieve your admin credentials, run the following command:

oc get secret mta-keycloak-rhbk -n openshift-mta -o json| jq -r '.data.password | @base64d'

$ oc get secret mta-keycloak-rhbk -n openshift-mta -o json| jq -r '.data.password | @base64d'

Copy to Clipboard

Additional resources

3.3.1. Roles, Personas, Users, and Permissions

MTA makes use of three roles, each of which corresponds to a persona:

Table 3.3. Roles and personas
Role	Persona
`tackle-admin`	Administrator
`tackle-architect`	Architect
`tackle-migrator`	Migrator

The roles are already defined in your RHBK instance. You do not need to create them.

If you are an MTA administrator, you can create users in your RHBK and assign each user one or more roles, one role per persona.

3.3.1.1. Roles, personas, and access to user interface views

Although a user can have more than one role, each role corresponds to a specific persona:

Administrator: An administrator has all the permissions that architects and migrators have, along with the ability to create some application-wide configuration parameters that other users can consume but cannot change or view. Examples: Git credentials, Maven settings.xml files.
Architect: A technical lead for the migration project who can run assessments and can create and modify applications and information related to them. An architect cannot modify or delete sensitive information, but can consume it. Example: Associate an existing credential to the repository of a specific application.
Migrator: A user who can analyze applications, but not create, modify, or delete them.

As described in User interface views, MTA has two views, Administration and Migration.

Only administrators can access Administration view. Architects and migrators have no access to Administration view, they cannot even see it.

Administrators can perform all actions supported by Migration view. Architects and migrators can see all elements of Migration view, but their ability to perform actions in Migration view depends on the permissions granted to their role.

The ability of administrators, architects, and migrators to access the Administration and Migration views of the MTA user interface is summarized in the table below:

Table 3.4. Roles vs. access to MTA views
Menu	Architect	Migrator	Admin
Administration	No	No	Yes
Migration	Yes	Yes	Yes

3.3.1.2. Roles and permissions

The following table contains the roles and permissions (scopes) that MTA seeds the managed RHBK instance with:

tackle-admin	Resource Name	Verbs
	addons	delete get post put
	adoptionplans	post get post put
	applications	delete get post put
	applications.facts	delete get post put
	applications.tags	delete get post put
	applications.bucket	delete get post put
	assessments	delete get patch post put
	businessservices	delete get post put
	dependencies	delete get post put
	identities	delete get post put
	imports	delete get post put
	jobfunctions	delete get post put
	proxies	delete get post put
	reviews	delete get post put
	settings	delete get post put
	stakeholdergroups	delete get post put
	stakeholders	delete get post put
	tags	delete get post put
	tagtypes	delete get post put
	tasks	delete get post put
	tasks.bucket	delete get post put
	tickets	delete get post put
	trackers	delete get post put
	cache	delete get
	files	delete get post put
	rulebundles	delete get post put

tackle-architect	Resource Name	Verbs
	addons	delete get post put
	applications.bucket	delete get post put
	adoptionplans	post
	applications	delete get post put
	applications.facts	delete get post put
	applications.tags	delete get post put
	assessments	delete get patch post put
	businessservices	delete get post put
	dependencies	delete get post put
	identities	get
	imports	delete get post put
	jobfunctions	delete get post put
	proxies	get
	reviews	delete get post put
	settings	get
	stakeholdergroups	delete get post put
	stakeholders	delete get post put
	tags	delete get post put
	tagtypes	delete get post put
	tasks	delete get post put
	tasks.bucket	delete get post put
	trackers	get
	tickets	delete get post put
	cache	get
	files	delete get post put
	rulebundles	delete get post put

tackle-migrator	Resource Name	Verbs
	addons	get
	adoptionplans	post
	applications	get
	applications.facts	get
	applications.tags	get
	applications.bucket	get
	assessments	get post
	businessservices	get
	dependencies	delete get post put
	identities	get
	imports	get
	jobfunctions	get
	proxies	get
	reviews	get post put
	settings	get
	stakeholdergroups	get
	stakeholders	get
	tags	get
	tagtypes	get
	tasks	delete get post put
	tasks.bucket	delete get post put
	tackers	get
	tickets	get
	cache	get
	files	get
	rulebundles	get

3.4. Installing and configuring the Migration Toolkit for Applications Operator in a Red Hat OpenShift Local environment

Red Hat OpenShift Local provides a quick and easy way to set up a local OpenShift cluster on your desktop or laptop. This local cluster allows you to test your applications and configuration parameters before sending them to production.

3.4.1. Operating system requirements

Red Hat OpenShift Local requires the following minimum version of a supported operating system:

3.4.1.1. Red Hat OpenShift Local requirements on Microsoft Windows

On Microsoft Windows, Red Hat OpenShift Local requires the Windows 10 Fall Creators Update (version 1709) or later. Red Hat OpenShift Local does not run on earlier versions of Microsoft Windows. Microsoft Windows 10 Home Edition is not supported.

3.4.1.2. Red Hat OpenShift Local requirements on macOS

On macOS, Red Hat OpenShift Local requires macOS 11 Big Sur or later. Red Hat OpenShift Local does not run on earlier versions of macOS.

3.4.1.3. Red Hat OpenShift Local requirements on Linux

On Linux, Red Hat OpenShift Local is supported only on the latest two Red Hat Enterprise Linux 8 and 9 minor releases and on the latest two stable Fedora releases.

When using Red Hat Enterprise Linux, the machine running Red Hat OpenShift Local must be registered with the Red Hat Customer Portal.

Ubuntu 18.04 LTS or later and Debian 10 or later are not supported and might require manual setup of the host machine.

3.4.1.3.1. Required software packages for Linux

Red Hat OpenShift Local requires the libvirt and NetworkManager packages to run on Linux:

On Fedora and Red Hat Enterprise Linux run:
```
sudo dnf install NetworkManager
```
```
sudo dnf install NetworkManager
```
Copy to Clipboard

On Debian/Ubuntu run:

sudo apt install qemu-kvm libvirt-daemon libvirt-daemon-system network-manager

sudo apt install qemu-kvm libvirt-daemon libvirt-daemon-system network-manager

Copy to Clipboard

3.4.2. Installing the Migration Toolkit for Applications Operator in a Red Hat OpenShift Local environment

To install Red Hat OpenShift Local:

Download the latest release of Red Hat OpenShift Local for your platform.
1. Download OpenShift Local.
2. Download pull secret.
Assuming you saved the archive in the ~/Downloads directory, follow these steps:
```
cd ~/Downloads
```
```
cd ~/Downloads
```
Copy to Clipboard
```
tar xvf crc-linux-amd64.tar.xz
```
```
tar xvf crc-linux-amd64.tar.xz
```
Copy to Clipboard

Copy the crc executable to it:

cp ~/Downloads/crc-linux-<version-number>-amd64/crc ~/bin/crc

cp ~/Downloads/crc-linux-<version-number>-amd64/crc ~/bin/crc

Copy to Clipboard

Add the ~/bin/crc directory to your $PATH variable:

export PATH=$PATH:$HOME/bin/crc

export PATH=$PATH:$HOME/bin/crc

Copy to Clipboard

echo 'export PATH=$PATH:$HOME/bin/crc' >> ~/.bashrc

echo 'export PATH=$PATH:$HOME/bin/crc' >> ~/.bashrc

Copy to Clipboard

To disable telemetry, run the following command:
```
crc config set consent-telemetry no
```
```
crc config set consent-telemetry no
```
Copy to Clipboard

Note

For macOS, download the relevant crc-macos-installer.pkg.

Navigate to Downloads using Finder.
Double-click on crc-macos-installer.pkg.

3.4.3. Setting up Red Hat OpenShift Local

The crc setup command performs operations to set up the environment of your host machine for the Red Hat OpenShift Local instance.

The crc setup command creates the ~/.crc directory.

Set up your host machine for Red Hat OpenShift Local:
```
crc setup
```
```
crc setup
```
Copy to Clipboard

3.4.4. Starting the Red Hat OpenShift Local instance

Red Hat OpenShift Local presets represent a managed container runtime, and the lower bounds of system resources required by the instance to run it.

Note

On Linux or macOS, ensure that your user account has permission to use the sudo command.
On Microsoft Windows, ensure that your user account can elevate to Administrator privileges.

The crc start command starts the Red Hat OpenShift Local instance and configured container runtime. It offers the following flags:

Flags	Type	Description	Default value
-b, --bundle	string	Bundle path/URI - absolute or local path, HTTP, HTTPS or docker URI, for example, `'https://foo.com/crc_libvirt_4.15.14_amd64.crcbundle', 'docker://quay.io/myorg/crc_libvirt_4.15.14_amd64.crcbundle:2.37.1'`	default `'/home/<user>/.crc/cache/ crc_libvirt_4.15.14_amd64.crcbundle'`
-c, –cpus	int	Number of CPU cores to assign to the instance	4
–disable-update-check		Do not check for update
-d, –disk-size	uint	Total size in GB of the disk used by the instance	31
-h, –help		Help for start
-m, –memory	int	`Mi` of memory to assign to the instance	10752
-n, –nameserver	string	IPv4 address of name server to use for the instance
-o, –output	string	Output format in JSON
-p, –pull-secret-file	string	File path of image pull secret (download from https://console.redhat.com/openshift/create/local)

It also offers the following global flags:

Flags Type Description Default value

Flags	Type	Description	Default value
–log-level	string	log level for example: * `debug` * `info` * `warn` * `error`	`info`

–log-level

string

log level for example:

* debug

* info

* warn

* error

info

The default configuration creates a virtual machine (VM) with 4 virtual CPUs, a disk size of 31 GB, and 10 GB of RAM. However, this default configuration is not sufficent to stably run MTA.

To increase the number of virtual CPUs to 6, the disk-size to 200 GB, and the memory to 20 GB, run crc config as follows:

crc config set cpus 6

crc config set cpus 6

Copy to Clipboard

crc config set disk-size 200

crc config set disk-size 200

Copy to Clipboard

crc config set memory 20480

$ crc config set memory 20480

Copy to Clipboard

To check the configuration, run:

crc config view

crc config view

Copy to Clipboard

Example Output

- consent-telemetry    : yes
- cpus                 : 6
- disk-size            : 200
- memory               : 16384

- consent-telemetry    : yes
- cpus                 : 6
- disk-size            : 200
- memory               : 16384

Copy to Clipboard

Note

Changes to the inputted configuration property are only applied when the CRC instance is started.

If you already have a running CRC instance, for this configuration change to take effect, stop the CRC instance with crc stop and restart it with crc start.

3.4.5. Checking the status of Red Hat OpenShift Local instance

To check the status of your Red Hat OpenShift Local instance, run:

crc status

crc status

Copy to Clipboard

Example Output

CRC VM:          Running
OpenShift:       Starting (v4.15.14)
RAM Usage:       9.25GB of 20.97GB
Disk Usage:      31.88GB of 212.8GB (Inside the CRC VM)
Cache Usage:     26.83GB
Cache Directory: /home/<user>/.crc/cache

CRC VM:          Running
OpenShift:       Starting (v4.15.14)
RAM Usage:       9.25GB of 20.97GB
Disk Usage:      31.88GB of 212.8GB (Inside the CRC VM)
Cache Usage:     26.83GB
Cache Directory: /home/<user>/.crc/cache

Copy to Clipboard

3.4.6. Configuration of the Migration Toolkit for Applications Operator in a Red Hat OpenShift Local environment

The following table shows the recommended minimum configurations of Red Hat OpenShift Local tested:

Memory (Gi)	CPU	Disk sze (Gi)
`20Gi`	5	`110Gi`
`20Gi`	5	`35Gi`, with the MTA Operator configurations `cache_data_volume_size` and `hub_bucket_volume_size` set to `5Gi`.

3.5. Adding minimum requirements for Java analyzer and discovery

There is a minimum requirement for the Java analyzer, and also the discovery task, which by default is set to 2 GB.

While this minimum requirement can be lowered to 1.5 GB, it is not recommended.

You can also increase this minimum requirement to more than 2 GB.

kind: Tackle
apiVersion: tackle.konveyor.io/v1alpha1
metadata:
  name: tackle
  namespace: openshift-mta
spec:
  feature_auth_required: 'true'
  provider_java_container_limits_memory: 2Gi
  provider_java_container_requests_memory: 2Gi

kind: Tackle
apiVersion: tackle.konveyor.io/v1alpha1
metadata:
  name: tackle
  namespace: openshift-mta
spec:
  feature_auth_required: 'true'
  provider_java_container_limits_memory: 2Gi
  provider_java_container_requests_memory: 2Gi

Copy to Clipboard

Note

To guarantee scheduling has the correct space, provider_java_container_limits_memory and provider_java_container_requests_memory should be assigned the same amount of space.

Chapter 4. Configuring the instance environment

You can configure the following in Administration view:

General
Credentials
Repositories
Proxy (HTTP and HTTPS proxy settings)
Custom migration targets
Issue management
Assessment questionnaires

4.1. General

You can enable or disable the following option:

Allow reports to be downloaded after running an analysis

4.2. Configuring credentials

You can configure the following types of credentials in Administration view:

Source control
Maven settings file
Proxy
Basic auth (Jira)
Bearer token (Jira)

4.2.1. Configuring source control credentials

You can configure source control credentials in the Credentials view of the Migration Toolkit for Applications (MTA) user interface.

Procedure

In Administration view, click Credentials.
Click Create new.
Enter the following information:
- Name
- Description (Optional)
In the Type list, select Source Control.
In the User credentials list, select Credential Type and enter the requested information:
- Username/Password
  - Username
  - Password (hidden)
- SCM Private Key/Passphrase
  - SCM Private Key
  - Private Key Passphrase (hidden)
    Note
    Type-specific credential information such as keys and passphrases is either hidden or shown as [Encrypted].
Click Create.
MTA validates the input and creates a new credential. SCM keys must be parsed and checked for validity. If the validation fails, the following error message is displayed: “not a valid key/XML file”.

4.2.2. Configuring Maven credentials

You can configure new Maven credentials in the Credentials view of the Migration Toolkit for Applications (MTA) user interface.

Procedure

In Administration view, click Credentials.
Click Create new.
Enter the following information:
- Name
- Description (Optional)
In the Type list, select Maven Settings File.
Upload the settings file or paste its contents.
Click Create.
MTA validates the input and creates a new credential. The Maven settings.xml file must be parsed and checked for validity. If the validation fails, the following error message is displayed: “not a valid key/XML file”.

4.2.3. Configuring proxy credentials

You can configure proxy credentials in the Credentials view of the Migration Toolkit for Applications (MTA) user interface.

Procedure

In Administration view, click Credentials.
Click Create new.
Enter the following information:
- Name
- Description (Optional)
In the Type list, select Proxy.
Enter the following information.
- Username
- Password
  Note
  Type-specific credential information such as keys and passphrases is either hidden or shown as [Encrypted].
Click Create.
MTA validates the input and creates a new credential.

4.3. Configuring repositories

You can configure the following types of repositories in Administration view:

Git
Subversion
Maven

4.3.1. Configuring Git repositories

You can configure Git repositories in the Repositories view of the Migration Toolkit for Applications (MTA) user interface.

Procedure

In Administration view, click Repositories and then click Git.
Toggle the Consume insecure Git repositories switch to the right.

4.3.2. Configuring subversion repositories

You can configure subversion repositories in the Repositories view of the Migration Toolkit for Applications (MTA) user interface.

Procedure

In Administration view, click Repositories and then click Subversion.
Toggle the Consume insecure Subversion repositories switch to the right.

4.3.3. Configuring a Maven repository and reducing its size

You can use the MTA user interface to both configure a Maven repository and to reduce its size.

4.3.3.1. Configuring a Maven repository

You can configure a Maven repository in the Repositories view of the Migration Toolkit for Applications (MTA) user interface.

Procedure

In Administration view, click Repositories and then click Maven.
Toggle the Consume insecure artifact repositories switch to the right.

4.3.3.2. Reducing the size of a Maven repository

You can reduce the size of a Maven repository in the Repositories view of the Migration Toolkit for Applications (MTA) user interface.

Note

If the rwx_supported configuration option of the Tackle CR is set to false, both the Local artifact repository field and the Clear repository button are disabled and this procedure is not possible.

Procedure

In Administration view, click Repositories and then click Maven.
Click the Clear repository link.
Note
Depending on the size of the repository, the size change may not be evident despite the function working properly.

4.4. Configuring HTTP and HTTPS proxy settings

You can configure HTTP and HTTPS proxy settings with this management module.

Procedure

In the Administration view, click Proxy.
Toggle HTTP proxy or HTTPS proxy to enable the proxy connection.
Enter the following information:
- Proxy host
- Proxy port
Optional: Toggle HTTP proxy credentials or HTTPS proxy credentials to enable authentication.
Click Insert.

4.5. Creating custom migration targets

Architects or users with admin permissions can create and maintain custom rulesets associated with custom migration targets. Architects can upload custom rule files and assign them to various custom migration targets. The custom migration targets can then be selected in the analysis configuration wizard.

By using ready-made custom migration targets, you can avoid configuring custom rules for each analysis run. This simplifies analysis configuration and execution for non-admin users or third-party developers.

Prerequisites

You are logged in as a user with admin permissions.

Procedure

In the Administration view, click Custom migration targets.
Click Create new.
Enter the name and description of the target.
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.
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.
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.
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.

4.6. Seeding an instance

If you are a project architect, you can configure the instance’s key parameters in the Controls window, before migration. The parameters can be added and edited as needed. The following parameters define applications, individuals, teams, verticals or areas within an organization affected or participating in the migration:

Stakeholders
Stakeholder groups
Job functions
Business services
Tag categories
Tags

You can create and configure an instance in any order. However, the suggested order below is the most efficient for creating stakeholders and tags.

Stakeholders:

Create Stakeholder groups
Create Job functions
Create Stakeholders

Tags:

Create Tag categories
Create Tags

Stakeholders and defined by:

Email
Name
Job function
Stakeholder groups

4.6.1. Creating a new stakeholder group

There are no default stakeholder groups defined. You can create a new stakeholder group by following the procedure below.

Procedure

In Migration view, click Controls.
Click Stakeholder groups.
Click Create new.
Enter the following information:
- Name
- Description
- Member(s)
Click Create.

4.6.2. Creating a new job function

Migration Toolkit for Applications (MTA) uses the job function attribute to classify stakeholders and provides a list of default values that can be expanded.

You can create a new job function, which is not in the default list, by following the procedure below.

Procedure

In Migration view, click Controls.
Click Job functions.
Click Create new.
Enter a job function title in the Name text box.
Click Create.

4.6.3. Creating a new stakeholder

You can create a new migration project stakeholder by following the procedure below.

Procedure

In Migration view, click Controls.
Click Stakeholders.
Click Create new.
Enter the following information:
- Email
- Name
- Job function - custom functions can be created
- Stakeholder group
Click Create.

4.6.4. Creating a new business service

Migration Toolkit for Applications (MTA) uses the business service attribute to specify the departments within the organization that use the application and that are affected by the migration.

You can create a new business service by following the procedure below.

Procedure

In Migration view, click Controls.
Click Business services.
Click Create new.
Enter the following information:
- Name
- Description
- Owner
Click Create.

4.6.5. Creating new tag categories

Migration Toolkit for Applications (MTA) uses tags in multiple categories and provides a list of default values. You can create a new tag category by following the procedure below.

Procedure

In Migration view, click Controls.
Click Tags.
Click Create tag category.
Enter the following information:
- Name
- Rank - the order in which the tags appear on the applications
- Color
Click Create.

4.6.5.1. Creating new tags

You can create a new tag, which is not in the default list, by following the procedure below.

Procedure

In Migration view, click Controls.
Click Tags.
Click Create tag.
Enter the following information:
- Name
- Tag category
Click Create.

Chapter 5. Creating and configuring a Jira connection

You can track application migrations by creating a Jira issue for each migration from within the MTA user interface. To be able to create Jira issues, you first need to do the following:

Create an MTA credential to authenticate to the API of the Jira instance that you create in the next step.
Create a Jira instance in MTA and establish a connection to that instance.

5.1. Configuring Jira credentials

To define a Jira instance in MTA and establish a connection to that instance, you must first create an MTA credential to authenticate to the Jira instance’s API.

Two types of credentials are available:

Basic auth - for Jira Cloud and a private Jira server or data center
Bearer Token - for a private Jira server or data center

To create an MTA credential, follow the procedure below.

Procedure

In Administration view, click Credentials.
The Credentials page opens.
Click Create new.
Enter the following information:
- Name
- Description (optional)
In the Type list, select Basic Auth (Jira) or Bearer Token (Jira):
- If you selected Basic Auth (Jira), proceed as follows:
  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), proceed as follows:
  1. In the Token field, enter your token generated on the Jira site.
  2. Click Save.
    The new credential appears on the Credentials page.

You can edit a credential by clicking Edit.

To delete a credential, click Delete.

Note

You cannot delete a credential that has already been assigned to a Jira connection instance.

5.2. Creating and configuring a Jira connection

To create a Jira instance in MTA and establish a connection to that instance, follow the procedure below.

Procedure

In Administration view, under Issue Management, click Jira.
The Jira configuration page opens.
Click Create new.
The New instance window opens.
Enter the following information:
- Name of the instance
- URL of the web interface of your Jira account
- Instance type - select either Jira Cloud or Jira Server/Data center from the list
- Credentials - select from the list
  Note
  If the selected instance type is Jira Cloud, only Basic Auth credentials are displayed in the list.
  If the selected instance type is Jira Server/Data center, 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.
By default, a connection cannot be established with a server with an invalid certificate. To override this restriction, toggle the Enable insecure communication switch.
Click Create.
The new connection instance appears on the Jira configuration page.
Once the connection has been established and authorized, the status in the Connection column becomes Connected.
If the Connection status becomes Not connected, click the status to see the reason for the error.

The Jira configuration table has filtering by Name and URL and sorting by Instance name and URL.

Note

A Jira connection that was used for creating issues for a migration wave cannot be removed as long as the issues exist in Jira, even after the migration wave is deleted.

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.

Chapter 7. Assessing and analyzing applications with MTA

You can use the Migration Toolkit for Applications (MTA) user interface to assess and analyze applications:

When adding to or editing the Application Inventory, MTA automatically spawns programming language and technology discovery tasks. The tasks apply appropriate tags to the application, reducing the time you spend tagging the application manually.
When assessing applications, MTA estimates the risks and costs involved in preparing applications for containerization, including time, personnel, and other factors. You can use the results of an assessment for discussions between stakeholders to determine whether applications are suitable for containerization.
When analyzing applications, MTA uses rules to determine which specific lines in an application must be modified before the application can be migrated or modernized.

7.1. The Assessment module features

The Migration Toolkit for Applications (MTA) Assessment module offers the following features for assessing and analyzing applications:

Assessment hub

The Assessment hub integrates with the Application inventory.

Enhanced assessment questionnaire capabilities

In MTA 7.0, you can import and export assessment questionnaires. You can also design custom questionnaires with a downloadable template by using the YAML syntax, which includes the following features:

Conditional questions: You can include or exclude questions based on the application or archetype if a certain tag is present on this application or archetype.
Application auto-tagging based on answers: You can define tags to be applied to applications or archetypes if a certain answer was provided.
Automated answers from tags in applications or archetypes.

For more information, see The custom assessment questionnaire.

Note

You can customize and save the default questionnaire. For more information, see The default assessment questionnaire.

Multiple assessment questionnaires

The Assessment module supports multiple questionnaires, relevant to one or more applications.

Archetypes

You can group applications with similar characteristics into archetypes. This allows you to assess multiple applications at once. Each archetype has a shared taxonomy of tags, stakeholders, and stakeholder groups. All applications inherit assessment and review from their assigned archetypes.

For more information, see Working with archetypes.

7.2. MTA assessment questionnaires

The Migration Toolkit for Applications (MTA) uses an assessment questionnaire, either default or custom, to assess the risks involved in containerizing an application.

The assessment report provides information about applications and risks associated with migration. The report also generates an adoption plan informed by the prioritization, business criticality, and dependencies of the applications submitted for assessment.

7.2.1. The default assessment questionnaire

Legacy Pathfinder is the default Migration Toolkit for Applications (MTA) questionnaire. Pathfinder is a questionnaire-based tool that you can use to evaluate the suitability of applications for modernization in containers on an enterprise Kubernetes platform.

Through interaction with the default questionnaire and the review process, the system is enriched with application knowledge exposed through the collection of assessment reports.

You can export the default questionnaire to a YAML file:

Example 7.1. The Legacy Pathfinder YAML file

name: Legacy Pathfinder
description: ''
sections:
  - order: 1
    name: Application details
    questions:
      - order: 1
        text: >-
          Does the application development team understand and actively develop
          the application?
        explanation: >-
          How much knowledge does the team have about the application's
          development or usage?
        answers:
          - order: 2
            text: >-
              Maintenance mode, no SME knowledge or adequate documentation
              available
            risk: red
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Little knowledge, no development (example: third-party or
              commercial off-the-shelf application)
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: Maintenance mode, SME knowledge is available
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Actively developed, SME knowledge is available
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: greenfield application
            risk: green
            rationale: ''
            mitigation: ''
      - order: 2
        text: How is the application supported in production?
        explanation: >-
          Does the team have sufficient knowledge to support the application in
          production?
        answers:
          - order: 3
            text: >-
              Multiple teams provide support using an established escalation
              model
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              External support provider with a ticket-driven escalation process;
              no inhouse support resources
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Separate internal support team, separate from the development
              team, with little interaction between the teams
            risk: red
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              SRE (Site Reliability Engineering) approach with a knowledgeable
              and experienced operations team
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              DevOps approach with the same team building the application and
              supporting it in production
            risk: green
            rationale: ''
            mitigation: ''
      - order: 3
        text: >-
          How much time passes from when code is committed until the application
          is deployed to production?
        explanation: What is the development latency?
        answers:
          - order: 3
            text: 2-6 months
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Not tracked
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: More than 6 months
            risk: red
            rationale: ''
            mitigation: ''
          - order: 4
            text: 8-30 days
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: 1-7 days
            risk: green
            rationale: ''
            mitigation: ''
          - order: 6
            text: Less than 1 day
            risk: green
            rationale: ''
            mitigation: ''
      - order: 4
        text: How often is the application deployed to production?
        explanation: Deployment frequency
        answers:
          - order: 3
            text: Between once a month and once every 6 months
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Not tracked
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: Less than once every 6 months
            risk: red
            rationale: ''
            mitigation: ''
          - order: 4
            text: Weekly
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: Daily
            risk: green
            rationale: ''
            mitigation: ''
          - order: 6
            text: Several times a day
            risk: green
            rationale: ''
            mitigation: ''
      - order: 5
        text: >-
          What is the application's mean time to recover (MTTR) from failure in
          a production environment?
        explanation: Average time for the application to recover from failure
        answers:
          - order: 5
            text: Less than 1 hour
            risk: green
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Not tracked
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: 1-7 days
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 2
            text: 1 month or more
            risk: red
            rationale: ''
            mitigation: ''
          - order: 4
            text: 1-24 hours
            risk: green
            rationale: ''
            mitigation: ''
      - order: 6
        text: Does the application have legal and/or licensing requirements?
        explanation: >-
          Legal and licensing requirements must be assessed to determine their
          possible impact (cost, fault reporting) on the container platform
          hosting the application. Examples of legal requirements: isolated
          clusters, certifications, compliance with the Payment Card Industry
          Data Security Standard or the Health Insurance Portability and
          Accountability Act. Examples of licensing requirements: per server,
          per CPU.
        answers:
          - order: 1
            text: Multiple legal and licensing requirements
            risk: red
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 2
            text: 'Licensing requirements (examples: per server, per CPU)'
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: >-
              Legal requirements (examples: cluster isolation, hardware, PCI or
              HIPAA compliance)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: None
            risk: green
            rationale: ''
            mitigation: ''
      - order: 7
        text: Which model best describes the application architecture?
        explanation: Describe the application architecture in simple terms.
        answers:
          - order: 3
            text: >-
              Complex monolith, strict runtime dependency startup order,
              non-resilient architecture
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 5
            text: Independently deployable components
            risk: green
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Massive monolith (high memory and CPU usage), singleton
              deployment, vertical scale only
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Massive monolith (high memory and CPU usage), non-singleton
              deployment, complex to scale horizontally
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: 'Resilient monolith (examples: retries, circuit breakers)'
            risk: green
            rationale: ''
            mitigation: ''
  - order: 2
    name: Application dependencies
    questions:
      - order: 1
        text: Does the application require specific hardware?
        explanation: >-
          OpenShift Container Platform runs only on x86, IBM Power, or IBM Z
          systems
        answers:
          - order: 3
            text: 'Requires specific computer hardware (examples: GPUs, RAM, HDDs)'
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Requires CPU that is not supported by red Hat
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: 'Requires custom or legacy hardware (example: USB device)'
            risk: red
            rationale: ''
            mitigation: ''
          - order: 4
            text: Requires CPU that is supported by red Hat
            risk: green
            rationale: ''
            mitigation: ''
      - order: 2
        text: What operating system does the application require?
        explanation: >-
          Only Linux and certain Microsoft Windows versions are supported in
          containers. Check the latest versions and requirements.
        answers:
          - order: 4
            text: Microsoft Windows
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Operating system that is not compatible with OpenShift Container
              Platform (examples: OS X, AIX, Unix, Solaris)
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: Linux with custom kernel drivers or a specific kernel version
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: 'Linux with custom capabilities (examples: seccomp, root access)'
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: Standard Linux distribution
            risk: green
            rationale: ''
            mitigation: ''
      - order: 3
        text: >-
          Does the vendor provide support for a third-party component running in
          a container?
        explanation: Will the vendor support a component if you run it in a container?
        answers:
          - order: 2
            text: No vendor support for containers
            risk: red
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Not recommended to run the component in a container
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: >-
              Vendor supports containers but with limitations (examples:
              functionality is restricted, component has not been tested)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Vendor supports their application running in containers but you
              must build your own images
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: Vendor fully supports containers, provides certified images
            risk: green
            rationale: ''
            mitigation: ''
          - order: 6
            text: No third-party components required
            risk: green
            rationale: ''
            mitigation: ''
      - order: 4
        text: Incoming/northbound dependencies
        explanation: Systems or applications that call the application
        answers:
          - order: 3
            text: >-
              Many dependencies exist, can be changed because the systems are
              internally managed
            risk: green
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 4
            text: Internal dependencies only
            risk: green
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Dependencies are difficult or expensive to change because they are
              legacy or third-party
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Many dependencies exist, can be changed but the process is
              expensive and time-consuming
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: No incoming/northbound dependencies
            risk: green
            rationale: ''
            mitigation: ''
      - order: 5
        text: Outgoing/southbound dependencies
        explanation: Systems or applications that the application calls
        answers:
          - order: 3
            text: Application not ready until dependencies are verified available
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Dependency availability only verified when application is
              processing traffic
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: Dependencies require a complex and strict startup order
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Limited processing available if dependencies are unavailable
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: No outgoing/southbound dependencies
            risk: green
            rationale: ''
            mitigation: ''
  - order: 3
    name: Application architecture
    questions:
      - order: 1
        text: >-
          How resilient is the application? How well does it recover from
          outages and restarts?
        explanation: >-
          If the application or one of its dependencies fails, how does the
          application recover from failure? Is manual intervention required?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Application cannot be restarted cleanly after failure, requires
              manual intervention
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Application fails when a soutbound dependency is unavailable and
              does not recover automatically
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: >-
              Application functionality is limited when a dependency is
              unavailable but recovers when the dependency is available
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Application employs resilient architecture patterns (examples:
              circuit breakers, retry mechanisms)
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Application containers are randomly terminated to test resiliency;
              chaos engineering principles are followed
            risk: green
            rationale: ''
            mitigation: ''
      - order: 2
        text: How does the external world communicate with the application?
        explanation: >-
          What protocols do external clients use to communicate with the
          application?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: 'Non-TCP/IP protocols (examples: serial, IPX, AppleTalk)'
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: TCP/IP, with host name or IP address encapsulated in the payload
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: 'TCP/UDP without host addressing (example: SSH)'
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: TCP/UDP encapsulated, using TLS with SNI header
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: HTTP/HTTPS
            risk: green
            rationale: ''
            mitigation: ''
      - order: 3
        text: How does the application manage its internal state?
        explanation: >-
          If the application must manage or retain an internal state, how is
          this done?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 3
            text: State maintained in non-shared, non-ephemeral storage
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 1
            text: Application components use shared memory within a pod
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              State is managed externally by another product (examples:
              Zookeeper or red Hat Data Grid)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Disk shared between application instances
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: Stateless or ephemeral container storage
            risk: green
            rationale: ''
            mitigation: ''
      - order: 4
        text: How does the application handle service discovery?
        explanation: How does the application discover services?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Uses technologies that are not compatible with Kubernetes
              (examples: hardcoded IP addresses, custom cluster manager)
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Requires an application or cluster restart to discover new service
              instances
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: >-
              Uses technologies that are compatible with Kubernetes but require
              specific libraries or services (examples: HashiCorp Consul,
              Netflix Eureka)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Uses Kubernetes DNS name resolution
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: Does not require service discovery
            risk: green
            rationale: ''
            mitigation: ''
      - order: 5
        text: How is the application clustering managed?
        explanation: >-
          Does the application require clusters? If so, how is clustering
          managed?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: 'Manually configured clustering (example: static clusters)'
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: Managed by an external off-PaaS cluster manager
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: >-
              Managed by an application runtime that is compatible with
              Kubernetes
            risk: green
            rationale: ''
            mitigation: ''
          - order: 4
            text: No cluster management required
            risk: green
            rationale: ''
            mitigation: ''
  - order: 4
    name: Application observability
    questions:
      - order: 1
        text: How does the application use logging and how are the logs accessed?
        explanation: How the application logs are accessed
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Logs are unavailable or are internal with no way to export them
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Logs are in a custom binary format, exposed with non-standard
              protocols
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: Logs are exposed using syslog
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Logs are written to a file system, sometimes as multiple files
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: 'Logs are forwarded to an external logging system (example: Splunk)'
            risk: green
            rationale: ''
            mitigation: ''
          - order: 6
            text: 'Logs are configurable (example: can be sent to stdout)'
            risk: green
            rationale: ''
            mitigation: ''
      - order: 2
        text: Does the application provide metrics?
        explanation: >-
          Are application metrics available, if necessary (example: OpenShift
          Container Platform collects CPU and memory metrics)?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: No metrics available
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 2
            text: Metrics collected but not exposed externally
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 3
            text: 'Metrics exposed using binary protocols (examples: SNMP, JMX)'
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Metrics exposed using a third-party solution (examples: Dynatrace,
              AppDynamics)
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Metrics collected and exposed with built-in Prometheus endpoint
              support
            risk: green
            rationale: ''
            mitigation: ''
      - order: 3
        text: >-
          How easy is it to determine the application's health and readiness to
          handle traffic?
        explanation: >-
          How do we determine an application's health (liveness) and readiness
          to handle traffic?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: No health or readiness query functionality available
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: Basic application health requires semi-complex scripting
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Dedicated, independent liveness and readiness endpoints
            risk: green
            rationale: ''
            mitigation: ''
          - order: 2
            text: Monitored and managed by a custom watchdog process
            risk: red
            rationale: ''
            mitigation: ''
          - order: 5
            text: Health is verified by probes running synthetic transactions
            risk: green
            rationale: ''
            mitigation: ''
      - order: 4
        text: What best describes the application's runtime characteristics?
        explanation: >-
          How would the profile of an application appear during runtime
          (examples: graphs showing CPU and memory usage, traffic patterns,
          latency)? What are the implications for a serverless application?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Deterministic and predictable real-time execution or control
              requirements
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Sensitive to latency (examples: voice applications, high frequency
              trading applications)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 3
            text: Constant traffic with a broad range of CPU and memory usage
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Intermittent traffic with predictable CPU and memory usage
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: Constant traffic with predictable CPU and memory usage
            risk: green
            rationale: ''
            mitigation: ''
      - order: 5
        text: How long does it take the application to be ready to handle traffic?
        explanation: How long the application takes to boot
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: More than 5 minutes
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: 2-5 minutes
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 3
            text: 1-2 minutes
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: 10-60 seconds
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: Less than 10 seconds
            risk: green
            rationale: ''
            mitigation: ''
  - order: 5
    name: Application cross-cutting concerns
    questions:
      - order: 1
        text: How is the application tested?
        explanation: >-
          Is the application is tested? Is it easy to test (example: automated
          testing)? Is it tested in production?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: No testing or minimal manual testing only
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: Minimal automated testing, focused on the user interface
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 3
            text: >-
              Some automated unit and regression testing, basic CI/CD pipeline
              testing; modern test practices are not followed
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Highly repeatable automated testing (examples: unit, integration,
              smoke tests) before deploying to production; modern test practices
              are followed
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Chaos engineering approach, constant testing in production
              (example: A/B testing + experimentation)
            risk: green
            rationale: ''
            mitigation: ''
      - order: 2
        text: How is the application configured?
        explanation: >-
          How is the application configured? Is the configuration method
          appropriate for a container? External servers are runtime
          dependencies.
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Configuration files compiled during installation and configured
              using a user interface
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Configuration files are stored externally (example: in a database)
              and accessed using specific environment keys (examples: host name,
              IP address)
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: Multiple configuration files in multiple file system locations
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Configuration files built into the application and enabled using
              system properties at runtime
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Configuration retrieved from an external server (examples: Spring
              Cloud Config Server, HashiCorp Consul)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 6
            text: >-
              Configuration loaded from files in a single configurable location;
              environment variables used
            risk: green
            rationale: ''
            mitigation: ''
      - order: 4
        text: How is the application deployed?
        explanation: >-
          How the application is deployed and whether the deployment process is
          suitable for a container platform
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 3
            text: Simple automated deployment scripts
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 1
            text: Manual deployment using a user interface
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: Manual deployment with some automation
            risk: red
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Automated deployment with manual intervention or complex promotion
              through pipeline stages
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Automated deployment with a full CI/CD pipeline, minimal
              intervention for promotion through pipeline stages
            risk: green
            rationale: ''
            mitigation: ''
          - order: 6
            text: Fully automated (GitOps), blue-green, or canary deployment
            risk: green
            rationale: ''
            mitigation: ''
      - order: 5
        text: Where is the application deployed?
        explanation: Where does the application run?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Bare metal server
            risk: green
            rationale: ''
            mitigation: ''
          - order: 2
            text: 'Virtual machine (examples: red Hat Virtualization, VMware)'
            risk: green
            rationale: ''
            mitigation: ''
          - order: 3
            text: 'Private cloud (example: red Hat OpenStack Platform)'
            risk: green
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Public cloud provider (examples: Amazon Web Services, Microsoft
              Azure, Google Cloud Platform)
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Platform as a service (examples: Heroku, Force.com, Google App
              Engine)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 7
            text: Other. Specify in the comments field
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 6
            text: Hybrid cloud (public and private cloud providers)
            risk: green
            rationale: ''
            mitigation: ''
      - order: 6
        text: How mature is the containerization process, if any?
        explanation: If the team has used containers in the past, how was it done?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Application runs in a container on a laptop or desktop
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: Some experience with containers but not yet fully defined
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Proficient with containers and container platforms (examples:
              Swarm, Kubernetes)
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: Application containerization has not yet been attempted
            risk: green
            rationale: ''
            mitigation: ''
      - order: 3
        text: How does the application acquire security keys or certificates?
        explanation: >-
          How does the application retrieve credentials, keys, or certificates?
          External systems are runtime dependencies.
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Hardware security modules or encryption devices
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Keys/certificates bound to IP addresses and generated at runtime
              for each application instance
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: Keys/certificates compiled into the application
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Loaded from a shared disk
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Retrieved from an external server (examples: HashiCorp Vault,
              CyberArk Conjur)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 6
            text: Loaded from files
            risk: green
            rationale: ''
            mitigation: ''
          - order: 7
            text: Not required
            risk: green
            rationale: ''
            mitigation: ''
thresholds:
  red: 5
  yellow: 30
  unknown: 5
riskMessages:
  red: ''
  yellow: ''
  green: ''
  unknown: ''
builtin: true

name: Legacy Pathfinder
description: ''
sections:
  - order: 1
    name: Application details
    questions:
      - order: 1
        text: >-
          Does the application development team understand and actively develop
          the application?
        explanation: >-
          How much knowledge does the team have about the application's
          development or usage?
        answers:
          - order: 2
            text: >-
              Maintenance mode, no SME knowledge or adequate documentation
              available
            risk: red
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Little knowledge, no development (example: third-party or
              commercial off-the-shelf application)
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: Maintenance mode, SME knowledge is available
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Actively developed, SME knowledge is available
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: greenfield application
            risk: green
            rationale: ''
            mitigation: ''
      - order: 2
        text: How is the application supported in production?
        explanation: >-
          Does the team have sufficient knowledge to support the application in
          production?
        answers:
          - order: 3
            text: >-
              Multiple teams provide support using an established escalation
              model
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              External support provider with a ticket-driven escalation process;
              no inhouse support resources
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Separate internal support team, separate from the development
              team, with little interaction between the teams
            risk: red
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              SRE (Site Reliability Engineering) approach with a knowledgeable
              and experienced operations team
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              DevOps approach with the same team building the application and
              supporting it in production
            risk: green
            rationale: ''
            mitigation: ''
      - order: 3
        text: >-
          How much time passes from when code is committed until the application
          is deployed to production?
        explanation: What is the development latency?
        answers:
          - order: 3
            text: 2-6 months
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Not tracked
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: More than 6 months
            risk: red
            rationale: ''
            mitigation: ''
          - order: 4
            text: 8-30 days
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: 1-7 days
            risk: green
            rationale: ''
            mitigation: ''
          - order: 6
            text: Less than 1 day
            risk: green
            rationale: ''
            mitigation: ''
      - order: 4
        text: How often is the application deployed to production?
        explanation: Deployment frequency
        answers:
          - order: 3
            text: Between once a month and once every 6 months
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Not tracked
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: Less than once every 6 months
            risk: red
            rationale: ''
            mitigation: ''
          - order: 4
            text: Weekly
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: Daily
            risk: green
            rationale: ''
            mitigation: ''
          - order: 6
            text: Several times a day
            risk: green
            rationale: ''
            mitigation: ''
      - order: 5
        text: >-
          What is the application's mean time to recover (MTTR) from failure in
          a production environment?
        explanation: Average time for the application to recover from failure
        answers:
          - order: 5
            text: Less than 1 hour
            risk: green
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Not tracked
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: 1-7 days
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 2
            text: 1 month or more
            risk: red
            rationale: ''
            mitigation: ''
          - order: 4
            text: 1-24 hours
            risk: green
            rationale: ''
            mitigation: ''
      - order: 6
        text: Does the application have legal and/or licensing requirements?
        explanation: >-
          Legal and licensing requirements must be assessed to determine their
          possible impact (cost, fault reporting) on the container platform
          hosting the application. Examples of legal requirements: isolated
          clusters, certifications, compliance with the Payment Card Industry
          Data Security Standard or the Health Insurance Portability and
          Accountability Act. Examples of licensing requirements: per server,
          per CPU.
        answers:
          - order: 1
            text: Multiple legal and licensing requirements
            risk: red
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 2
            text: 'Licensing requirements (examples: per server, per CPU)'
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: >-
              Legal requirements (examples: cluster isolation, hardware, PCI or
              HIPAA compliance)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: None
            risk: green
            rationale: ''
            mitigation: ''
      - order: 7
        text: Which model best describes the application architecture?
        explanation: Describe the application architecture in simple terms.
        answers:
          - order: 3
            text: >-
              Complex monolith, strict runtime dependency startup order,
              non-resilient architecture
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 5
            text: Independently deployable components
            risk: green
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Massive monolith (high memory and CPU usage), singleton
              deployment, vertical scale only
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Massive monolith (high memory and CPU usage), non-singleton
              deployment, complex to scale horizontally
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: 'Resilient monolith (examples: retries, circuit breakers)'
            risk: green
            rationale: ''
            mitigation: ''
  - order: 2
    name: Application dependencies
    questions:
      - order: 1
        text: Does the application require specific hardware?
        explanation: >-
          OpenShift Container Platform runs only on x86, IBM Power, or IBM Z
          systems
        answers:
          - order: 3
            text: 'Requires specific computer hardware (examples: GPUs, RAM, HDDs)'
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Requires CPU that is not supported by red Hat
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: 'Requires custom or legacy hardware (example: USB device)'
            risk: red
            rationale: ''
            mitigation: ''
          - order: 4
            text: Requires CPU that is supported by red Hat
            risk: green
            rationale: ''
            mitigation: ''
      - order: 2
        text: What operating system does the application require?
        explanation: >-
          Only Linux and certain Microsoft Windows versions are supported in
          containers. Check the latest versions and requirements.
        answers:
          - order: 4
            text: Microsoft Windows
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Operating system that is not compatible with OpenShift Container
              Platform (examples: OS X, AIX, Unix, Solaris)
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: Linux with custom kernel drivers or a specific kernel version
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: 'Linux with custom capabilities (examples: seccomp, root access)'
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: Standard Linux distribution
            risk: green
            rationale: ''
            mitigation: ''
      - order: 3
        text: >-
          Does the vendor provide support for a third-party component running in
          a container?
        explanation: Will the vendor support a component if you run it in a container?
        answers:
          - order: 2
            text: No vendor support for containers
            risk: red
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Not recommended to run the component in a container
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: >-
              Vendor supports containers but with limitations (examples:
              functionality is restricted, component has not been tested)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Vendor supports their application running in containers but you
              must build your own images
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: Vendor fully supports containers, provides certified images
            risk: green
            rationale: ''
            mitigation: ''
          - order: 6
            text: No third-party components required
            risk: green
            rationale: ''
            mitigation: ''
      - order: 4
        text: Incoming/northbound dependencies
        explanation: Systems or applications that call the application
        answers:
          - order: 3
            text: >-
              Many dependencies exist, can be changed because the systems are
              internally managed
            risk: green
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 4
            text: Internal dependencies only
            risk: green
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Dependencies are difficult or expensive to change because they are
              legacy or third-party
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Many dependencies exist, can be changed but the process is
              expensive and time-consuming
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: No incoming/northbound dependencies
            risk: green
            rationale: ''
            mitigation: ''
      - order: 5
        text: Outgoing/southbound dependencies
        explanation: Systems or applications that the application calls
        answers:
          - order: 3
            text: Application not ready until dependencies are verified available
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Dependency availability only verified when application is
              processing traffic
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: Dependencies require a complex and strict startup order
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Limited processing available if dependencies are unavailable
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: No outgoing/southbound dependencies
            risk: green
            rationale: ''
            mitigation: ''
  - order: 3
    name: Application architecture
    questions:
      - order: 1
        text: >-
          How resilient is the application? How well does it recover from
          outages and restarts?
        explanation: >-
          If the application or one of its dependencies fails, how does the
          application recover from failure? Is manual intervention required?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Application cannot be restarted cleanly after failure, requires
              manual intervention
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Application fails when a soutbound dependency is unavailable and
              does not recover automatically
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: >-
              Application functionality is limited when a dependency is
              unavailable but recovers when the dependency is available
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Application employs resilient architecture patterns (examples:
              circuit breakers, retry mechanisms)
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Application containers are randomly terminated to test resiliency;
              chaos engineering principles are followed
            risk: green
            rationale: ''
            mitigation: ''
      - order: 2
        text: How does the external world communicate with the application?
        explanation: >-
          What protocols do external clients use to communicate with the
          application?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: 'Non-TCP/IP protocols (examples: serial, IPX, AppleTalk)'
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: TCP/IP, with host name or IP address encapsulated in the payload
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: 'TCP/UDP without host addressing (example: SSH)'
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: TCP/UDP encapsulated, using TLS with SNI header
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: HTTP/HTTPS
            risk: green
            rationale: ''
            mitigation: ''
      - order: 3
        text: How does the application manage its internal state?
        explanation: >-
          If the application must manage or retain an internal state, how is
          this done?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 3
            text: State maintained in non-shared, non-ephemeral storage
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 1
            text: Application components use shared memory within a pod
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              State is managed externally by another product (examples:
              Zookeeper or red Hat Data Grid)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Disk shared between application instances
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: Stateless or ephemeral container storage
            risk: green
            rationale: ''
            mitigation: ''
      - order: 4
        text: How does the application handle service discovery?
        explanation: How does the application discover services?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Uses technologies that are not compatible with Kubernetes
              (examples: hardcoded IP addresses, custom cluster manager)
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Requires an application or cluster restart to discover new service
              instances
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: >-
              Uses technologies that are compatible with Kubernetes but require
              specific libraries or services (examples: HashiCorp Consul,
              Netflix Eureka)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Uses Kubernetes DNS name resolution
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: Does not require service discovery
            risk: green
            rationale: ''
            mitigation: ''
      - order: 5
        text: How is the application clustering managed?
        explanation: >-
          Does the application require clusters? If so, how is clustering
          managed?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: 'Manually configured clustering (example: static clusters)'
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: Managed by an external off-PaaS cluster manager
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: >-
              Managed by an application runtime that is compatible with
              Kubernetes
            risk: green
            rationale: ''
            mitigation: ''
          - order: 4
            text: No cluster management required
            risk: green
            rationale: ''
            mitigation: ''
  - order: 4
    name: Application observability
    questions:
      - order: 1
        text: How does the application use logging and how are the logs accessed?
        explanation: How the application logs are accessed
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Logs are unavailable or are internal with no way to export them
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Logs are in a custom binary format, exposed with non-standard
              protocols
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: Logs are exposed using syslog
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Logs are written to a file system, sometimes as multiple files
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: 'Logs are forwarded to an external logging system (example: Splunk)'
            risk: green
            rationale: ''
            mitigation: ''
          - order: 6
            text: 'Logs are configurable (example: can be sent to stdout)'
            risk: green
            rationale: ''
            mitigation: ''
      - order: 2
        text: Does the application provide metrics?
        explanation: >-
          Are application metrics available, if necessary (example: OpenShift
          Container Platform collects CPU and memory metrics)?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: No metrics available
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 2
            text: Metrics collected but not exposed externally
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 3
            text: 'Metrics exposed using binary protocols (examples: SNMP, JMX)'
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Metrics exposed using a third-party solution (examples: Dynatrace,
              AppDynamics)
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Metrics collected and exposed with built-in Prometheus endpoint
              support
            risk: green
            rationale: ''
            mitigation: ''
      - order: 3
        text: >-
          How easy is it to determine the application's health and readiness to
          handle traffic?
        explanation: >-
          How do we determine an application's health (liveness) and readiness
          to handle traffic?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: No health or readiness query functionality available
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: Basic application health requires semi-complex scripting
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Dedicated, independent liveness and readiness endpoints
            risk: green
            rationale: ''
            mitigation: ''
          - order: 2
            text: Monitored and managed by a custom watchdog process
            risk: red
            rationale: ''
            mitigation: ''
          - order: 5
            text: Health is verified by probes running synthetic transactions
            risk: green
            rationale: ''
            mitigation: ''
      - order: 4
        text: What best describes the application's runtime characteristics?
        explanation: >-
          How would the profile of an application appear during runtime
          (examples: graphs showing CPU and memory usage, traffic patterns,
          latency)? What are the implications for a serverless application?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Deterministic and predictable real-time execution or control
              requirements
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Sensitive to latency (examples: voice applications, high frequency
              trading applications)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 3
            text: Constant traffic with a broad range of CPU and memory usage
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Intermittent traffic with predictable CPU and memory usage
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: Constant traffic with predictable CPU and memory usage
            risk: green
            rationale: ''
            mitigation: ''
      - order: 5
        text: How long does it take the application to be ready to handle traffic?
        explanation: How long the application takes to boot
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: More than 5 minutes
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: 2-5 minutes
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 3
            text: 1-2 minutes
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: 10-60 seconds
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: Less than 10 seconds
            risk: green
            rationale: ''
            mitigation: ''
  - order: 5
    name: Application cross-cutting concerns
    questions:
      - order: 1
        text: How is the application tested?
        explanation: >-
          Is the application is tested? Is it easy to test (example: automated
          testing)? Is it tested in production?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: No testing or minimal manual testing only
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: Minimal automated testing, focused on the user interface
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 3
            text: >-
              Some automated unit and regression testing, basic CI/CD pipeline
              testing; modern test practices are not followed
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Highly repeatable automated testing (examples: unit, integration,
              smoke tests) before deploying to production; modern test practices
              are followed
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Chaos engineering approach, constant testing in production
              (example: A/B testing + experimentation)
            risk: green
            rationale: ''
            mitigation: ''
      - order: 2
        text: How is the application configured?
        explanation: >-
          How is the application configured? Is the configuration method
          appropriate for a container? External servers are runtime
          dependencies.
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: >-
              Configuration files compiled during installation and configured
              using a user interface
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Configuration files are stored externally (example: in a database)
              and accessed using specific environment keys (examples: host name,
              IP address)
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: Multiple configuration files in multiple file system locations
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Configuration files built into the application and enabled using
              system properties at runtime
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Configuration retrieved from an external server (examples: Spring
              Cloud Config Server, HashiCorp Consul)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 6
            text: >-
              Configuration loaded from files in a single configurable location;
              environment variables used
            risk: green
            rationale: ''
            mitigation: ''
      - order: 4
        text: How is the application deployed?
        explanation: >-
          How the application is deployed and whether the deployment process is
          suitable for a container platform
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 3
            text: Simple automated deployment scripts
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 1
            text: Manual deployment using a user interface
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: Manual deployment with some automation
            risk: red
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Automated deployment with manual intervention or complex promotion
              through pipeline stages
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Automated deployment with a full CI/CD pipeline, minimal
              intervention for promotion through pipeline stages
            risk: green
            rationale: ''
            mitigation: ''
          - order: 6
            text: Fully automated (GitOps), blue-green, or canary deployment
            risk: green
            rationale: ''
            mitigation: ''
      - order: 5
        text: Where is the application deployed?
        explanation: Where does the application run?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Bare metal server
            risk: green
            rationale: ''
            mitigation: ''
          - order: 2
            text: 'Virtual machine (examples: red Hat Virtualization, VMware)'
            risk: green
            rationale: ''
            mitigation: ''
          - order: 3
            text: 'Private cloud (example: red Hat OpenStack Platform)'
            risk: green
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Public cloud provider (examples: Amazon Web Services, Microsoft
              Azure, Google Cloud Platform)
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Platform as a service (examples: Heroku, Force.com, Google App
              Engine)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 7
            text: Other. Specify in the comments field
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 6
            text: Hybrid cloud (public and private cloud providers)
            risk: green
            rationale: ''
            mitigation: ''
      - order: 6
        text: How mature is the containerization process, if any?
        explanation: If the team has used containers in the past, how was it done?
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Application runs in a container on a laptop or desktop
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: Some experience with containers but not yet fully defined
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: >-
              Proficient with containers and container platforms (examples:
              Swarm, Kubernetes)
            risk: green
            rationale: ''
            mitigation: ''
          - order: 5
            text: Application containerization has not yet been attempted
            risk: green
            rationale: ''
            mitigation: ''
      - order: 3
        text: How does the application acquire security keys or certificates?
        explanation: >-
          How does the application retrieve credentials, keys, or certificates?
          External systems are runtime dependencies.
        answers:
          - order: 0
            text: unknown
            risk: unknown
            rationale: ''
            mitigation: ''
          - order: 1
            text: Hardware security modules or encryption devices
            risk: red
            rationale: ''
            mitigation: ''
          - order: 2
            text: >-
              Keys/certificates bound to IP addresses and generated at runtime
              for each application instance
            risk: red
            rationale: ''
            mitigation: ''
          - order: 3
            text: Keys/certificates compiled into the application
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 4
            text: Loaded from a shared disk
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 5
            text: >-
              Retrieved from an external server (examples: HashiCorp Vault,
              CyberArk Conjur)
            risk: yellow
            rationale: ''
            mitigation: ''
          - order: 6
            text: Loaded from files
            risk: green
            rationale: ''
            mitigation: ''
          - order: 7
            text: Not required
            risk: green
            rationale: ''
            mitigation: ''
thresholds:
  red: 5
  yellow: 30
  unknown: 5
riskMessages:
  red: ''
  yellow: ''
  green: ''
  unknown: ''
builtin: true

Copy to Clipboard

7.2.2. The custom assessment questionnaire

You can use the Migration Toolkit for Applications (MTA) to import a custom assessment questionnaire by using a custom YAML syntax to define the questionnaire. The YAML syntax supports the following features:

Conditional questions

The YAML syntax supports including or excluding questions based on tags existing on the application or archetype, for example:

If the application or archetype has the Language/Java tag, the What is the main JAVA framework used in your application? question is included in the questionnaire:

...
  questions:
    - order: 1
      text: What is the main JAVA framework used in your application?
      explanation: Identify the primary JAVA framework used in your application.
      includeFor:
        - category: Language
          tag: Java
...

...
  questions:
    - order: 1
      text: What is the main JAVA framework used in your application?
      explanation: Identify the primary JAVA framework used in your application.
      includeFor:
        - category: Language
          tag: Java
...

Copy to Clipboard

If the application or archetype has the Deployment/Serverless and Architecture/Monolith tag, the Are you currently using any form of container orchestration? question is excluded from the questionnaire:

...
  questions:
    - order: 4
      text: Are you currently using any form of container orchestration?
      explanation: Determine if the application utilizes container orchestration tools like Kubernetes, Docker Swarm, etc.
      excludeFor:
        - category: Deployment
          tag: Serverless
        - category: Architecture
          tag: Monolith
...

...
  questions:
    - order: 4
      text: Are you currently using any form of container orchestration?
      explanation: Determine if the application utilizes container orchestration tools like Kubernetes, Docker Swarm, etc.
      excludeFor:
        - category: Deployment
          tag: Serverless
        - category: Architecture
          tag: Monolith
...

Copy to Clipboard

Automated answers based on tags present on the assessed application or archetype

Automated answers are selected based on the tags existing on the application or archetype. For example, if an application or archetype has the Runtime/Quarkus tag, the Quarkus answer is automatically selected, and if an application or archetype has the Runtime/Spring Boot tag, the Spring Boot answer is automatically selected:

...
  text: What is the main technology in your application?
    explanation: Identify the main framework or technology used in your application.
      answers:
        - order: 1
          text: Quarkus
          risk: green
          autoAnswerFor:
            - category: Runtime
              tag: Quarkus
        - order: 2
          text: Spring Boot
          risk: green
          autoAnswerFor:
            - category: Runtime
              tag: Spring Boot
...

...
  text: What is the main technology in your application?
    explanation: Identify the main framework or technology used in your application.
      answers:
        - order: 1
          text: Quarkus
          risk: green
          autoAnswerFor:
            - category: Runtime
              tag: Quarkus
        - order: 2
          text: Spring Boot
          risk: green
          autoAnswerFor:
            - category: Runtime
              tag: Spring Boot
...

Copy to Clipboard

Automatic tagging of applications based on answers

During the assessment, tags are automatically applied to the application or archetype based on the answer if this answer is selected. Note that the tags are transitive. Therefore, the tags are removed if the assessment is discarded. Each tag is defined by the following elements:

category: Category of the target tag (String).
tag: Definition for the target tag as (String).

For example, if the selected answer is Quarkus, the Runtime/Quarkus tag is applied to the assessed application or archetype. If the selected answer is Spring Boot, the Runtime/Spring Boot tag is applied to the assessed application or archetype:

...
questions:
  - order: 1
    text: What is the main technology in your application?
    explanation: Identify the main framework or technology used in your application.
    answers:
      - order: 1
        text: Quarkus
        risk: green
        applyTags:
          - category: Runtime
            tag: Quarkus
      - order: 2
        text: Spring Boot
        risk: green
        applyTags:
          - category: Runtime
            tag: Spring Boot
...

...
questions:
  - order: 1
    text: What is the main technology in your application?
    explanation: Identify the main framework or technology used in your application.
    answers:
      - order: 1
        text: Quarkus
        risk: green
        applyTags:
          - category: Runtime
            tag: Quarkus
      - order: 2
        text: Spring Boot
        risk: green
        applyTags:
          - category: Runtime
            tag: Spring Boot
...

Copy to Clipboard

7.2.2.1. The YAML template for the custom questionnaire

You can use the following YAML template to build your custom questionnaire. You can download this template by clicking Download YAML template on the Assessment questionnaires page.

Example 7.2. The YAML template for the custom questionnaire

name: Uploadable Cloud Readiness Questionnaire Template
description: This questionnaire is an example template for assessing cloud readiness. It serves as a guide for users to create and customize their own questionnaire templates.
required: true
sections:
  - order: 1
    name: Application Technologies
    questions:
      - order: 1
        text: What is the main technology in your application?
        explanation: Identify the main framework or technology used in your application.
        includeFor:
          - category: Language
            tag: Java
        answers:
          - order: 1
            text: Quarkus
            risk: green
            rationale: Quarkus is a modern, container-friendly framework.
            mitigation: No mitigation needed.
            applyTags:
              - category: Runtime
                tag: Quarkus
            autoAnswerFor:
              - category: Runtime
                tag: Quarkus
          - order: 2
            text: Spring Boot
            risk: green
            rationale: Spring Boot is versatile and widely used.
            mitigation: Ensure container compatibility.
            applyTags:
              - category: Runtime
                tag: Spring Boot
            autoAnswerFor:
              - category: Runtime
                tag: Spring Boot
          - order: 3
            text: Legacy Monolithic Application
            risk: red
            rationale: Legacy monoliths are challenging for cloud adaptation.
            mitigation: Consider refactoring into microservices.
      - order: 2
        text: Does your application use a microservices architecture?
        explanation: Assess if the application is built using a microservices architecture.
        answers:
          - order: 1
            text: Yes
            risk: green
            rationale: Microservices are well-suited for cloud environments.
            mitigation: Continue monitoring service dependencies.
          - order: 2
            text: No
            risk: yellow
            rationale: Non-microservices architectures may face scalability issues.
            mitigation: Assess the feasibility of transitioning to microservices.
          - order: 3
            text: Unknown
            risk: unknown
            rationale: Lack of clarity on architecture can lead to unplanned issues.
            mitigation: Conduct an architectural review.

      - order: 3
        text: Is your application's data storage cloud-optimized?
        explanation: Evaluate if the data storage solution is optimized for cloud usage.
        includeFor:
          - category: Language
            tag: Java
        answers:
          - order: 1
            text: Cloud-Native Storage Solution
            risk: green
            rationale: Cloud-native solutions offer scalability and resilience.
            mitigation: Ensure regular backups and disaster recovery plans.
          - order: 2
            text: Traditional On-Premises Storage
            risk: red
            rationale: Traditional storage might not scale well in the cloud.
            mitigation: Explore cloud-based storage solutions.
          - order: 3
            text: Hybrid Storage Approach
            risk: yellow
            rationale: Hybrid solutions may have integration complexities.
            mitigation: Evaluate and optimize cloud integration points.
thresholds:
  red: 1
  yellow: 30
  unknown: 15
riskMessages:
  red: Requires deep changes in architecture or lifecycle
  yellow: Cloud friendly but needs minor changes
  green: Cloud Native
  unknown: More information needed

name: Uploadable Cloud Readiness Questionnaire Template
description: This questionnaire is an example template for assessing cloud readiness. It serves as a guide for users to create and customize their own questionnaire templates.
required: true
sections:
  - order: 1
    name: Application Technologies
    questions:
      - order: 1
        text: What is the main technology in your application?
        explanation: Identify the main framework or technology used in your application.
        includeFor:
          - category: Language
            tag: Java
        answers:
          - order: 1
            text: Quarkus
            risk: green
            rationale: Quarkus is a modern, container-friendly framework.
            mitigation: No mitigation needed.
            applyTags:
              - category: Runtime
                tag: Quarkus
            autoAnswerFor:
              - category: Runtime
                tag: Quarkus
          - order: 2
            text: Spring Boot
            risk: green
            rationale: Spring Boot is versatile and widely used.
            mitigation: Ensure container compatibility.
            applyTags:
              - category: Runtime
                tag: Spring Boot
            autoAnswerFor:
              - category: Runtime
                tag: Spring Boot
          - order: 3
            text: Legacy Monolithic Application
            risk: red
            rationale: Legacy monoliths are challenging for cloud adaptation.
            mitigation: Consider refactoring into microservices.
      - order: 2
        text: Does your application use a microservices architecture?
        explanation: Assess if the application is built using a microservices architecture.
        answers:
          - order: 1
            text: Yes
            risk: green
            rationale: Microservices are well-suited for cloud environments.
            mitigation: Continue monitoring service dependencies.
          - order: 2
            text: No
            risk: yellow
            rationale: Non-microservices architectures may face scalability issues.
            mitigation: Assess the feasibility of transitioning to microservices.
          - order: 3
            text: Unknown
            risk: unknown
            rationale: Lack of clarity on architecture can lead to unplanned issues.
            mitigation: Conduct an architectural review.

      - order: 3
        text: Is your application's data storage cloud-optimized?
        explanation: Evaluate if the data storage solution is optimized for cloud usage.
        includeFor:
          - category: Language
            tag: Java
        answers:
          - order: 1
            text: Cloud-Native Storage Solution
            risk: green
            rationale: Cloud-native solutions offer scalability and resilience.
            mitigation: Ensure regular backups and disaster recovery plans.
          - order: 2
            text: Traditional On-Premises Storage
            risk: red
            rationale: Traditional storage might not scale well in the cloud.
            mitigation: Explore cloud-based storage solutions.
          - order: 3
            text: Hybrid Storage Approach
            risk: yellow
            rationale: Hybrid solutions may have integration complexities.
            mitigation: Evaluate and optimize cloud integration points.
thresholds:
  red: 1
  yellow: 30
  unknown: 15
riskMessages:
  red: Requires deep changes in architecture or lifecycle
  yellow: Cloud friendly but needs minor changes
  green: Cloud Native
  unknown: More information needed

Copy to Clipboard

7.2.2.2. The custom questionnaire fields

Every custom questionnaire field marked as required is mandatory and must be completed. Otherwise, the YAML syntax will not validate on upload. Each subsection of the field defines a new structure or object in YAML, for example:

...
name: Testing
thresholds:
    red: 30
    yellow: 45
    unknown: 5
...

...
name: Testing
thresholds:
    red: 30
    yellow: 45
    unknown: 5
...

Copy to Clipboard

Table 7.1. The custom questionnaire fields
Questionnaire field	Description
`name` (required, string)	The name of the questionnaire. This field must be unique for the entire MTA instance.
`description` (optional, string)	A short description of the questionnaire.
`thresholds` (required)	The definition of a threshold for each risk category of the application or archetype that is considered to be affected by that risk level. The threshold values can be the following: `red` (required, unsigned integer): Numeric percentage, for example, `30` for `30%`, of red answers that the questionnaire can have until the risk level is considered red. `yellow` (required, unsigned integer): Numeric percentage, for example, `30` for `30%`, of yellow answers that the questionnaire can have until the risk level is considered yellow. `unknown` (required, unsigned integer): Numeric percentage, for example, `30` for `30%`, of unknown answers that the questionnaire can have until the risk level is considered unknown. The higher risk level always takes precedence. For example, if the `yellow` threshold is set to 30% and `red` to 5%, and the answers for the application or archetype are set to have 35% `yellow` and 6% `red`, the risk level for the application or archetype is red.
`riskMessages` (required)	Messages to be displayed in reports for each risk category. The risk_messages map is defined by the following fields: `red` (required, string): A message to be displayed in reports for the red risk level. `yellow` (required, string): A message to be displayed in reports for the yellow risk level. `green` (required, string): A message to be displayed in reports for the green risk level. `unknown` (required, string): A message to be displayed in reports for the unknown risk level.
`sections` (required)	A list of sections that the questionnaire must include. `name` (required, string): A name to be displayed for the section. `order` (required, integer): An order of the question in the section. `comment` (optional, string): A description the section. `questions` (required): A list of questions that belong to the section. `order` (required, integer): An order of the question in the section. `text` (required, string): A question to be asked. `explanation` (optional, string): An additional explanation for the question. `includeFor` (optional): A list that defines if a question must be displayed if any of the tags included in this list is present in the target application or archetype. `category` (required, string): A category of the target tag. `tag` (required, string): A target tag. `excludeFor` (optional): A list that defines if a question must be skipped if any of the tags included in the list is present in the target application or archetype. `category` (required, string): A category of the target tag. `tag` (required, string): A target tag. `answers` (required): A list of answers for the given question. `order` (required, integer): An order of the question in the section. `text` (required, string): An answer for the question. `risk` (required): An implied risk level (red, yellow, green, or unknown) of the current answer. `rationale` (optional, string): A justification for the answer that is being considered a risk. `mitigation` (optional, string): An explanation of the potential mitigation strategy for the risk implied by the answer. `applyTags` (optional): A list of tags to be automatically applied to the assessed application or archetype if this answer is selected. `category` (required, string): A category of the target tag. `tag` (required,string): A target tag. `autoAnswerFor` (optional, list): A list of tags that will lead to this answer being automatically selected when the application or archetype is assessed. `category` (required, string): A category of the target tag. `tag` (required, string): A target tag.

7.3. Managing assessment questionnaires

By using the MTA user interface, you can perform the following actions on assessment questionnaires:

Display the questionnaire. You can also diplay the answer choices and their associated risk weight.
Export the questionnaire to the desired location on your system.
Import the questionnaire from your system.
Warning
The name of the imported questionnaire must be unique. If the name, which is defined in the YAML syntax (name:<name of questionnaire>), is duplicated, the import will fail with the following error message: UNIQUE constraint failed: Questionnaire.Name.
Delete an assessment questionnaire.
Warning
When you delete the questionnaire, its answers for all applications that use it in all archetypes are also deleted.
Important
You cannot delete the Legacy Pathfinder default questionnaire.

Procedure

Depending on your scenario, perform one of the following actions:
- Display the quest the assessment questionnaire:
  1. In the Administration view, select Assessment questionnaires.
  2. Click the Options menu ( ).
  3. Select View for the questionnaire you want to display.
  4. Optional: Click the arrow to the left from the question to display the answer choices and their risk weight.
- Export the assessment questionnaire:
  1. In the Administration view, select Assessment questionnaires.
  2. Select the desired questionnaire.
  3. Click the Options menu ( ).
  4. Select Export.
  5. Select the location of the download.
  6. Click Save.
- Import the assessment questionnaire:
  1. In the Administration view, select Assessment questionnaires.
  2. Click Import questionnaire.
  3. Click Upload.
  4. Navigate to the location of your questionnaire.
  5. Click Open.
  6. Import the desired questionnaire by clicking Import.
- Delete the assessment questionnaire:
  1. In the Administration view, select Assessment questionnaires.
  2. Select the questionnaire you want to delete.
  3. Click the Options menu ( ).
  4. Select Delete.
  5. Confirm deleting by entering on the Name of the questionnaire.

7.4. Assessing an application

You can estimate the risks and costs involved in preparing applications for containerization by performing application assessment. You can assess an application and display the currently saved assessments by using the Assessment module.

The Migration Toolkit for Applications (MTA) assesses applications according to a set of questions relevant to the application, such as dependencies.

To assess the application, you can use the default Legacy Pathfinder MTA questionnaire or import your custom questionnaires.

Important

You can assess only one application at a time.

Prerequisites

You are logged in to an MTA server.

Procedure

In the MTA user interface, select the Migration view.
Click Application inventory in the left menu bar. A list of the available applications appears in the main pane.
Select the application you want to assess.
Click the Options menu ( ) at the right end of the row and select Assess from the drop-down menu.
From the list of available questionnaires, click Take for the desired questionnaire.
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 Seeding an instance.
Click Next.
Answer each Application assessment question and click Next.
Click Save to review the assessment and proceed with the steps in Reviewing an application.

Note

If you are seeing false positives in an application that is not fully resolvable, then this is not entirely unexpected.

The reason, is that MTA cannot discover the class is that is being called. Therefore, MTA cannot determine whether it is a valid match or not.

When this happens, MTA defaults to exposing more information than less.

In this situation, the following solutions are suggested:

Ensure that the maven settings can get all the dependencies.
Ensure the application can be fully compiled.

7.5. Reviewing an application

You can use the Migration Toolkit for Applications (MTA) user interface to determine the migration strategy and work priority for each application.

Important

You can review only one application at a time.

Procedure

In the Migration view, click Application inventory.
Select the application you want to review.
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. The application Review parameters appear in the main pane.
Click Proposed action and select the action.
Click Effort estimate and set the level of effort required to perform the assessment with the selected questionnaire.
In the Business criticality field, enter how critical the application is to the business.
In the Work priority field, enter the application’s priority.
Optional: Enter the assessment questionnaire comments in the Comments field.
Click Submit review.
The fields from Review are now populated on the Application details page.

7.6. Reviewing an assessment report

An MTA assessment report displays an aggregated assessment of the data obtained from multiple questionnaires for multiple applications.

Procedure

In the Migration view, click Reports. The aggregated assessment report for all applications is displayed.
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.

7.7. Tagging an application

You can attach various tags to the application that you are analyzing. You can use tags to classify applications and instantly identify application information, for example, an application type, data center location, and technologies used within the application. You can also use tagging to associate archetypes to applications for automatic assessment. For more information about archetypes, see Working with archetypes.

Tagging can be done automatically during the analysis manually at any time.

Note

Not all tags can be assigned automatically. For example, an analysis can only tag the application based on its technologies. If you want to tag the application also with the location of the data center where it is deployed, you need to tag the application manually.

7.7.1. Creating application tags

You can create custom tags for applications that MTA assesses or analyzes.

Procedure

In the Migration view, click Controls.
Click the Tags tab.
Click Create tag.
In the Name field in the opened dialogue, enter a unique name for the tag.
Click the Tag category field and select the category tag to associate with the tag.
Click Create.
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.

7.7.2. Manually tagging an application

You can tag an application manually, both before or after you run an application analysis.

Procedure

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

7.7.3. Automatic tagging

MTA automatically spawns language discovery and technology discovery tasks when adding an application to the Application Inventory. When the language discovery task is running, the technology discovery and analysis tasks wait until the language discovery task is finished. These tasks automatically add tags to the application. MTA can automatically add tags to the application based on the application analysis. Automatic tagging is especially useful when dealing with large portfolios of applications.

Automatic tagging of applications based on application analysis is enabled by default. You can disable automatic tagging during application analysis by deselecting the Enable automated tagging checkbox in the Advanced section of the Analysis configuration wizard.

Note

To tag an application automatically, make sure that the Enable automated tagging checkbox is selected before you run an application analysis.

7.7.4. Displaying application tags

You can display the tags attached to a particular application.

Note

You can display the tags that were attached automatically only after you have run an application analysis.

Procedure

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

7.8. Working with archetypes

An archetype is a group of applications with common characteristics. You can use archetypes to assess multiple applications at once.

Application archetypes are defined by criteria tags and the application taxonomy. Each archetype defines how the assessment module assesses the application according to the characteristics defined in that archetype. If the tags of an application match the criteria tags of an archetype, the application is associated with the archetype.

Creation of an archetype is defined by a series of tags, stakeholders, and stakeholder groups. The tags include the following types:

Criteria tags are tags that the archetype requires to include an application as a member.
Note
If the archetype criteria tags match an application only partially, this application cannot be a member of the archetype. For example, if the application a only has tag a, but the archetype a criteria tags include tags a AND b, the application a will not be a member of the archetype a.
Archetype tags are tags that are applied to the archetype entity.

Note

All applications associated with the archetype inherit the assessment and review from the archetype groups to which these applications belong. This is the default setting. You can override inheritance for the application by completing an individual assessment and review.

7.8.1. Creating an archetype

When you create an archetype, an application in the inventory is automatically associated to that archetype if this application has the tags that match the criteria tags of the archetype.

Procedure

Open the MTA web console.
In the left menu, click Archetypes.
Click Create new archetype.
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).
Click Create.

7.8.2. Assessing an archetype

An archetype is considered assessed when all required questionnaires have been answered.

Note

If an application is associated with several archetypes, this application is considered assessed when all associated archetypes have been assessed.

Prerequisites

You are logged in to an MTA server.

Procedure

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

7.8.3. Reviewing an archetype

An archetype is considered reviewed when it has been reviewed once even if multiple questionnaires have been marked as required.

Note

If an application is associated with several archetypes, this application is considered reviewed when all associated archetypes have been reviewed.

Prerequisites

You are logged in to an MTA server.

Procedure

Open the MTA web console.
Select the Migration view and click Archetype.
Click the Options menu ( ) and select Review from the drop-down menu..
From the list of available questionnaires, click Take to select the desired assessment questionnaire.
In the Assessment menu, answer the required questions.
Select Save and Review. You will automatically be redirected to the Review tab.
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.
Click Submit review.

7.8.4. Deleting an archetype

Deleting an archetype deletes any associated assessment and review. All associated applications move to the Unassessed and Unreviewed state.

7.9. Analyzing an application

You can use the Migration Toolkit for Applications (MTA) user interface to configure and run an application analysis. The analysis determines which specific lines in the application must be modified before the application can be migrated or modernized.

7.9.1. Configuring and running an application analysis

You can analyze more than one application at a time against more than one transformation target in the same analysis.

Procedure

In the Migration view, click Application inventory.
Select an application that you want to analyze.
Review the credentials assigned to the application.
Click Analyze.
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.
Click Next.
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
Click Next.
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.
Click Next.
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.
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.
Click Next.
In Review, verify the analysis parameters.
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.

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.

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.
When analysis is complete, to see its results, open the application drawer by clicking on the application name.

Note

After creating an application instance on the Application Inventory page, the language discovery task starts, automatically pre-selecting the target filter option. However, you can choose a different language that you prefer.

7.9.2. Reviewing analysis details

You can display the activity log of the analysis. The activity log contains such analysis details as, for example, analysis steps.

Procedure

In the Migration view, click Application inventory.
Click on the application row to open the application drawer.
Click the Reports tab.
Click View analysis details for the activity log of the analysis.
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.

7.9.3. Accessing unmatched rules

To access unmatched rules, you must run the analysis with enhanced logging enabled.

Navigate to Advanced under Application analysis.
Select Options.
Check Enhanced advanced analysis details.

When you run an analysis:

Navigate to Reports in the side drawer.
Click View analysis details, which opens the YAML/JSON format log view.
Select the issues.yaml file.
For each ruleset, there is an unmatched section that lists the rule IDs that do not find match rules.

7.9.4. Downloading an analysis report

An MTA analysis report contains a number of sections, including a listing of the technologies used by the application, the dependencies of the application, and the lines of code that must be changed to successfully migrate or modernize the application.

For more information about the contents of an MTA analysis report, see Reviewing the reports.

For your convenience, you can download analysis reports. Note that by default this option is disabled.

Procedure

In Administration view, click General.
Toggle the Allow reports to be downloaded after running an analysis. switch.
Go to the Migration view and click Application inventory.
Click on the application row to open the application drawer.
Click the Reports tab.
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.

7.10. Controlling MTA tasks by using Task Manager

Task Manager provides precise information about the Migration Toolkit for Applications (MTA) tasks queued for execution. Task Manager handles the following types of tasks:

Application analysis
Language discovery
Technology discovery

You can display task-related information either of the following ways:

To display active tasks, open the Task Manager drawer by clicking the notifications button.
To display all tasks, open the Task Manager page in the Migration view.

Warning

There are no multi-user access restrictions on resources. For example, an analyzer task created by a user can be canceled by any other user.

7.10.1. Reviewing a task log

To find details and logs of a particular Migration Toolkit for Applications (MTA) task, you can use the Task Manager page.

Procedure

In the Migration view, click Task Manager.
Click the Options menu ( ) for the selected task.
Click Task details.
Alternatively, click on the task status in the Status column.

7.10.2. Controlling the order of task execution

You can use Task Manager to preempt a Migration Toolkit for Applications (MTA) task you have scheduled for execution.

Note

You can enable Preemption on any scheduled task (not in the status of Running, Succeeded, or Failed). However, only lower-priority tasks are candidates to be preempted. When a higher-priority task is blocked by lower-priority tasks and has Preemption enabled, the low-priority tasks might be rescheduled so that the blocked higher-priority task might run. Therefore, it is only useful to enable Preemption on higher-priority tasks, for example, application analysis.

Procedure

In the Migration view, click Task Manager.
Click the Options menu ( ) for the selected task.
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.

Revised on 2025-05-22 13:32:48 UTC

Legal Notice

The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.

Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.

Linux® is the registered trademark of Linus Torvalds in the United States and other countries.

Java® is a registered trademark of Oracle and/or its affiliates.

XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.

MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.

Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.

The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.

All other trademarks are the property of their respective owners.