createRemoteMigrJar command

The createRemoteMigrJar command makes remote migrations easier because you no longer have to install WebSphere® Application Server Version 9.0 on any source machine that is targeted to be replaced.

After you install WebSphere Application Server Version 9.0 on your target machine, run the createRemoteMigrJar command. The command packages the WASPreUpgrade command along with its supporting files into a remote migration JAR file. Send this JAR file to a source machine and extract its contents into a temporary directory. Open a command prompt and switch to the bin directory located of the temporary directory. You are now ready to run the first step in the migration process by running the 9.0 version of the WASPreUpgrade command. The WASPreUpgrade command captures the configuration data of a source profile into a migration backup directory. Archive the migration backup directory and send it to the target machine where you complete the final steps of the migration process.

After you create the JAR file for your remote migration, you can then use it on any source machine that you plan to replace.


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

Avoid trouble: Before you create the remote migration JAR file, update the Version 9.0 installation with any available fix packs or migration-related interim fixes. To verify the service level of the Version 9.0 installation, run the versionInfo command. The versionInfo command is also included in the remote migration JAR file. If you apply any additional fix packs or migration-related interim fixes, recreate the JAR file for your remote migration to include these fixes.


[Linux][AIX][Solaris][HP-UX] -targetDir targetDirectory -includeJava
createRemoteMigrJar.bat -targetDir targetDirectory -includeJava


The command has the following parameters:
This required parameter specifies the directory where the remote migration JAR file is created.

This optional parameter specifies whether you want the command to collect the JDK from the product installation as part of the resulting remote JAR file.

This parameter alters the name of the resulting JAR file.

  • If you specify the parameter, then the name of the JAR file reflects the operating system and architecture of the Java™ collected:

    Use of the remote migration JAR file is restricted to only those source machines that support the version of Java collected.

  • If you do not specify the parameter, the name of the JAR file is
    You can use this JAR file on any distributed operating system and architecture. However, because it does not include a Java runtime, you must set the JAVA_HOME environment variable before you run the WASPreUpgrade command. The JDK found in the JAVA_HOME directory must be version 7.0 or later.

This parameter is optional when you migrate to WebSphere Application Server Version or later. The -allPlugins parameter allows any plug-ins to the WebSphere Application Server Version 9.0 migration framework to be included automatically in the JAR file. When a stack product, such as WebSphere Portal, migrates its product and specifies this parameter, the modules for the stack product are included in the plugins directory. A stack product needs its own modules collected into the remote JAR file for the migration to succeed.

Important: In previous versions of WebSphere Application Server, the -allPlugins parameter was passed automatically and any plug-ins to the WebSphere Application Server migration framework were included automatically in the JAR file. Beginning with Version, the -allPlugins is not automatic. You must specify the parameter to use it.

Packaged resources

The createRemoteMigrJar command creates a WAS*RemoteMigrSupport.jar file in the specified target directory. To build the JAR file, the createRemoteMigrJar collects files from the target installation, including files that are required to run the WASPreUpgrade and versionInfo commands, certain libraries, and optionally Java.

The createRemoteMigrJar command does not create any log files. After the remote migration JAR file is built, the command displays instructions on how to use the JAR file to run the WASPreUpgrade command on the source machine.