Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 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

    An application must have all of the archetype’s criteria tags to be a member. 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.

8.1. Creating an archetype
Copy link

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

Procedure

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

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

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

8.2. Assessing an archetype
Copy link

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

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

8.3. Reviewing an archetype
Copy link

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

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

  7. Enter the following information:

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

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat