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


Migrating to a remote system

Use the migration tools to migrate from an older version on one system to a newer version of WebSphere® ESB on a different, remote system. (Stand-alone servers only.)

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 WebSphere ESB version 6.2 onto the source 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 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 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. Navigate to the migration_copy/migration/bin directory.
  3. On the source system, save the current configuration using the WBIPreUpgrade script from the migration_copy/bin directory. Save the configuration in the migration-specific backup directory on the system hosting the older version (source system). See the WBIPreUpgrade command-line utility for details. Use one of the following scripts, depending on your operating system.
    • For Linux operating systemFor UNIX operating system On Linux/UNIX platforms: ./WBIPreUpgrade.sh /filepath/migration_specific_backup currentWebSphereDirectory
    • For Windows operating system On Windows® platforms: WBIPreUpgrade C:\filepath\migration_specific_backup currentWebSphereDirectory
    The WBIPreUpgrade command provides status to the screen and to log files in the migration_specific_backup/logs directory. Log file names start with the text WBIPreUpgrade and include a date and timestamp.
  4. Copy the migration_specific_backup directory from the source system to the target system.

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

  5. On the target system, add the configuration from the older version of WebSphere ESB configuration to the newer version's configuration using the WBIPostUpgrade command. Use the WBIPostUpgrade command in the install_root/bin directory of the new installation to add the older version's configuration (which you copied into a directory on the new system in step 4) to the newer version's configuration.
    See the WBIPostUpgrade command-line utility for details. Use one of the following scripts, depending on your operating system.
    Important: Use the -createTargetProfile parameter when invoking WBIPostUpgrade. This option creates a matching required new target profile for migration. For more information about target profiles, refer to Target profile considerations.
    Note: In the following scripts, -profileName refers to the target profile.
    • For Linux operating systemFor UNIX operating system On Linux/UNIX platforms: ./WBIPostUpgrade.sh /filepath/migration_specific_backup/-profileNameprofileName
    • For Windows operating system On Windows platforms: WBIPostUpgrade C:\filepath\migration_specific_backup/-profileNameprofileName
    The WBIPostUpgrade command provides status to the screen and to log files in the migration_specific_backup/logs directory. Log file names start with the text WBIPreUpgrade and include a date and timestamp.
  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.
  8. If the databases supporting WebSphere ESB resided on the local system in the original setup, they will now be remote to WebSphere ESB after moving to a different system. Therefore, if you used a type 2 JDBC driver you may need to switch to a type 4 driver now.
  9. Modify the configuration using the newer WebSphere ESB version's administrative 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 system hosting the older version.

    2. Change other system-specific information.

      The configuration might refer to other software products or configurations that do not exist on the new system. For example, the old system might have a database. Modify the data source to point to the database on the old system.

Results

You have migrated WebSphere ESB from the older version to a remote system hosting the newer version.

What to do next

Verify that the migration has been successful.

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_remote.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).