[AIX Solaris HP-UX Linux Windows]

createRemoteMigrJar command

The createRemoteMigrJar command makes remote migrations easier because you no longer have to install WebSphere® Application Server V8.5.5 on source machines that are targeted to be replaced.

Install WebSphere Application Server V8.5.5 on your target machine, and then run the createRemoteMigrJar command. This utility 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 in the temporary directory. You are now ready to run the first step in the migration process by running the 8.5.5 version of the WASPreUpgrade command. The WASPreUpgrade command captures the configuration data of a source profile into a migration backup directory. The migration backup directory must be archived and sent 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.

Location

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

Avoid trouble: Before you create the remote migration JAR file, update the V8.5.5 installation with any available fix packs or migration-related interim fixes. To verify the service level of the V8.5.5 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.

Syntax

[Linux][AIX][HP-UX][Solaris]
createRemoteMigrJar.sh -targetDir targetDirectory -skipJava
[Windows]
createRemoteMigrJar.bat -targetDir targetDirectory -skipJava

Parameters

The command has the following parameters:

-targetDir
This required parameter specifies the directory where the remote migration JAR file is created.
-skipJava

This optional parameter specifies whether you want the command to skip collecting 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, the name of the JAR file is WAS_V855_RemoteMigrSupport.jar.

    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 running the WASPreUpgrade command. The JDK found in the JAVA_HOME directory must be version 6.0 or later.

  • If you do not specify this parameter, the name of the jar file is WAS_V855_OS.ARCH_RemoteMigrSupport.jar. The name of the JAR file reflects the operating system and architecture of the Java™ collected and restricts its use to only those source machines that support the version of Java collected.

Packaged resources

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

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