Chapter 2. Installing and Running the CLI

Procedure

1. Navigate to the MTA Download page and download the OS-specific CLI file or the src file:

   • mta-7.2.3-cli-linux-amd64.zip
   • mta-7.2.3-cli-linux-arm64.zip
   • mta-7.2.3-cli-darwin-amd64.zip
   • mta-7.2.3-cli-darwin-arm64.zip
   • mta-7.2.3-cli-windows-amd64.zip
   • mta-7.2.3-cli-windows-arm64.zip
   • mta-7.2.3-cli-src.zip

2. Extract the .zip file to the .kantra directory inside your $HOME directory. The .zip file extracts the mta-cli binary, along with other required directories and files.

   When you encounter <MTA_HOME> in this guide, replace it with the actual path to your MTA installation.

Procedure

1. Use Podman to authenticate to registry.redhat.io by running the following command:

   $ podman login registry.redhat.io

   Copy to Clipboard Toggle word wrap

   Enter the user name and password:

   Username: <username>
   Password: <***********>

   Copy to Clipboard Toggle word wrap

2. Copy the binary PATH to enable system-wide use by running the following command:

   $ podman cp $(podman create registry.redhat.com/mta-toolkit/mta-mta-cli-rhel9:{ProductVersion}):/usr/local/bin/mta-cli ./

   Copy to Clipboard Toggle word wrap
   Warning

   Although installation using Podman is possible, downloading and installing the .zip file is the preferred installation.

Procedure

1. Open a PowerShell with Administrator privileges.

2. Ensure Hyper-V is installed and enabled:

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

   Copy to Clipboard Toggle word wrap

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

   Copy to Clipboard Toggle word wrap
   Note

   You may need to reboot Windows.

3. Install Docker Desktop on Windows.

   1. Double-click Docker_Desktop_Installer.exe to run the installer. By default, Docker Desktop is installed at C:\Program Files\Docker\Docker.
   2. Deselect the Use WSL 2 instead of Hyper-V option on the Configuration page to ensure that Docker will run Windows containers as the backend instead of Linux containers.

4. In PowerShell, create a folder for MTA:

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

   Copy to Clipboard Toggle word wrap

   Replace <your_user_name> with the username for your home directory.

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

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

   Copy to Clipboard Toggle word wrap

   Replace <your_user_name> with the username for your home directory.

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

   Copy to Clipboard Toggle word wrap

   Replace <your_user_name> with the username for your home directory.

6. Ensure Docker is running Windows containers:

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

   Copy to Clipboard Toggle word wrap

   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 

   1

   
    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 

   2

   
     Experimental:     false

   Copy to Clipboard Toggle word wrap

   1 2

   Ensure the OS/Arch setting is windows/amd64.

7. Set the PODMAN_BIN environment variable to use Docker:

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

   Copy to Clipboard Toggle word wrap

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

   PS C:\Users\<your_user_name>> $env:DOTNET_PROVIDER_IMG="registry.redhat.io/mta/mta-dotnet-external-provider-rhel9:7.1.0"

   Copy to Clipboard Toggle word wrap

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

   # double-check reference
   PS C:\Users\<your_user_name>> $env:RUNNER_IMG="registry.redhat.io/mta/mta-cli-rhel9:7.1.0"

   Copy to Clipboard Toggle word wrap

Procedure

1. Use Podman to authenticate to registry.redhat.io:

   $ podman login registry.redhat.io

   Copy to Clipboard Toggle word wrap

2. Enter your username and then your password for registry.redhat.io:

   Username: <registry_service_account_username>
   Password: <registry_service_account_password>

   Copy to Clipboard Toggle word wrap

   You should see the following output:

   Login Succeeded!

   Copy to Clipboard Toggle word wrap

3. Use Podman to pull the image from the registry:

   $ podman pull registry.redhat.io/mta/mta-cli-rhel9:7.1.0

   Copy to Clipboard Toggle word wrap

4. Use Podman to pull the provider image that you need from the registry:

   1. For Java, run:

      $ podman pull registry.redhat.io/mta/mta-java-external-provider-rhel9:7.1.0

      Copy to Clipboard Toggle word wrap

   2. For .NET, run:

      $ podman pull registry.redhat.io/mta/mta-dotnet-external-provider-rhel9:7.1.0

      Copy to Clipboard Toggle word wrap

5. Save the images:

   $ podman save <image> -o <my_image.image>

   Copy to Clipboard Toggle word wrap
6. Copy the .image file and the binary onto a USB or directly to the file system of the disconnected device.

7. On the disconnected device, run

   $ podman load --input <my_image.image>

   Copy to Clipboard Toggle word wrap

