Before you start:For the latest details of all supported levels of hardware and software, visit the 
IBM® Integration Bus Requirements website.
This topic assumes
the following prerequisite steps:
- You are currently using the broker as an interface for functions
other than, but in addition to, publishing and subscribing, and you
want to continue to use those other functions after you migrate publish/subscribe information to WebSphere MQ.
- On distributed systems, you have set up and initialized a command
environment in which WebSphere MQ and WebSphere Message Broker commands can run.
- You have installed a version of WebSphere MQ that
supports IBM Integration Bus and you have migrated
your Version
6.1 broker's queue manager.
- The queue manager attribute PSMODE is set
to COMPAT; run the command ALTER QMGR PSMODE(COMPAT).
- You have not migrated your Version
6.1 broker
to Version
9.0 and the broker's
database definitions are still valid for WebSphere Message Broker Version
6.1.
- Your Version
6.1 broker is stopped.
Note: WebSphere MQ publish/subscribe functionality might alter the
header chains in your published message. The message body is not affected,
but avoid assumptions about the value of the CodedCharSetId field
in MQRFH2 headers when subscribing.
To migrate publish/subscribe configuration data from a WebSphere Message
Broker Version 6.1 broker to WebSphere MQ, complete the following steps:
- Start the broker on your WebSphere Message
Broker Version 6.1 system but do not attempt
to migrate the broker yet.
- Run the migration process with the -r parameter.
For information about the migmbbrk command,
see the WebSphere MQ information center.
This option rehearses the migration of the publish/subscribe configuration data from the
broker to its underlying queue manager without changing either of
the configurations. For example, on supported systems other than z/OS®, use the following command
to rehearse the migration from a broker named BRK1:
migmbbrk -r -b BRK1
On z/OS use the equivalent parameters
with the CSQUMGMB utility.
- Run the following command:
migmbbrk -t -b brokername
then
run the security commands that set up the security environment. If
you do not run these commands, migration fails.
- Run the migration process with the -o parameter.
The migration process migrates the publish/subscribe configuration data to the queue
manager, and creates a log file and a new security commands file.
For example, on supported systems other than z/OS, use the following command:
migmbbrk -c -o -b BRK1
This
command completes the following actions:
- Migrates the publish/subscribe configuration
data from broker BRK1
- Overwrites any subscription or retained publication that exists
in the queue manager
- Creates a file that has the same name as a migrating subscription
or retained publication
On z/OS use the
equivalent parameters with the CSQUMGMB utility.
- Stop the broker and check the Administration log to confirm that the broker
has stopped.
Note: After you have stopped the broker, the
queue manager is in COMPAT mode. As a result, the publish/subscribe state cannot be changed in WebSphere MQ or WebSphere Message Broker, allowing the migration
to proceed.
- Run the commands that are in your copy of the security
commands file.
- To set the PSMODE queue manager attribute
to ENABLED, run the following command:
ALTER QMGR PSMODE(ENABLED)
This command starts the queued publish/subscribe interface so that the queue
manager deals with all subsequent publish/subscribe processing.
- Continue with the migration of your Version
6.1 broker. When migration is complete,
enable content-based filtering on your Version
9.0 broker (if you are
using that feature). For more information, see Enabling content-based filtering with publish/subscribe.
Last updated Friday, 21 July 2017