This topic introduces
the migration tools that WebSphere Application Server provides. All of the
migration tools are in the install_root/bin directory after installation.
The WASPreUpgrade.sh or WASPreUpgrade.bat scripts also ship
in the /migration/bin directory on the product CD-ROM so that you
can store the configuration of an existing release before installing the V6
product. It is important to use the migration tools for the version of Application
Server that you are installing. The tools change over time. The tools on the
product CD-ROM provide the necessary function for migrating from a previous
release of Application Server to the one on the product CD-ROM. The tools
on the CD-ROM match the product on the CD-ROM. If you use migration tools
from an earlier release of Application Server, you are likely to encounter
a problem with the migration.
- clientUpgrade.sh (and clientUpgrade.bat)
- Upgrades the client application to a new release level.
- convertScriptCompatibility.sh (and convertScriptCompatibility.bat)
- Used by administrators to convert their configuration from a mode that
supports backward compatibility of V5.x administration scripts to a mode that
is fully V6.0.
- WASPreUpgrade.sh (and WASPreUpgrade.bat)
- Saves the applications and configuration data from a previous installation
of WebSphere Application Server to a backup directory. The WASPostUpgrade
script restores the configuration data from the directory to the new installation.
The Migration
wizard calls the WASPreUpgrade.sh script during migration.
You can also use the command to perform a manual migration, after installing
the new version.
- WASPostUpgrade.sh (and WASPostUpgrade.bat)
- Restores the configuration data from a previous release. WASPostUpgrade
reads the data from the backup directory where the WASPreUpgrade script stored
the data. The Migration
wizard calls the WASPostUpgrade.sh script during migration.
You can also use the command to perform a manual migration, after installing
the new version.