WASMigrationAppInstaller command

The WASMigrationAppInstaller command for WebSphere® Application Server Version 9.0 migrates applications from a previously installed version of WebSphere Application Server into the new version. Only applications that are not already installed are migrated.

Location

The command file is located in and must be run from the Version 9.0 profile_root/bin directory.

Authority

To run this command script, your user profile must have *ALLOBJ authority.

Syntax

Parameters

The command has the following parameters:

backupDirectory
This is a required parameter and must be the first parameter that you specify. The value backupDirectory specifies the name of the directory from which the command loads configuration data and runs scripts that install the applications.
Avoid trouble: The WAS_INSTALL and USER_INSTALL root directories are invalid directories for the location of the WebSphere Application Server backup directory.

This is also the directory from which the WASPostUpgrade command reads the configuration.

-properties
This is an optional parameter. The value properties_file_name specifies the path to a properties file containing parameter properties that define how migration tools such as WASMigrationAppInstaller operate.

You can define parameter properties in the migration properties file rather than specifying most optional parameters on the command line. If parameters are both defined in the properties file and specified on the command line, the parameters specified on the command line take precedence.

Note: Certain parameters cannot be specified in the properties file, such as the -properties parameter itself and -javaoption. For a list of parameters that cannot be defined as a property, see the template migration.properties file in the app_server_root/bin directory.
-traceString
This is an optional parameter. The value trace_spec specifies the trace information that you want to collect.

To gather all trace information, specify "*=all=enabled" (with quotation marks).

If you do not specify the -traceString or -traceFile parameter, the command creates a trace file by default and places it in the backupDirectory/logs directory.

-traceFile
This is an optional parameter. The value file_name specifies the name of the output file for trace information.

If you do not specify the -traceString or -traceFile parameter, the command creates a trace file by default and places it in the backupDirectory/logs directory.

-javaoption
This is an optional parameter. Use this parameter to specify memory sizes for the Java™ heap used by the WASPreUpgrade command.

The value "-Xms...m" is the parameter specified to indicate the starting heap size. Replace the "..." with the size in megabytes that you intended to use. For example, if the starting heap size is to be 128 MB, specify the parameter as: -javaoption -Xms128m

The value "-Xmx...m" is the parameter specified to indicate the maximum heap size. Replace the "..." with the size in megabytes that you intend to use. For example, if the maximum heap size is to be 1024 MB, specify the parameter as: -javaoption -Xmx1024m

-appName
This is an optional parameter. Use this parameter to specify only the applications that are intended to be processed by the command. The applications are specified in a comma-separated-list, and the application names do not include their .ear extension.

The backupDirectory may contain many applications. If the -appName parameter is not specified, all applications will be deployed.

Logging

The WASMigrationAppInstaller tool displays status to the screen while it runs. The tool also saves a more extensive set of logging information in the WASMigrationAppInstaller.time_stamp.log file written to the backupDirectory directory, where backupDirectory is the value specified for the backupDirectory parameter. You can view the WASMigrationAppInstaller.time_stamp.log file with a text editor.

Migrated resources

The WASMigrationAppInstaller tool migrates only applications that are not already installed in the target release. If any applications do not successfully install, you can rerun the tool as many times as needed without repeatedly reinstalling the same applications.

The tool also automatically installs business-level applications (BLAs).