The topics in this section describe two different migration
scenarios that are available to you when migrating from
WebSphere MQ Integrator Broker Version 2.1 to
WebSphere Message Broker Version 6.0. The following table lists each scenario,
summarizes what is involved in that scenario, and tells you where to find
the detailed, step-by-step instructions:
Scenario |
Summary |
Detailed instructions |
Scenario 1 |
You have a domain of Version 2.1 components
that you want to migrate to Version 6.0, while
maintaining the state of each component. |
Application and server migration: migrate your applications
and runtime components. This scenario allows you to maintain the state of
the broker, for example, publish/subscribe retained
publications and subscriptions. |
Follow the instructions in Migrating from Version 2.1 to Version 6.0: migrating applications and runtime components |
Scenario 2 |
You have a Version 2.1 domain
and you want to create a Version 6.0 domain that
is running the same applications, and is running in parallel with the Version 2.1 domain. |
Application-only migration: migrate your applications
and create new runtime components, leaving the Version 2.1 components
as they are. In this scenario, you must re-create the state of your broker,
such as publish/subscribe retained publications and
subscriptions, after you have redeployed the message flow applications. |
Follow the instructions in Migrating from Version 2.1 to Version 6.0: Version 6.0 coexisting temporarily with Version 2.1 |