Skip to content

Latest commit

 

History

History
63 lines (50 loc) · 2.64 KB

proc_running-the-containerless-mta-cli.adoc

File metadata and controls

63 lines (50 loc) · 2.64 KB

Analyzing an application in containerless mode

To analyze applications in environments where a container engine is not available or not needed, you can run the {ProductFullName} command-line interface (CLI) in containerless mode. This way, you can run assessments directly on your local machine by using the provided shell script, bypassing the need for Podman or Docker.

Important

In {ProductShortName} 7.2.0 and later, containerless CLI is a default mode. To enable container runtime usage for the analysis of Java applications, you must set the --run-local flag to false:

--run-local=false

The analysis for other applications runs in the container mode automatically.
Prerequisites

  • You installed the {ProductShortName} CLI. For more information, see Installing the CLI by using a .zip file.

  • You installed Java Development Kit (JDK) version 17 or later.

  • If you use OpenJDK on Red Hat Enterprise Linux (RHEL) or Fedora, you installed the Java devel package.

  • You installed Maven version 3.9.9 or later.

  • The CLI assumes that a path to the mvn binary is correctly registered in the system variable. Therefore, ensure that you added mvn to the following variable:

    • Path for Windows.

    • PATH for Linux and macOS.

  • You set the JAVA_HOME environmental variable.

  • You set the JVM_MAX_MEM system variable.

    Note
    		 If you do not set JVM_MAX_MEM, the analysis might hang because Java might require more memory than the default JVM_MAX_MEM value.

  • For Gradle analysis:

    • You installed OpenJDK version 8.

    • You set $JAVA8_HOME and it is pointing to the OpenJDK 8 home directory.

    • Your project has a Gradle wrapper.

Procedure

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

    $ mta-cli analyze --help

  2. Run the application analysis:

    $ mta-cli analyze --overwrite --input <path_to_input>  --output <path_to_output> --target <target_source>
    Note
    		 The --overwrite option overwrites the output folder if it exists.