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


Migrating from an operating system that is no longer supported

Use the migration tools to migrate an earlier WebSphere® ESB release that is running on an operating system that the newer version does not support. (Stand-alone servers only.)

Before you begin

Note: This procedure is supported for stand-alone servers only.
Note: When you migrate using the command-line tools, you can migrate either a WebSphere ESB profile or a WebSphere Application Server profile.
Make sure that the following conditions are met before you start the migration process:
  • Your 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.

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

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. 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. See the WBIPreUpgrade command-line utility for details. Use one of the following scripts, depending on your operating system.
    • For i5/OS operating system On i5/OS® platforms: ./WBIPreUpgrade /filepath/migration_specific_backup currentWebSphereDirectory
      Note: On i5/OS platforms, the user profile must have *ALLOBJ authority. Also, you must run i5/OS the scripts under QSHELL. To start a QSHELL session, open the CL command prompt and type QSH.
    • 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. Shut down the older WebSphere ESB release by stopping all server nodes in the configuration.
  5. Use the following procedure to back up your system, depending on your operating system:
    • For i5/OS operating system On i5/OS platforms: Perform the following backup tasks to migrate from i5/OS V5R3 to i5/OS V5R4:
      • Back up each of the WebSphere ESB or WebSphere Application Server stand-alone profiles that were configured on i5/OS V5R3 by using the WBIPreUpgrade command
      • Back up any database schemas associated with each of the profiles by using i5/OS native save commands for database collections. For example: crtsavf and savlib.
      • Back up anything special that you might have customized in these profiles.
      • Keep track of any special authorities you might have assigned to i5/OS user profiles to the configuration directories/files under each version 6.1.x profile. You can manually restore these private authorities under the target profiles after migrating to WebSphere ESB version 6.2.
    • For Linux operating systemFor UNIX operating systemFor Windows operating system On Linux®, UNIX®, and Windows platforms: Compress the backup directory (with a utility such as TAR or ZIP), and use FTP to copy the file to another system.
  6. Use the following procedure to install the new operating system, depending on which operating system you are using:
    • For i5/OS operating system On i5/OS platforms: Install the new i5/OS V5R4 or i5/OS V6R1 operating system, using the following procedure.
      1. Slip-install either i5/OS V5R4 or i5/OS V6R1 on top of i5/OS V5R3, using the instructions in the Memorandum to Users for the operating system you are installing:
      2. Apply the latest PTF (Program temporary fix) for the operating system that you slip-installed.
      3. Apply the latest PTF groups for supporting products, such as: DB2® for i5/OS, Java™, IBM® Tookbox for Java, and IBM HTTP Server.
    • For Linux operating systemFor UNIX operating systemFor Windows operating system On Linux. UNIX, and Windows platforms: Install the new operating system, keeping the same host name. If possible, keep the system name and passwords the same as on the old system. Place any database files related to applications that you are migrating in the same path as on the previous system. In general, try to keep paths the same. If you must change paths or names, make any changes with the administrative console before running the WBIPostUpgrade command as described in a later step.
  7. Use FTP to copy the backup directory from the other system, and extract it.
  8. Install the newer version of WebSphere ESB.

    See Installing and configuring WebSphere Enterprise Service Bus.

  9. Run the WBIPostUpgrade command from the newer versioninstall_root/bin directory.
    Specify the copy of the backup directory that you made in step 7. See WBIPostUpgrade command-line utility for the correct command syntax. For example:
    install_root\bin\WBIPostUpgrade wbi_installation\migration
    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.
    For i5/OS operating system Note: If you are migrating on an i5/OS platform, the target profile name must match the profile name of the source profile being migrated.
  10. 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.

  11. 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 have now migrated your configuration to an operating system that supports WebSphere ESB.

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