Migrating from Version 5.x to a Version 6.0.x standalone application server on a remote machine

Use the migration tools to migrate from Version 5.x to a Version 6.0.x standalone application server on a remote machine.

Before you begin

Typically, you can use the WASPreUpgrade and the WASPostUpgrade migration tools to upgrade from Version 5.x to Version 6.0.x on the same machine.

However, some scenarios require that you migrate the Version 5.x configuration on one machine to Version 6.0.x on a different machine. One of these scenarios is when you install new machines for your Version 6.0.x environment but need to migrate your existing Version 5.x configuration from other machines.

If the node you are migrating is part of a deployment manager cell, migrate the Version 5.x deployment manager to Version 6.0.x as described in Migrating from Network Deployment Version 5.x to a Version 6.0.x deployment manager first, before continuing this procedure. The deployment manager node must always be at the highest release level within the cell.
Restriction: Migrating to a Version 6.0.x deployment manager on a remote machine is not supported.

To ensure that your operating system is supported by WebSphere Application Server Version 6.0.x, visit the following site for the most current list of supported hardware and software: Supported hardware and software Web page.

If you find that your operating system is not supported for migration to Version 6.0.x, see Migrating from an operating system that is no longer supported.

About this task

The WASPreUpgrade tool saves the existing Version 5.x configuration into a migration_specific_backup directory. The WASPostUpgrade tool uses this directory to add the old configuration settings to the new Version 6.0.x environment.

Procedure

  1. Obtain the Version 6.0.x 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 Version 6.0.x.

  2. Save the current configuration using the WASPreUpgrade script from the migration/bin directory of the Version 6.0.x product CD-ROM, which you must mount to the Version 5.x machine.

    Save the configuration in the migration_specific_backup directory on the Version 5.x machine.

    [Linux]
    ./WASPreUpgrade.sh /filepath/migration_specific_backup /opt/WebSphere/AppServer
    [Windows]
    WASPreUpgrade C:\filepath\migration_specific_backup C:\Program Files\WebSphere\AppServer
    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.
  3. Copy the migration_specific_backup directory from the Version 5.x machine to the Version 6.0.x machine.

    Use the ftp command, shared storage, or some other mechanism to copy the directory to the new machine.

  4. Optional: Run the backupConfig tool from the Version 5.x app_server_root/ directory to create a backup of your Version 5.x environment.
  5. Install Version 6.0.x of WebSphere Application Server. Install the same features as the earlier release.
  6. Create a profile with the Profile creation wizard.
    Note: When you create the Version 6.0.x profile, the NodeName you choose must match one of the NodeNames in the Version 4.0.x environment.
  7. Add the Version 5.x configuration to the Version 6.0.x configuration.

    Use the WASPostUpgrade tool in the app_server_root/bin directory of the Version 6.0.x installation to add the Version 5.x configuration to the Version 6.0.x configuration.

    [Linux]
    ./WASPostUpgrade.sh /filepath/migration_specific_backup
    [Windows]
    WASPostUpgrade C:\filepath\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. Modify the configuration using the WebSphere Application Server 6.0.x administration interfaces.
    1. 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 Version 5.x machine.

    2. 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. Modify the data source to point to the database on the old machine.

Results

You have migrated WebSphere Application Server from Version 5.x to a remote Version 6.0.x machine.

What to do next

Return to Migrating configuration data to continue.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 9:31:45 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=tinsmanualmigdif251
File name: tins_manualmigdif251.html