The migration team has provided the following instructions
for migration across machines:
Using WebSphere Application Server V5.0 migration tools to migrate
across different host machines
The WebSphere Application Server V5.0 migration tools are typically used
for upgrading the WebSphere Application Server version from either V3.5 or
V4.0 to V5.0 on the same host machine. The commands that are used are
WASPreUpgrade and WASPostUpgrade.
You might want to migrate your V3.5 or V4.0 configuration on one
machine to V5.0 on a different host machine. One scenario where
this occurs is when you install new machines for your V5.0 environment and
want to migrate your existing V3.5 or V4.0 configuration to your V5.0
configuration.
This technote describes how to use the V5.0 migration tools to perform
this task for the following versions:
- V3.5 SE
- V3.5 AE
- V4.0 AE
- V4.0 AEs (the steps vary slightly)
The WASPreUpgrade command is used to save the existing V3.5 or V4.0
configuration into a migration-specific-backup directory. This
directory is then used by the WASPostUpgrade command to add the old
configuration settings to the new V5.0 environment.
Following are the steps for performing this type of migration.
- Obtain the V5.0 Installation CD. On this CD is a directory called
migration . This directory contains a special environment that
is used to execute the WASPreUpgrade command without installing WebSphere
Application Server 5.0. The WASPreUpgrade command is located in the
migration/bin directory on the V5.0 Installation CD.
- Use the WASPreUpgrade command in the
migration/bin
directory to create the migration-specific-backup directory
on the host machine where the previous version is installed.
For example: WASPreUpgrade backupDirectoryName
currentWebSphereDirectory
For all versions except V4.0 AEs, ensure that the Administrative
Server is running for this step to complete successfully.
- The
migration-specific-backup directory must be
copied using FTP, shared storage, or some other mechanism to the new
machine where V5.0 will be installed.
The remainder of the steps are performed on the V5.0 host machine.
- This step is not required for V4.0AEs. The WASPreUpgrade
command calls XMLConfig to export the V3.5 or V4.0 repository to a file
called websphere_backup.xml, located in the
migration-specific-backup directory. Make a copy of this
file in the migration-specific-backup directory. The
original websphere_backup.xml file is modified in the next step.
- This step is not required for V4.0AEs. Modify the
websphere_backup.xml file as follows.
- Node name: The node name of the original machine can be
propagated in many XML stanzas throughout the file. If the node name that
is to be used for the V5.0 configuration is different than the node name
used on the original V3.5 or V4.0 configuration, all entries where the
node name is referenced must be updated to the node name used for
the V5.0 configuration. Failure to do this results in an incomplete
migration of data.
- Path names: The configuration file contains references to path
names in many XML stanzas throughout the file. If any reference is made to
files outside of the V3.5 or V4.0 directory, the paths must be updated to
use the equivalent directory on the new machine, or the directory must be
recreated on the new machine. This might require copying the directory or
installing appropriate software.
- Operating System path differences: If the operating system on
the machine running V3.5 or V4.0 is different than the machine running
V5.0 (for example, if you are migrating from Windows® to Unix®), any path
in the configuration file must be updated to use the appropriate path
style.
For example: change c:\mystuff\somepath to
/usr/mystuff/somepath
- Install V5.0 on the new host machine without using the migration
selection.
- Use the WASPostUpgrade command from the V5.0
/bin
directory to add the V3.5 or V4.0 configuration to the V5.0 configuration.
For example: WASPostUpgrade backupDirectoryName
|