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


Overview of migrating

Migrate from earlier versions of WebSphere® ESB.

Moving from one version of WebSphere ESB to a newer release of WebSphere ESB is referred to as version-to-version migration. Version-to-version migration occurs when you install a new version of a product, such as WebSphere ESB, and then copy relevant application and configuration data from the old installation to the new installation. With migration, the new version of the product is installed alongside the older product. Then, data is copied from the old version of the product to the new version of the product. Migrating is different from updating, in which out-of-date files or data of an existing installation are replaced with current information. Refresh packs, interim fixes, and fix packs are examples of updates. For more information on updating, see Installing Maintenance Packages.

Migration must take place from an older version of WebSphere ESB to a newer version that is running on the same operating system. You cannot migrate across different operating systems. For example, if your WebSphere ESB version 6.1.x is running on Microsoft® Windows® XP, you can migrate the data from that instance of WebSphere ESB to WebSphere ESB version 6.2 running on Windows XP. However, you could not migrate data from WebSphere ESB version 6.1.x running on Windows XP to WebSphere ESB version 6.2 running on AIX®. In the case of a standalone server only, you can migrate from a prior release of a given operating system to a new supported release of the same operating system. (Refer to Migrating from an operating system that is no longer supported for instructions on such a migration.)

The following table shows the supported version-to-version migration scenarios for this release of WebSphere ESB. You can migrate all of the products listed under "Currently installed version" to WebSphere ESB version 6.2.

Table 1. Supported version-to-version migration scenarios
Currently installed version New version
WebSphere Enterprise Service Bus version 6.0.2.x WebSphere Enterprise Service Bus version 6.2
WebSphere Enterprise Service Bus version 6.1.x WebSphere Enterprise Service Bus version 6.2
Note: If you are migrating from a version of WebSphere ESB that is earlier than version 6.0.2.x, you must first migrate to version 6.0.2.x, then migrate to version 6.2. For information about migrating to WebSphere ESB version 6.0.2.x, refer to the WebSphere ESB version 6.0.2.x information center.

Why perform version-to-version migration?

WebSphere ESB provides user application binary compatibility with prior versions. However, version-to-version migration allows you to preserve WebSphere ESB configuration data in addition to your applications when moving to a newer version of WebSphere ESB. Configuration of WebSphere ESB or WebSphere Application Server profiles, cells, clusters, servers and nodes are retained when you perform a version-to-version migration. If you did not perform this migration, and simply installed the new version of WebSphere ESB, you would need to reconfigure your environment from scratch.

For some releases of WebSphere ESB, an "in-place update" or maintenance package is available. Such an update will also preserve configuration data. In cases for which no maintenance package is available, such as when moving from WebSphere ESB version 6.1.x or version 6.0.2.x to version 6.2, a version-to-version migration is required to preserve your configuration data.

Profile types: WebSphere ESB and WebSphere Application Server profiles

You can migrate two types of profiles to WebSphere ESB version 6.2: WebSphere ESB and WebSphere Application Server profiles.
Important: Even though the following definitions refer to the Profile Management Tool as a tool that may have been used to create the profiles being migrated, you cannot use the Profile Management Tool to create new target profiles during migration. During migration, you use only the migration wizard or the command-line tools to create new target profiles.
WebSphere Enterprise Service Bus
A WebSphere Enterprise Service Bus profile is one that was created using one of the following profile templates: "default.esbserver," "dmgr.esbserver," or "managed.esbserver." When using the Profile Management Tool, this means selecting WebSphere Enterprise Service Bus on the Environment selection page.
WebSphere Application Server profile
A WebSphere Application Server profile is one that was created using one of the following profile templates: "default", "dmgr," or "managed." When using the Profile Management Tool, this means selecting one of the following choices on the Environment selection page: Application Server, Deployment Manager, or Custom profile.
Note: In a WebSphere ESB network deployment environment, the deployment manager must always be created in a WebSphere ESB profile.
Note: In a WebSphere ESB client installation, only WebSphere Application Server profiles can be created.
Table 2. Profiles supported during migration
Profile type Environment in which profile was created Can profile be migrated using the migration wizard? Can profile be migrated using command-line tools?
WebSphere Enterprise Service Bus WebSphere ESB - server installation Yes Yes
WebSphere Application Server WebSphere ESB - client installation No Yes
WebSphere Application Server WebSphere ESB - server installation No Yes

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