+

Search Tips   |   Advanced Search

 

Migrate to a V6.1 standalone appserver on a remote machine

 

Use the migration tools to migrate from V5.x or 6.0.x to a V6.1 standalone appserver on a remote machine. See Overview of migration, coexistence, and interoperability and Premigration considerations.

Typically, you can use the WASPreUpgrade and the WASPostUpgrade migration tools to upgrade from V5.x or 6.0.x to V6.1 on the same machine. However, some scenarios require that you migrate the V5.x or 6.0.x configuration on one machine to V6.1 on a different machine. One of these scenarios is when you install new machines for your V6.1 environment but need to migrate your existing V5.x or 6.0.x configuration from other machines.

If the node that you are migrating is part of a deployment cell, migrate the V5.x or 6.0.x deployment manager to V6.1 as described in Migrating to a V6.1 deployment manager first before continuing this procedure. The deployment manager must always be at the highest release level within the cell.

To ensure that your operating system is supported by WAS V6.1, visit the following site for the most current list of supported hardware and software: WAS system requirements.

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

The WASPreUpgrade command saves the existing V5.x or 6.0.x configuration into a migration_specific_backup directory. The WASPostUpgrade command uses this directory to add the old configuration settings to the new V6.1 environment.

For help in troubleshooting problems when migrating, see Troubleshooting migration.

Before migrating a WAS V5.x or 6.0.x standalone appserver on a remote machine, use the backupConfig command or your own preferred backup utility to back up your existing configuration if you want to be able to restore it to its previous state after migration. See backupConfig command. Make sure that you note the exact name and location of this backed-up configuration.

 

Procedure

  1. Obtain the WAS V6.1 utilities disk.

    This disk contains the migration/bin directory. This directory contains a special environment used to to run the WASPreUpgrade command without installing V6.1.

  2. Save the current configuration using the WASPreUpgrade script from the migration/bin directory of the WebSphere Application Server V6.1 utilities disk, which mount to the V5.x or 6.0.x machine.

    See WASPreUpgrade command.

    Save the configuration in the migration_specific_backup directory on the V5.x or 6.0.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 command 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 WAS V5.x or 6.0.x machine to the V6.1 machine.

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

  4. Install WAS V6.1.

    See Installing the product and additional software.

    Install the same features as the earlier release.

  5. Create a profile with the Profile Management tool.

    See Creating profiles through the graphical user interface.

  6. Add the WAS V5.x or 6.0.x configuration to the V6.1 configuration.

    See WASPostUpgrade command.

    Use the WASPostUpgrade command in the app_server_root/bin directory of the V6.1 installation to add the V5.x or 6.0.x configuration to the V6.1 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.

  7. Modify the configuration using the WAS V6.1 administration console.

    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 V5.x or 6.0.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 WAS from V5.x or 6.0.x to a remote V6.1 machine.


Migrating product configurations
Use the migration tools to migrate product configurations

 

Related Reference


WASPreUpgrade command
WASPostUpgrade command