SupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

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

  1. In Administration view, click Credentials.
  2. Click Create new.

  3. Enter the following information:

    • Name
    • Description (Optional)
  4. In the Type list, select Source Control.

  5. 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].

  6. 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

  1. In Administration view, click Credentials.
  2. Click Create new.

  3. Enter the following information:

    • Name
    • Description (Optional)
  4. In the Type list, select Maven Settings File.
  5. Upload the settings file or paste its contents.

  6. 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

  1. In Administration view, click Credentials.
  2. Click Create new.

  3. Enter the following information:

    • Name
    • Description (Optional)
  4. In the Type list, select Proxy.

  5. Enter the following information.

    • Username

    • Password

      Note

      Type-specific credential information such as keys and passphrases is either hidden or shown as [Encrypted].

  6. 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

  1. In Administration view, click Repositories and then click Git.
  2. 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

  1. In Administration view, click Repositories and then click Subversion.
  2. 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.

Note

If the rwx_supported configuration option of the Tackle CR is set to false, the Consume insecure artifact repositories switch is disabled and this procedure is not possible.

Procedure

  1. In Administration view, click Repositories and then click Maven.
  2. 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

  1. In Administration view, click Repositories and then click Maven.

  2. 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

  1. In the Administration view, click Proxy.
  2. Toggle HTTP proxy or HTTPS proxy to enable the proxy connection.

  3. Enter the following information:

    • Proxy host
    • Proxy port
  4. Optional: Toggle HTTP proxy credentials or HTTPS proxy credentials to enable authentication.
  5. 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

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

  5. 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.

  6. 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:

  1. Create Stakeholder groups
  2. Create Job functions
  3. Create Stakeholders

Tags:

  1. Create Tag categories
  2. 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

  1. In Migration view, click Controls.
  2. Click Stakeholder groups.
  3. Click Create new.

  4. Enter the following information:

    • Name
    • Description
    • Member(s)
  5. 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

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

4.6.3. Creating a new stakeholder

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

Procedure

  1. In Migration view, click Controls.
  2. Click Stakeholders.
  3. Click Create new.

  4. Enter the following information:

    • Email
    • Name
    • Job function - custom functions can be created
    • Stakeholder group
  5. 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

  1. In Migration view, click Controls.
  2. Click Business services.
  3. Click Create new.

  4. Enter the following information:

    • Name
    • Description
    • Owner
  5. 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

  1. In Migration view, click Controls.
  2. Click Tags.
  3. Click Create tag category.

  4. Enter the following information:

    • Name
    • Rank - the order in which the tags appear on the applications
    • Color
  5. 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

  1. In Migration view, click Controls.
  2. Click Tags.
  3. Click Create tag.

  4. Enter the following information:

    • Name
    • Tag category
  5. Click Create.
Red Hat logoGithubRedditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

© 2024 Red Hat, Inc.