WAS v8.0 > Migration and coexistence > Distributed operating systems > Scenario 4: Flexible Management: Migrating a job manager profile and its registered set of servers > 4. Run the WASPreUpgrade command from the new WAS install root bin directory

WASPreUpgrade command

The WASPreUpgrade command for WAS v8.0 saves the configuration of a previously installed version of WAS into a migration-specific backup directory.

The command file is located in and must be run from...

v8_WAS_HOME/bin

Syntax...

WASPreUpgrade.sh backupDirectory
                 currentWebSphereDirectory
                 [-traceString trace_spec [-traceFile file_name ]]
                 [-machineChange true | false]
                 [-oldProfile profile_name]
                 [-workspaceRoot profile1=user_workspace_folder_name_1;profile2=user_workspace_folder_name_2]

The command has the following parameters:

backupDirectory

Name of the directory where the command script stores the saved configuration. Must be the first parameter specified.

WAS_INSTALL and USER_INSTALL root directories are invalid directories for the location of the WAS backup directory.

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

If the directory does not exist, the WASPreUpgrade command script creates it.

currentWebSphereDirectory

Name of the installation root directory for the current WAS v6.x installation. Must be the second parameter specified.

-traceString

Trace information to collect.

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

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

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. Optional.

-machineChange

Used for a migration involving cross operating-system and machine boundaries. If specified as true, this parameter provides support for changing physical hardware when migrating by backing up items that are stored outside the WAS installation or profile folder hierarchy. If specified as false, only files stored under the WAS installation folder or profile folders are copied to the backup directory during migration.

The default is false.

When this value is false, migration assumes that the new and old WAS installations are on the same physical machine with shared access to the file system. Therefore, any files located outside the WebSphere directories are communal and can be shared. Migration does not copy files outside the WAS tree into the backup directory when -machineChange is false. False is the only option when you use the Migration wizard. If you select -machineChange=false, run the WASPostUpgrade command on the same physical hardware.

If you intend to run the WASPostUpgrade command on a different machine or file system, you should run the WASPreUpgrade command with -machineChange=true. If you select -machineChange=true, migration creates an additional subdirectory (/migrated/) in the migration backup directory that contains any files referenced by the WAS configuration that reside outside the product or profile directories. When you run the WASPostUpgrade command, these files are returned to their original paths on the new machine.

Performance considerations:

If you migrate with Service Integration Bus (SIB) busses configured with file-system file-store repositories, you might require additional space in your migration heap and migration backup directory. Each bus has three file-store values—a log, a tempspace, and a repository. These three files vary in size, but they can be as much as 100-500 MB each. When migration is running, it backs up any file stores that are in the WAS tree during the pre-upgrade process. There needs to be sufficient space on the file system to permit this. If file stores exist at the destination location already during the post-upgrade process, migration backs up the file stores in memory to support rollback.

If you run the WASPreUpgrade command with -machineChange=true, resulting in a backup directory that contains shared file-store objects, you might find that the post-upgrade process suffers from out-of-memory exceptions because the default maximum heap is too small to contain the file-store backups in support of rollback.

To resolve this issue, perform one of the following three tasks:

• If the file stores at the system location are valid, delete the copies from the backup directory before running the WASPostUpgrade command.

  By deleting the entire /migrated/ subdirectory from the migration backup directory before running the WASPostUpgrade command, you essentially convert your pre-upgrade backup from -machineChange=true to -machineChange=false.

• If the copies of the file stores in the backup directory are valid, delete the versions at the destination location.

  This changes the rollback support so that the destination files do not exist and will not occupy space in memory during the migration.

• If you require rollback support and you need both the files in the backup directory as well as the files on the file system, increase your maximum heap size for the post-upgrade process to some value great enough to support all of the SIB files that conflict.

-oldProfile

Used for migrating a specific instance or profile from a previous version of WAS. Optional.

-workspaceRoot

Location of the administrative console customized "My tasks" settings for one or more profiles. Optional.

Log

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

Migrated resources

WASPreUpgrade saves all of your resources, but it does not migrate entities in your classes directory.

Migration saves the following files in the backupDirectory directory.

• classes
• config
• properties

Migrate product configurations
Migrate product configurations with migration tools
WASPostUpgrade command

+

Search Tips   |   Advanced Search