You can use the migration tools to migrate configuration data from Version 3.5.x or Version 4.0.x of WebSphere Application Server to WebSphere Application Server V5.x.
Before you begin
If you use an earlier version of WebSphere Application Server, the system administrator might have fine-tuned various application and server settings for your environment. It is important to have a strategy for migrating these settings with maximum efficiency and minimal loss.You can migrate administrative configurations with the installation wizard or manually, as this task describes. If you decide to migrate manually, do not select the migration check box on the installation wizard migration panel.
You can perform incremental manual migration by calling the migration tools multiple times, each time specifying a different configuration file. There are various reasons for having multiple configuration files. Whatever the reason, migrating one configuration file at a time lets you test applications incrementally before continuing to the next configuration file.
Manual migration provides a more incremental migration approach than the complete migration that the installation wizard provides. IBM provides a set of migration tools for migrating administrative configurations to the base WebSphere Application Server product from either edition of Version 3.5.x, or from Version 4.x. The overall migration process is to back up the current configuration and necessary files, install the Version 5 product, and restore the configuration.
Before using the migration tools, consult the Release Notes document to understand what fixes you must apply to earlier versions. Applying fixes to an earlier version might also apply fixes to files that have a role in the migration. Apply any fixes to ensure the most effective migration of configurations and applications possible.
Typically
you can use the WASPreUpgrade and WASPostUpgrade migration tools from V5.0.x
of WebSphere Application Server to upgrade from either V3.5 or V4.0 to 5.0.x
on the same machine. If your scenario includes migrating a V3.5.x or a V4.0.x
configuration on one machine to WebSphere Application Server 5.0.x on another
machine, use the alternate procedure described in Migrating Version 3.5.x or Version 4.0.x of WebSphere Application Server to a remote Version 5.0.x machine.
Why and when to perform this task
This topic describes using the V5.x migration tools to migrate the following products:
The WASPreUpgrade tool saves the existing V3.5 or V4.0 configuration into a migration-specific-backup directory. The WASPostUpgrade tool uses this directory to add the old configuration settings to the new V5.x environment.
Steps for this task
WASPreUpgrade /usr/tmp/migration-specific-backup /usr/websphere/appserver yourNodeNameFor all scenarios except V4.0.x Advanced Single Server Edition, verify that the administrative server of the existing environment is running.
The WASPreUpgrade tool saves all files from the following directories in the existing V3.5.x or the V4.0.x configuration to the backup directory:
The WASPreUpgrade tool saves selected files from the V3.5.x or the V4.0.x install_root/bin directory. It also exports the existing Application Server configuration from the V3.5.x or the V4.0.x repository. The WASPreUpgrade tool calls the XMLConfig tool to export the existing V3.5 or the V4.0 repository to the websphere_backup.xml file in the migration-specific-backup directory.
V4.0.x Advanced Single Server Edition does not require the administrative server to run at the time of migration. The WASPreUpgrade tool copies the server-cfg.xml file from the install_root/config directory to the migration-specific-backup/config directory.
If errors occur while running the WASPreUpgrade tool, you might have to apply fixes to the V3.5 or the V4.0 installation to successfully complete the export step. See the IBM Support page for the latest fixes that might be applicable. When viewing this information from the information center, click Support to link to the IBM Support page.
After each use of WASPostUpgrade, verify V port settings in two files:
If the BOOTSTRAP_ADDRESS port of the earlier version is 900, migration maps this to 2809. If the BOOTSTRAP_ADDRESS port of the earlier version is not 900, migration maps the value to server1 in an Advanced Edition migration, or to the actual server name in an Advanced Single Server Edition migration.
WASPostUpgrade processing adds the HTTP Transport ports from the earlier version to the Version server.xml file. This means that server1 contains duplicate HTTP Transport port assignments, from both the coexistence panel and the previous version Default Server.
The WASPostUpgrade tool does not migrate Samples or the administrative console application because there are already Samples and an administrative console application in .
Results
You can use the migration tools to perform a manual migration from Version 3.5.x or Version 4.0.x of WebSphere Application Server to .What to do next
After you test and verify that the applications and configuration data that you moved to the node work successfully, you can uninstall the V3.5.x or the V4.0.x Application Server as described in the information centers for those releases. Click the Library link at the bottom of any information center topic to locate the information centers for the other releases.Return to Migrating configuration data to continue.