In IBM WebSphere Application Server Version 4.0,
automated migration support is part of the installation program.
In the preinstallation phase, the installation program
detects previously installed versions, collects information
about how you want the migrated installation to look,
and exports the current administrative configuration.
After you have updated product prerequisites,
you run the second phase, which installs the new version
of the product and imports the backed-up administrative configuration.
Before you begin,
make sure the administrative server is running.
Preinstallation phase
When you start the installation program,
it automatically detects previous installed versions of the product
and displays them in a list.
If the installation program supports migration from a selected version,
a Perform migration check box appears above the list.
The installation program prompts you for the following information:
[Windows NT and Windows 2000 only]
Directory for the new installation (default is the current installation root).
Be sure this is correct:
This information is not used until the next phase,
but you will not be able to modify it then.
Backup directory.
Directory for temporary staging.
Directory for migration log.
The installation program prompts you to start the administrative server.
Click Start Migration.
The installation program exports the current configuration
and displays the migration log file.
On UNIX and Linux installations,
the migration log is displayed only after migration is finished.
On Windows NT and Windows 2000 installations,
display of the migration log file is refreshed throughout the migration process.
When the installation program prompts you to check the
migration log file, do one of the following:
If the migration log file indicates success,
click Finish.
The next time you run the installation program,
the next phase will start.
Otherwise, click Cancel
and correct the logged errors.
The next time you run the installation program,
migration will start from the beginning.
Note for UNIX users:
If the migration log file indicates problems with
migration and you click Finish,
you cannot rerun this phase of
migration until you delete the file /tmp/WAS_Migration_temp.properties.
When this phase finishes successfully, do the following:
If you are installing Version 4.0 into the same directory structure as Version 3.x,
do one of the following:
If the migration backup directory is
within the Version 3.x directory structure,
retain the migration backup directory
but delete the rest of the Version 3.x directory structure.
Otherwise,
delete the entire Version 3.x directory structure.
Restart the installation program.
Installation and postinstallation phase
When you restart the product installation program,
it detects the following problems:
Prerequisites that have not been upgraded appropriately.
A running application server,
if the new installation directory is the same as the current one.
The product must be stopped in order for the
installation program to properly overlay the files.
[Windows NT and Windows 2000 only]
Unlike during the standard installation process, however,
you cannot modify the installation directory
during the combined installation and migration.
After installation is finished,
postinstallation migration is performed.
The installation program imports the configuration
that was exported in the first phase and
displays the migration log file.
If this phase finishes successfully,
restart the administrative server in order to complete the setup.
The administration server takes longer to start up this first time,
because it is loading the configuration file
that was created during the migration process.