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

You can use the migration tools to perform a manual migration between two machines.

 

Overview

Typically you can use the WASPreUpgrade and the WASPostUpgrade migration tools from V5.1 of WebSphere Application Server to upgrade from either V3.5 or V4.0 to V5.x on the same machine.

However, some scenarios require that you migrate the V3.5 or the V4.0 configuration on one machine to V5.x on a different machine. One of these scenarios is when you install new machines for your latest V5.1 environment but need to migrate your existing V3.5.x or V4.0.x configuration from other machines.

 

Overview

This topic describes using the V5.1 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.1 environment.

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

  2. Save the current configuration using the WASPreUpgrade script from the /migration/bin directory of the V5.1 product CD-ROM, which mount to the V3.5 or V4.0 machine. Save the configuration in the migration-specific-backup directory on the V3.5 or V4.0 machine. 

    WASPreUpgrade /opt/tmp/migration-specific-backup /opt/websphere/appserver adminNodeName
    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 selected files from the V3.5.x or V4.0.x /bin directory. It also exports the existing Application Server configuration from the V3.5.x or V4.0.x repository. The WASPreUpgrade tool calls XMLConfig to export the existing V3.5 or 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 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. Copy the migration-specific-backup directory from the V3.5 or V4.0 machine to the V5.x machine.Use the ftp command, shared storage, or some other mechanism to copy the file to the new machine.

    Perform the following steps on the machine with V5.x of WebSphere Application Server.

  4. Copy the migration-specific-backup/websphere_backup.xml or the migration-specific-backup/config/server-cfg.xml file and store it as an archive.You edit the original file in the next step.

  5. Edit the migration-specific-backup/websphere_backup.xml or the /migration-specific-backup/config/server-cfg.xml file to correct machine-dependent settings.Make the following changes in the file:

    1. Change the node name in the migration-specific-backup/websphere_backup.xml file. There is no node name in the migration-specific-backup/config/server-cfg.xml file. If you are using the same node name for the V5.x machine that you use for the original V3.5 or the V4.0 configuration, do not change the name. Otherwise, change all occurrences of the V3.5 or the V4.0 node name to the node name you are using for WebSphere Application Server V5.1. The node name occurs in many XML stanzas throughout the file. Failing to change all occurrences results in an incomplete migration of data.

    2. Change the path names in the migration-specific-backup/websphere_backup.xml or the migration-specific-backup/config/server-cfg.xml file. The configuration file refers to path names in many XML stanzas throughout the file. Update any reference to a file outside of the V3.5 or V4.0 directory structure to the equivalent directory on the new machine, even if create an equivalent directory. The implication of configuring a matching environment means that you might have to copy the original directory to the V5.1 machine. Or you might have to install the appropriate software.

    3. Check files in the properties directories for references that contain path names.In particular, edit the migration-specific-backup/properties/sas.client.props and the migration-specific-backup/properties/TraceSettings.properties files to correct machine-dependent settings: Make the following changes in the file:

      1. Change the path values of any property in the file.

        Each property file contains properties that refer to paths. Update any reference to a file outside of the V3.5 or V4.0 directory structure to the equivalent directory on the new machine, even if create an equivalent directory.

      2. Correct specification styles for path values that are dependent on the operating system.

      You must correct path specifications if they differ from what works on the machine running V5.1.

    4. Correct specification styles for path names that are dependent on the operating system.You must correct path specifications if they differ from what works on the machine running . For example, if you are moving from V3.5.x or V4.0.x on a Windows platform to V5.1 on a Linux platform, change any Windows-specific path in the configuration file to use the Linux path style. Change c:\mystuff\somepath to /opt/mystuff/somepath.

    5. 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.1 machine.

      To change an encoded password to a clear-text password, change <password>{xor}LCoxayht</password> to <password>mypassword</password>.

    6. 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. The V5.x configuration should still point to the database on the old machine, possibly. Modify the data source to point to the database on the V3.5 or the V4.0 machine.

  6. Install V5.1 of the WebSphere Application Server without selecting the migration option.

  7. Add the V3.5 or the V4.0 configuration to the V5.x configuration. Use the WASPostUpgrade tool in the install_root/bin directory of V5.x to add the V3.5 or the V4.0 configuration to the V5.x configuration. 

    WASPostUpgrade /opt/tmp/migration-specific-backup
    The WASPostUpgrade tool records detailed information specific to each enterprise bean it deploys, in the migration-specific-backup/WASPostUpgrade.log file.

  8. Configure WebSphere Application Server after migration.Configuring WebSphere Application Server after migration is a way of verifying the results of the migration tools. You can read Configuration mapping during migration to learn more about the results of migration. This topic has a detailed description of how the migration tools migrate objects, and what verify.

  9. If you migrated from a machine being run as non-root processes on a Linux or UNIX platform, perform the following steps:

    1. See Running the deployment manager with a non-root user ID for instructions on how to set up the deployment manager to run as non-root processes.

    2. See Running an Application Server and node agent from a non-root user and Running an Application Server from a non-root user and the nodeagent from root for instructions on how to set up the Application Server or the nodeagent process to run as non-root processes.

 

Results

You can migrate WebSphere Application Server from V3.5.x or V4.0.x to a remote V5.1 machine.

 

What to do next

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 V5.x[V5.1 and later]
Related reference
WASPreUpgrade command
WASPostUpgrade command