[V5.1 and later]Migrating V3.5.x or V4.0.x of WebSphere Application Server to V5.x

You can use the migration tools to migrate configuration data from V3.5.x or V4.0.x of WebSphere Application Server to WebSphere Application Server V5.x.

 

Overview

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 V3.5.x, or from V4.x. The overall migration process is to back up the current configuration and necessary files, install the V5 product, and restore the configuration.

Before using the migration tools, consult the Release Notes document to understand what fixes 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.

[V5.1 and later]Typically you can use the WASPreUpgrade and WASPostUpgrade migration tools from V5.1 of WebSphere Application Server to upgrade from either V3.5 or V4.0 to V5.1 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 V5.1 on another machine, use the alternate procedure described in Migrating V3.5.x or V4.0.x of WebSphere Application Server to a remote V5.1 machine.

 

Overview

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.

  1. Obtain the new 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 the product.

  2. Save the current configuration using the WASPreUpgrade command from the migration/bin directory of the product CD-ROM.Save the configuration in the migration-specific-backup directory: 

    WASPreUpgrade /usr/tmp/migration-specific-backup /usr/websphere/appserver yourNodeName
    For all scenarios except V4.0.x Advanced Single Server Edition, verify that the administrative server of the existing environment is running.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.

    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:

    For V3.5.x

    • bin

    • classes

    • deployableEJBs (Advanced Edition only)

    • deployedEJBs (Advanced Edition only)

    • hosts

    • properties

    • servlets

    For V4.x

    • bin

    • classes

    • config (V4.0.x Advanced Single Server Edition only)

    • installableApps

    • installedApps

    • installedConnectors (V4.0.x Advanced Edition only)

    • properties

    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.

  3. Install V5.1 of the WebSphere Application Server Vproduct, as described in Installing the product. Do not select the migration option, if it appears.

    After each use of WASPostUpgrade, verify V port settings in two files:

    • Verify the BOOTSTRAP_ADDRESS port assignment for server1 in the serverindex.xml file

      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.

    • Verify the HTTP Transport port assignments in the server.xml file

      WASPostUpgrade processing adds the HTTP Transport ports from the earlier version to the V server.xml file. This means that server1 contains duplicate HTTP Transport port assignments, from both the coexistence panel and the previous version Default Server.

  4. Migrate the previous configuration to the new installation with the WASPostUpgrade tool in the install_root/bin directory of the installation. The WASPostUpgrade tool migrates V3.5.x or V4.0.x configuration information created by the WASPreUpgrade tool to the installation. Because the product adheres to the J2EE programming model and V3.5.x does not, significant changes are required to apply the V3.5.x configuration to a installation.

    The WASPostUpgrade tool does not migrate Samples or the administrative console application because there are already Samples and an administrative console application in .

    The WASPostUpgrade tool records detailed information specific to each enterprise bean it deploys, in the WASPostUpgrade.log file.

  5. Stop the administrative server of the earlier version if it is running, before running the node.

  6. Configure WebSphere Application Server after migration, as described in Configuring WebSphere Application Server after migration. Configuring WebSphere Application Server after migration is a way of verifying the results of the migration tools. You can also use configuration mapping during migration, as described in Configuration mapping during migration to verify the results of the migration. The topic has a detailed description of how the migration tools migrate objects, and what verify.

 

Results

You can use the migration tools to perform a manual migration from V3.5.x or V4.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.

Related concepts
Migrating
Migration tools
Related tasks
Migrating configuration data
Migrating V3.5.x or V4.0.x of WebSphere Application Server to a remote V5.1 machine[V5.1 and later]
Related reference
WASPreUpgrade command
WASPostUpgrade command