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.
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.
Syntax
createRemoteMigrJar.sh -targetDir targetDirectory -skipJava
createRemoteMigrJar.bat -targetDir targetDirectory -skipJava
Parameters
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 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.
- If you specify the parameter, the name of the JAR file is
WAS_V855_RemoteMigrSupport.jar.
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.