Chapter 4. Analyzing applications written in languages other than Java with MTA command-line interface
Starting from Migration Toolkit for Applications (MTA) version 7.1.0, you can run the application analysis on applications written in languages other than Java. You can perform the analysis either of the following ways:
- Select a supported language provider to run the analysis for.
- Overwrite the existing supported language provider with your own unsupported language provider, and then run the analysis on it.
Analyzing applications written in languages other than Java is only possible in container mode. You can use the containerless CLI only for Java applications. For more information, see Analyzing an application in containerless mode.
4.1. Analyzing an application for the selected supported language provider Copy linkLink copied to clipboard!
You can explicitly set a supported language provider according to your application’s language to run the analysis for.
Prerequisites
- You have the latest version of MTA CLI installed on your system.
Procedure
List language providers supported for the analysis:
mta-cli analyze --list-providers
$ mta-cli analyze --list-providersCopy to Clipboard Copied! Toggle word wrap Toggle overflow Run the application analysis for the selected language provider:
mta-cli analyze --input <path_to_input> --output <path_to_output> --provider <language_provider> --rules <path_to_custom_rules>
$ mta-cli analyze --input <path_to_input> --output <path_to_output> --provider <language_provider> --rules <path_to_custom_rules>Copy to Clipboard Copied! Toggle word wrap Toggle overflow ImportantNote that if you do not set the
--provideroption, the analysis might fail because it detects unsupported providers. The analysis will complete without--provideronly if all discovered providers are supported.
4.2. Analyzing an application for an unsupported language provider Copy linkLink copied to clipboard!
You can run the analysis for an unsupported language provider. To do so, you must overwrite the existing supported language provider with your own unsupported language provider.
You must create a configuration file for your unsupported language provider before overriding the supported provider.
Prerequisites
You created a configuration file for your unsupported language provider, for example:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Procedure
Override an existing supported language provider with your unsupported provider and run the analysis:
mta-cli analyze --provider-override <path_to_configuration_file> --output <path_to_output> --rules <path_to_custom_rules>
$ mta-cli analyze --provider-override <path_to_configuration_file> --output <path_to_output> --rules <path_to_custom_rules>Copy to Clipboard Copied! Toggle word wrap Toggle overflow