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


Tools for version-to-version migration

You can perform migration from earlier versions of WebSphere® ESB by using a migration "wizard" (graphical user interface) or a series of commands or scripts.

Migration wizard

The migration wizard steps you through the migration process. You will be asked to fill in certain fields and make some choices provided by the wizard or use the defaults. You can invoke the migration wizard from the WebSphere ESB First Steps panel. You can also invoke it directly from install_root\bin\wbi_migration.bat (on Windows® systems) or install_root/bin/wbi_migration.sh (on UNIX-based systems).
Note: If you are using an i5/OS® operating system, you cannot use the migration wizard. You must use the migration commands.
Note: The migration wizard supports only WebSphere ESB profiles. If you have WebSphere Application Server profiles, you must use the migration commands.

Migration commands

You can use a series of scripts invoked from the command line to migrate from an earlier version of WebSphere ESB if you choose not to use the migration wizard. The following commands must be run in the correct sequence:
  1. WBIPreUpgrade - This command, which you run first, saves the existing WebSphere ESB configuration and applications into a migration-specific backup directory.
  2. WBIPostUpgrade - This command, which you run second, processes the contents of the migration-specific backup directory that was created with the WBIPreUpgrade command and imports it into the new WebSphere ESB environment.
  3. WBIProfileUpgrade.ant - This script needs to be run manually after running the WBIPreUpgrade and WBIPostUpgrade commands only if you are migrating a cell containing clusters. You might also need to run it in special cases in which migration did not occur successfully. The script updates enterprise applications and configuration settings in a profile. The WBIPostUpgrade command invokes this script and for non-clustered scenarios does not have to be manually re-run a second time.

Database upgrade scripts

Normally, if updates are required to any databases supporting WebSphere ESB components, the update is completed automatically when the migrated server process is started. However, some circumstances require that the databases be upgraded manually.

You must update the databases manually using scripts provided with WebSphere ESB in the following circumstances:
  • If the server process does not have sufficient permissions (that is, if it has not been configured with the correct user ID with sufficient permissions for the applicable database)
  • If you used non-default table spaces
  • If your servers run Business Process Choregrapher

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