WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Migrating from a 32-bit Windows platform to a 64–bit Windows platform

If you have a WebSphere® ESB version 6.0.x or 6.1.x installation that is installed on a Windows 32-bit operating system, you can migrate your existing stand-alone profiles to a 64-bit version of WebSphere ESB version 6.2 installed on a Windows 64-bit operating system. before performing the migration to WebSphere ESB version 6.2.

Before you begin

Note: This procedure is supported for stand-alone servers only.
Make sure that the following conditions are met before you start the migration process:
  • Your target system meets all the hardware and software requirements for the new version of WebSphere ESB.
  • Sufficient disk space is available for the migrated profile and its backup. See Premigration considerations for WebSphere ESB for disk space requirements.
Make sure that you have completed the following tasks before you start the migration process:
  • Back up the databases that support version 6.0.2.x or version 6.1.x WebSphere ESB components.

See Overview of migrating and Premigration considerations for WebSphere ESB.

Typically, you can use the migration tools to upgrade from an older version to a newer version on the same system. However, some scenarios require that you migrate the old version's configuration on one system to the new version of WebSphere ESB on a different system. One of these scenarios is when you install new systems for your environment based on the newer version but need to migrate your existing older configuration from other systems.

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

About this task

The WBIPreUpgrade command saves the existing older version configuration into a migration-specific backup directory. The WBIPostUpgrade command uses this directory to add the old configuration settings to the newer version environment.

Procedure
  1. Copy the WBIPreUpgrade utility and its related files from the 32–bit version of WebSphere ESB version 6.2 onto the source (32–bit) system. To do this, use one of the following procedures.
    1. On the target system, create a .zip or .tar.gz file of the installation files to copy to the source system. To do this, use the following procedure.
      Note: You must already have the 32–bit version of WebSphere ESB version 6.2 installed on the target system to use this procedure.
      1. Navigate to the WPS62_HOME/util/migration directory on the target system.
      2. Run one of the following commands, depending on your operation system.
        • For Linux operating systemFor UNIX operating system On Linux and UNIX platforms: createRemoteMigrationImage.sh full_path_name_of_the_new_.tar.gz_file

          Example: createRemoteMigrationImage.sh /tmp/migrationImage.tar.gz

        • For Windows operating system On Windows platforms: createRemoteMigrationImage.bat full_path_name_of_the_new_.zip_file

          Example: createRemoteMigrationImage.bat C:\migrationImage.zip

      3. Copy the migration image .zip file from the target system to the source system (the system that has version 6.0.x or 6.1.x of WebSphere ESB installed on it).
      4. Unzip the migration image file to a new directory called migration_copy.
        Note: This directory can be any name you choose. We are using "migration_copy" here for explanatory purposes.
    2. Copy the files from the JDK and migration directories of the 32–bit WebSphere ESB version 6.2 DVD. To do this, use the following procedure. Copy the migration and JDK directories from the WPS/ESB Version 6.2 DVD to a new directory . For instance, we use (migration_copy for explanatory purposes.)
      1. Create a new directory on the source system called migration_copy.
        Note: This directory can be any name you choose. We are using "migration_copy" here for explanatory purposes.
      2. Copy the migration and JDK directories in the new directory.
    You should now have the following directory structure on your source system:
    migration_copy/
       migration/
       JDK/
  2. Copy the backup directory of the WebSphere ESB version 6.0.x or 6.1.x installation to another system.
  3. Install Windows® 2003 64-bit operating system on the system where you want to perform the migration.
  4. Install WebSphere ESB version 6.2 on the system with the new Windows 2003 64-bit operating system.
  5. Run the WBIPostUpgrade command against the backup directory to complete the migration.
  6. If you are migrating from version 6.0.2 to version 6.2.x you need to create the common database.

    For information, see Creating the common database and configuring the recovery subsystem when migrating from version 6.0.2 to version 6.2.x.

  7. If required, manually update the databases used by WebSphere ESB. Some database changes required by new versions of WebSphere ESB are made automatically. However, if you have Business Space configured, or if the server has insufficient permissions to access the database schema, or other database-specific requirements are not met, you must update the database manually. For more information see Upgrading databases for migration.

Results

You migrated to WebSphere ESB version 6.2 from a version 6.0.x or 6.1.x installation that was installed on a Windows 32-bit operating system.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tmig_vtv_32_to_64.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).