If you preserve a broker at the
Version 2.1 level
of code during a migration to
WebSphere
Business Integration Message Broker Version 5.0,
the broker can subsequently participate in the
Version 5.0 broker
domain and be managed by the
Version 5.0 Configuration Manager. The
Version 2.1 broker
can be from any of the following products:
- WebSphere MQ Integrator Broker Version 2.1 at service level Fix Pack
4 or later
- WebSphere MQ
Integrator Version 2.1 at service level Fix Pack
4 or later
No other components of these products, or any previous
releases of these products, can participate in a Version 5.0 broker
domain. This means that you must migrate all your Version 2.1 Control Center, Configuration Manager,
and User Name Server components at the same time,
but you can migrate your Version 2.1 brokers
in stages.
The conditions under which a
Version 2.1 broker
can participate in a
WebSphere
Business Integration Message Broker Version 5.0 broker domain
are as follows:
- On a UNIX or Windows system, you cannot install any Version 5.0 product
code if there is Version 2.1 product code on
the system. You must first uninstall all the Version 2.1 product
code. This means, for example, that you cannot run a Version 2.1 broker
on the same system as a Version 5.0 broker or
a Version 5.0 Configuration Manager.
If
you want to preserve a broker at the Version 2.1 level
of code during a migration, and the broker is running on a system where you
need to install Version 5.0 product code, you
must move the Version 2.1 broker to another
system before you start the migration.
On z/OS, you can install Version 5.0 product code if there is Version 2.1 product
code on the system. This means that you can run a Version 2.1 broker
and a Version 5.0 broker on the same system.
- A Version 2.1 broker and a Version 5.0 broker
must use separate sets of database tables. This means that, if a Version 2.1 broker
and a Version 5.0 broker share a database, they
must use different database schemas.
- Only certain types of configuration data can be deployed to a Version 2.1 broker.
The following table shows which configuration data can be deployed to a Version 2.1 broker:
Configuration data |
Can be deployed to a Version 2.1 broker? |
Message flows |
Yes 1 |
Message sets |
Yes 2 |
Topology |
Yes |
Topics |
Yes 3 |
Broker properties |
No |
After migration, a Version 2.1 broker
can continue to use the same WebSphere MQ queue
manager, with the same WebSphere MQ configuration,
and with the same release and service level of the WebSphere MQ product
code, as it did before migration.
Note the following
additional coexistence guidelines:
- It is not possible to preserve a WebSphere MQ Event Broker broker
at the Version 2.1 level of code when you migrate
a WebSphere
MQ Event Broker Version 2.1 broker domain to a Version 5.0 broker
domain.
- You can create and operate a heterogeneous network of MQSeries Publish/Subscribe
brokers and WebSphere Business Integration Message Broker brokers. You can also
migrate MQSeries Publish/Subscribe brokers to WebSphere Business Integration Message Broker brokers.
For more information, see Migrating publish/subscribe applications.
- You cannot install WebSphere Business Integration Event Broker and WebSphere Business Integration Message Broker as separate products on the same
system. WebSphere Business Integration Message Broker, however, contains all
the function of WebSphere Business Integration Event Broker.