Procedure

1. In the Red Hat OpenShift web console, click Operators and then click OperatorHub.
2. Type MTA in the Filter by keyword field to search for the MTA Operator.
3. Click the Migration Toolkit for Applications Operator and then click Install.
4. On the Install Operator page, click Install.

5. Optional: Review and edit the custom resource (CR) settings.

   A window for creating CR settings pops up automatically after the installation of MTA Operator is complete. The default settings are acceptable. However, make sure to check the system requirements for storage, memory, and cores.

   Alternatively, to work directly with the YAML file, click the YAML view and review the CR settings that are listed in the spec section of the YAML file. For more details about commonly used CR settings, see Custom resource settings.

   The spec section of the YAML file can have the following configuration:

   kind: Tackle
   apiVersion: tackle.konveyor.io/v1alpha1
   metadata:
     name: mta
     namespace: openshift-mta
   spec:
     hub_bucket_volume_size: "2.5Gi"
     maven_data_volume_size: "2.5Gi"
     rwx_supported: "false"

6. Verify that the MTA pods are running by clicking Workloads and then Pods in the Administration view.

Procedure

1. Click MTA Operator.
2. Under Provided APIs, search for Tackle and click Create Instance.
3. Access the user interface from your browser by using the route exposed by the mta-ui application within OpenShift.

4. Log in to the user interface instance by using the default credentials:

   • User name: admin
   • Password: Passw0rd!
5. When prompted, create a new password.

Procedure

1. Navigate to the MTA download page and download one of the following operating system-specific CLI files or the src file:

   • mta-7.3.1-cli-linux-amd64.zip
   • mta-7.3.1-cli-linux-arm64.zip
   • mta-7.3.1-cli-darwin-amd64.zip
   • mta-7.3.1-cli-darwin-arm64.zip
   • mta-7.3.1-cli-windows-amd64.zip
   • mta-7.3.1-cli-windows-arm64.zip
   • mta-7.3.1-cli-src.zip
2. Extract the .zip file. .zip extracts the mta-cli binary, along with other required directories and files.

3. Move the mta-cli binary to your $PATH variable.

   Note

   You can place the mta-cli binary in any folder that is included in the $PATH variable. Alternatively, you can add a folder that contains mta-cli to $PATH. This way, you do not need to specify a full path when using the CLI.

1. Download the required images by using an external computer.
2. Copying the downloaded images to the system you want to install MTA CLI on.

Procedure

1. On a connected device, perform the following steps:

   1. Authenticate to registry.redhat.io:

      $ podman login registry.redhat.io

   2. Run the mta-cli binary file. The binary file pulls the required provider images. For example:

      $ mta-cli analyze

      Important

      This command only pulls the required images. For example, if you run a command that requires Java images, a .NET image will not be pulled.

   3. Display the image list:

      $ podman images
      REPOSITORY                                                        TAG         IMAGE ID      CREATED       SIZE
      registry.redhat.io/mta/mta-generic-external-provider-rhel9        7.3.1       8b8d7fa14570  13 days ago   692 MB
      registry.redhat.io/mta/mta-cli-rhel9                              7.3.1       45422a12d936  13 days ago   1.6 GB
      registry.redhat.io/mta/mta-java-external-provider-rhel9           7.3.1       4d6d0912a38b  13 days ago   715 MB
      registry.redhat.io/mta/mta-dotnet-external-provider-rhel9         7.3.1       66ec9fc51408  13 days ago   1.27 GB

   4. Save the images:

      $ podman save <image_ID> -o <image_name>.image

   5. Copy the images onto a USB drive or directly to the file system of the disconnected device.

2. On the disconnected device, enter:

   $ podman load --input <image_name>.image

Procedure

1. Open a PowerShell with Administrator privileges.

2. Ensure Hyper-V is installed and enabled:

   PS C:\Users\<user_name>> Enable-WindowsOptionalFeature -Online ` -FeatureName Microsoft-Hyper-V-All

   PS C:\Users\<user_name>> Enable-WindowsOptionalFeature -Online ` -FeatureName Containers

   Note

   You might need to reboot Windows for the change to take effect.

3. Install Docker Desktop on Windows.

   1. Run the installer by double-clicking the Docker_Desktop_Installer.exe file.

      By default, Docker Desktop is installed to the C:\Program Files\Docker\Docker path.

   2. Ensure that Docker will run Windows containers as the backend instead of Linux containers:

      1. In the Windows task bar, right-click on the Docker icon.
      2. Click Switch to Windows containers.

4. In PowerShell, create a folder for MTA:

   PS C:\Users\<user_name>> mkdir C:\Users\<user_name>\MTA

5. Extract the mta-7.3.1-cli-windows.zip file to the MTA folder:

   PS C:\Users\<user_name>> cd C:\Users\<user_name>\Downloads

   PS C:\Users\<user_name>> Expand-Archive ` -Path "{ProductShortNameLower}-{ProductVersion}-cli-windows.zip" ` -DestinationPath "C:\Users\<user_name>\MTA"

6. Ensure that Docker is running Windows containers the OS/Arch is set to windows/amd64:

   PS C:\Users\<user_name>> docker version

   Client:
    Version:           27.0.3
    API version:       1.46
    Go version:        go1.21.11
    Git commit:        7d4bcd8
    Built:             Sat Jun 29 00:03:32 2024
    OS/Arch:           windows/amd64
    Context:           desktop-windows
   Server: Docker Desktop 4.32.0 (157355)
    Engine:
     Version:          27.0.3
     API version:      1.46 (minimum version 1.24)
     Go version:       go1.21.11
     Git commit:       662f78c
     Built:            Sat Jun 29 00:02:13 2024
     OS/Arch:          windows/amd64
     Experimental:     false

7. Set the CONTAINER_TOOL environment variable to use Docker:

   PS C:\Users\<user_name>> $env:CONTAINER_TOOL="C:\Windows\system32\docker.exe"

8. Set the DOTNET_PROVIDER_IMG environment variable to use the upstream dotnet-external-provider:

   PS C:\Users\<user_name>> $env:DOTNET_PROVIDER_IMG="quay.io/konveyor/dotnet-external-provider:v0.5.0"

9. Set the RUNNER_IMG environment variable to use the upstream image:

   PS C:\Users\<user_name>> $env:RUNNER_IMG="quay.io/konveyor/kantra:v0.5.0"