Procedure

1. Open a terminal and navigate to the <MTA_HOME>/ directory.

2. Run the mta-cli script, or mta-cli.exe for Windows, and specify the appropriate arguments:

   $ ./mta-cli analyze --input <path_to_input> \
       --output <path_to_output> --source <source_name> --target <target_source> \

   Copy to Clipboard Toggle word wrap
   • --input: The application to be evaluated.
   • --output: The output directory for the generated reports.
   • --source: The source technology for the application migration. For example, weblogic.
   • --target: The target technology for the application migration. For example, eap8.
3. Access the report.

Procedure

1. Open a terminal and navigate to the <MTA_HOME>/ directory.

2. Run the mta-cli script, or mta-cli.exe for Windows, and specify the appropriate arguments, entering one input per analyze command, but entering the same output directory for all inputs. For example, to analyze applications A, B, and C:

   1. Enter the following command for input A:

      $ ./mta-cli analyze --bulk --input=<path_to_input_A> --output=<path_to_output_ABC> --source <source_A> --target <target_A>

      Copy to Clipboard Toggle word wrap
      • --input: The application to be evaluated.
      • --output: The output directory for the generated reports.
      • --source: The source technology for the application migration. For example, weblogic.
      • --target: The target technology for the application migration. For example, eap8.

   2. Enter the following command for input B:

      $ ./mta-cli analyze --bulk --input=<path_to_input_B> --output=<path_to_output_ABC>  --source <source_B> --target <target_B>

      Copy to Clipboard Toggle word wrap

   3. Enter the following command for input C:

      $ ./mta-cli analyze --bulk --input=<path_to_input_C> --output=<path_to_output_ABC>  --source <source_C> --target <target_C>

      Copy to Clipboard Toggle word wrap

      MTA generates a single report, listing all issues that need to be resolved before the applications can be migrated.

3. Access the report.

Usage example

1. Get an example application to run analysis on.

2. List available target technologies.

   mta-cli analyze --list-targets

   Copy to Clipboard Toggle word wrap

3. Run an analysis with a specified target technology, for example cloud-readiness.

   mta-cli analyze --input=<path-to/example-applications/example-1> --output=<path-to-output-dir> --target=cloud-readiness

   Copy to Clipboard Toggle word wrap

4. Several analysis reports are created in your specified output path:

   $ ls ./output/ -1
   analysis.log
   dependencies.yaml
   dependency.log
   output.yaml
   static-report

   Copy to Clipboard Toggle word wrap
   • output.yaml is the file that contains the issues report.
   • static-report contains the static HTML report.
   • dependencies.yaml contains the dependencies report.

1. To extract the dependency zip file to ~/.kantra, run:

   unzip $HOME/mta-cli.<os>.<arch>.zip -d $HOME/.kantra

   Copy to Clipboard Toggle word wrap

2. Add as a system-wide binary or add to the global $PATH variable:

   1. For example, to add the mta-cli binary to /usr/bin as a system-wide binary, using sudo, run:

      sudo mv ~/.kantra/mta-cli /usr/bin/

      Copy to Clipboard Toggle word wrap

   2. For example, to add to the global $PATH variable, run:

      export PATH=$HOME/.kantra:$PATH

      Copy to Clipboard Toggle word wrap
   Note

   The CLI can run with the requirements moved to the directory from which you run an analysis. During the analysis, the CLI checks for the requirements in this directory first, and if it does not find the requirements, it searches for them in the $HOME/.kantra directory.

3. Optional: Display all mta-cli analyze command options:

   mta-cli analyze --help

   Copy to Clipboard Toggle word wrap

4. Run the application analysis:

   $ mta-cli analyze --overwrite --input <path_to_input>  --output <path_to_output> --target <target_source>

   Copy to Clipboard Toggle word wrap

   The command arguments represent the following:

   • --overwrite: Overwrites the output folder if it exists.
   • --input: The application to be analyzed.
   • --output: The output directory for the generated reports.
   • --target: The target technology for the application migration, for example, eap8.

Procedure

1. List language providers supported for the analysis:

   $ mta-cli analyze --list-providers

   Copy to Clipboard Toggle word wrap

2. Run the application analysis for the selected language provider:

   $ mta-cli analyze --input <_path_to_the_source_repository_> --output <_path_to_the_output_directory_> --provider <_language_provider_> --rules <_path_to_custom_rules_>

   Copy to Clipboard Toggle word wrap

   Note that if you do not set the --provider option, the analysis might fail because it detects unsupported providers. The analysis will complete without --provider only if all discovered providers are supported.