You can use the migration tools to migrate between two machines.
Before you begin
Typically you can use the WASPreUpgrade and the WASPostUpgrade migration
tools to upgrade from Version 5.x to Version 6 on the same machine.
However,
some scenarios require that you migrate the V5.x configuration on one machine
to V6 on a different machine. One of these scenarios is when you install new
machines for your V6 environment but need to migrate your existing V5.x configuration
from other machines.
To ensure that your
operating system is supported by WebSphere Application Server Version 6, visit
the following site for the most current list of supported hardware and software:
If you find that your operating system is not supported for migration
to V6, see
Migrating from an operating system that is no longer supported.
Why and when to perform this task
This task describes how to use the V6 migration tools to migrate
WebSphere Application Server, Version 5.x to Version 6 on a separate machine.
The
WASPreUpgrade tool saves the existing V5.x configuration into a migration-specific-backup directory.
The WASPostUpgrade tool uses this directory to add the old configuration settings
to the new V6 environment.
Steps for this task
- Obtain the V6 product CD-ROM. On this CD is the migration/bin directory.
This directory contains a special environment that you can use to run the
WASPreUpgrade tool without installing V6.
- Save the current configuration using the WASPreUpgrade script from the migration/bin directory
of the V6 product CD-ROM, which you must mount to the V5.x machine.
Save the configuration in the migration-specific-backup directory
on the V5.x machine.
Linux:
./WASPreUpgrade.sh /filepath/migration-specific-backup /opt/WebSphere/AppServer
Windows:
WASPreUpgrade C:\filepath\migration-specific-backup C:\Program Files\WebSphere\AppServer
The WASPreUpgrade tool provides status to the screen and to log
files in the migration-specific-backup directory. ASCII log
file names start with the text WASPreUpgrade and include a date and
timestamp.
- Copy the migration-specific-backup directory from
the V5.x machine to the V6 machine. Use the ftp command,
shared storage, or some other mechanism to copy the directory to the new machine.
- Optional: Run the
backupConfig tool from the 5.x install_root to create a backup of your 5.x
environment.
- Install V6 of WebSphere
Application Server. Install the same features as the earlier
release.
- Create
a profile with the Profile Creation wizard.
Note: When you
create the V6 profile, the NodeName you choose must match one of the NodeNames
in the V4.0.x environment.
- Add the V5.x configuration to the V6 configuration. Use
the WASPostUpgrade tool
in the install_root/bin directory of the V6 installation to add the
V5.x configuration to the V6 configuration.
Linux:
./WASPostUpgrade.sh /filepath/migration-specific-backup
Windows:
WASPostUpgrade C:\filepath\migration-specific-backup
The WASPostUpgrade tool records detailed information specific
to each enterprise bean it deploys, in the migration-specific-backup/WASPostUpgrade.log file.
- Modify the configuration using the WebSphere Application Server
6 administration interfaces. Make these changes:
- Change user IDs and passwords to match security requirements.
You might have to change user IDs and passwords if they are not identical
to those in use on the V5.x machine.
- Change other machine-specific information. The configuration
might refer to other software products or configurations that do not exist
on the new machine. For example, the old machine might have a database. Modify
the data source to point to the database on the old machine.
Result
You have migrated WebSphere Application Server from V5.x to a remote
V6 machine.