app2container analyze command - AWS App2Container

app2container analyze command

Analyzes the specified application and generates a report.


If the command fails, an error message is displayed in the console, followed by additional messaging to help you troubleshoot.

When you ran the init command, if you chose to automatically upload logs to App2Container support if an error occurs, App2Container notifies you of the success of the automatic upload of your application support bundle.

Otherwise, App2Container messaging directs you to upload application artifacts by running the upload-support-bundle command for additional support.


app2container analyze --application-id id [--help]

Parameters and options


--application-id id

The application ID (required). After you run the inventory command, you can find the application ID in the inventory.json file in one of the following locations:

  • Linux: /root/inventory.json

  • Windows: C:\Users\Administrator\AppData\Local\.app2container-config\inventory.json



Displays the command help.


The analyze command creates files and directories for each application. Output varies slightly, depending on your application language and the application server operating system.

The application directory is created in the output location that you specified when you ran the init command. Each application has its own directory named for the application ID. The directory contains analysis output and editable application configuration files. The files are stored in subdirectories that match the application structure on the server.

An analysis.json file is created for the application that is specified in the --application-id parameter. The file contains information about the application found during analysis, and configurable fields for container settings. See Java application analysis file, or .NET application analysis file for more information about configurable fields, and for an example of what the file looks like.

For .NET applications, App2Container detects connection strings and produces the report.txt file. The report location is specified in the analysis.json file, in the reportPath attribute of the analysisInfo section. You can use this report to identify the changes that you need to make in application configuration files to connect your application container to new database endpoints, if needed. The report also contains the locations of other configuration files that might need changes.


Choose the operating system tab for the application server or worker machine where you run the command.


The following example shows the analyze command with the --application-id parameter and no additional options.

$ sudo app2container analyze --application-id java-tomcat-9e8e4799 √ Created artifacts folder /root/app2container/java-tomcat-9e8e4799 √ Generated analysis data in /root/app2container/java-tomcat-9e8e4799/analysis.json Analysis successful for application java-tomcat-9e8e4799 Please examine the application analysis file at /root/app2container/java-tomcat-9e8e4799/analysis.json, make appropriate edits and initiate containerization using "app2container containerize --application-id java-tomcat-9e8e4799

The following example shows the analyze command with the --application-id parameter and no additional options.

PS> app2container analyze --application-id iis-smarts-51d2dbf8 √ Created artifacts folder C:\Users\Administrator\AppData\Local\app2container\iis-smarts-51d2dbf8 √ Generated analysis data in C:\Users\Administrator\AppData\Local\app2container\iis-smarts-51d2dbf8\analysis.json Analysis successful for application iis-smarts-51d2dbf8 Please examine the application analysis file at C:\Users\Administrator\AppData\Local\app2container\iis-smarts-51d2dbf8\analysis.json, make appropriate edits and initiate containerization using "app2container containerize --application-id iis-smarts-51d2dbf8