app2container remote extract command - AWS App2Container

app2container remote extract command

Run this command from a worker machine to generate an application archive for the specified application on the target application server. The target application server is specified by its IP address or Fully Qualified Domain Name (FQDN). Before you call this command, you must call the remote analyze command.

Note

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.

Syntax

app2container remote extract --application-id id --target IP/FQDN [--output s3] [--help]

Parameters and options

--application-id id

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

  • Linux: <workspace>/remote/<target server IP or FQDN>/inventory.json

  • Windows: <workspace>\remote\<target server IP or FQDN>\.app2container-config\inventory.json

--target IP/FQDN

Specifies the IP address or FQDN of the application server targeted for the inventory (required).

--profile admin-profile

Use this option to specify a named profile to run this command. For more information about named profiles in AWS, see Named profiles in the AWS Command Line Interface User Guide

Options

--output s3

If specified, this option writes the archive file to an Amazon S3 bucket that you specified when you ran the init command.

--force

Bypasses the disk space prerequisite check.

--help

Displays the command help.

Output

This command creates an archive file. When you use the --output s3 option, the archive is written to the Amazon S3 bucket that you specified when you ran the init command. Otherwise, the archive is written to the output location that you specified when you ran the init command.

Examples

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

Linux

The following example shows the remote extract command with the --target and --application-id parameters and no additional options.

$ sudo app2container extract --target 192.0.2.0 --application-id java-tomcat-9e8e4799 Extraction successful for application java-tomcat-9e8e4799 Next Steps: 1. Please initiate containerization using "app2container containerize --input-archive <workspace>/remote/<target server IP or FQDN>/java-tomcat-9e8e4799/java-tomcat-9e8e4799-extraction.tar"
Windows

The following example shows the remote extract command with the --target and --application-id parameters and no additional options.

PS> app2container extract --target 192.0.2.0 --application-id iis-smarts-51d2dbf8 Extraction successful for application iis-smarts-51d2dbf8 Next Steps: 1. Please initiate containerization using "app2container containerize --input-archive <workspace>\remote\<target server IP or FQDN>/iis-smarts-51d2dbf8/iis-smarts-51d2dbf8.zip"