(Dist) createRemoteMigrJar command
The createRemoteMigrJar command makes remote migrations easier because we no longer have to install WebSphere Application Server v9.0 on any source machine targeted to be replaced.
After installing WAS v9.0 on the 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. We 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 completing the final steps of the migration process.
After creating the JAR file for our remote migration, we can then use it on any source machine that we plan to replace.
The command file is located in and must be run from the v9.0 install_root/bin/migration/bin directory.
Before creating the remote migration JAR file, update the v9.0 installation with any available fix packs or migration-related interim fixes. To verify the service level of the v9.0 installation, run the versionInfo command. The versionInfo command is also included in the remote migration JAR file. If we apply any additional fix packs or migration-related interim fixes, recreate the JAR file for our remote migration to include these fixes.
Syntax
- createRemoteMigrJar.sh -targetDir targetDirectory -includeJava
Parameters
The command has the following parameters:
- -targetDir
- Required. Directory where the remote migration JAR file is created.
- -includeJava
-
Optional. 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 specified, then the name of the JAR file reflects the operating system and architecture of the Java collected:
WAS_V90_OS.ARCH_RemoteMigrSupport.jar
Use of the remote migration JAR file is restricted to only those source machines that support the version of Java collected.
- If not specified, the name of the JAR file is
WAS_V90_RemoteMigrSupport.jar
Use this JAR file on any distributed operating system and architecture. However, because it does not include a Java runtime, set the JAVA_HOME environment variable before running the WASPreUpgrade command. The JDK found in the JAVA_HOME directory must be version 7.0 or later.
- If specified, then the name of the JAR file reflects the operating system and architecture of the Java collected:
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 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.
(Dist)
