If you choose to include a Version 5.0 broker
in a Version 6.1 broker domain, certain conditions and restrictions
apply.
If you preserve a broker at the
Version 5.0 level
of code during migration to
WebSphere Message Broker Version 6.1, the broker can
subsequently participate in the
Version 6.1 broker domain and
can be managed by the
Version 6.1 Configuration Manager.
The
Version 5.0 broker can be from either of
the following products:

- WebSphere Business Integration Message Broker Version 5.0 (Fix
Pack 6 or later)
- WebSphere Business Integration Message Broker with Rules and
Formatter Extension Version 5.0 (Fix
Pack 6 or later)
The following conditions apply:
- The Version 5.0 broker must use a unique
set of database tables. Therefore, if a Version 5.0 broker
and a Version 6.1 broker share a database, they must use different
database schemas.
- You can use a Version 6.1 Message Broker Toolkit and
a Version 5.0 Configuration Manager to
deploy to a Version 5.0 broker that is part of
a WebSphere Business Integration Message Broker Version 5.0 installation. However, if WebSphere Business Integration Message Broker Version 5.0 is at service level Fix Pack 3 or
earlier, apply Fix Pack 5 to the installation of which the Version 5.0 Configuration Manager is part.
After migration, a Version 5.0 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.
Except for user-defined extensions and mapping files, you do not need to
perform any tasks to migrate your development and deployment resources, such
as message flow files, message set definition files, ESQL files, Java files,
XML Schema files, and broker archive files. You can just start using these
resources with WebSphere Message Broker Version 6.1.
When you have migrated Version 5.0 mapping
files (.mfmap) to Version 6.1 mapping
files (.msgmap) using the mqsimigratemfmaps command,
edit them in the Version 6.1 Message Broker Toolkit.
You cannot preserve a WebSphere MQ Event Broker broker
at the Version 5.0 level of code when you migrate
a WebSphere Business Integration Event Broker Version 5.0 broker domain to a Version 6.1 broker
domain.