You can view this information in the workbench and record it manually.
When you migrate a broker domain from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Business Integration Message Broker Version 5.0, you can preserve some or all of your brokers at the Version 2.1 level of code. These brokers can participate in the Version 5.0 broker domain but, at any time subsequently, you can migrate the brokers to the Version 5.0 level of code, and you can do this in stages if you wish. This topic describes how to migrate a Version 2.1 broker to the Version 5.0 level of code when the Version 2.1 broker is already participating in a Version 5.0 broker domain.
If two or more brokers run on the same UNIX or Windows system, you must migrate them all at the same time. See Coexistence with previous releases and other products for more information. If two or more brokers share the same set of database tables, you must migrate all of these brokers at the same time. If you do need to migrate multiple brokers, on the same system or on different systems, you can adapt the instructions that follow.
The information in this topic assumes that you are migrating a WebSphere MQ Integrator Broker Version 2.1 broker. The same information applies, however, if you are migrating a WebSphere MQ Integrator Version 2.1 broker. Simply replace all references to "WebSphere MQ Integrator Broker" with "WebSphere MQ Integrator" in the instructions that follow.
If you are migrating a WebSphere MQ Integrator Version 2.1 broker that is participating in a WebSphere Business Integration Message Broker with Rules and Formatter Extension Version 5.0 broker domain, replace all references to "WebSphere Business Integration Message Broker" with "WebSphere Business Integration Message Broker with Rules and Formatter Extension" in the instructions that follow. For instructions on how to migrate the New Era of Networks Rules and Formatter support for WebSphere MQ Integrator, see the New Era of Networks documentation.
To migrate a Version 2.1 broker to the Version 5.0 level of code, do the following:
On a UNIX or Windows system, you stop a broker by issuing the mqsistop command with the name of the broker. For information about how to use the mqsistop command, see the WebSphere MQ Integrator Broker Version 2.1 Administration Guide.
On z/OS, you stop a broker by stopping the started task.
On a Windows system, do not select the option to uninstall WebSphere MQ Integrator Broker completely, including data.
On z/OS, you do not need to remove the WebSphere MQ Integrator Broker product code.
Recreate only the assignments configuration data you want to preserve. Use the information you recorded previously to prepare the broker archive file. When the broker archive file is ready, deploy it to the broker.
For detailed instructions on how to perform this task, see Deploying message flow applications.
Deploy migrated message flows and message sets to a test environment first of all. When you are sure that they are working correctly, you can then deploy them to a production environment.
Related concepts
Coexistence with previous releases and other products
Related tasks
Installing on AIX
Installing on HP-UX
Installing on Solaris
Installing on Windows
Installing on z/OS
Changing the ODBC connection and XA resource manager definitions for a migrated broker
Configuring a migrated broker on z/OS
Starting and stopping a broker on UNIX platforms
Starting and stopping a broker on Windows
Starting the broker
Adding an execution group to a broker
Deploying message flow applications
Deploying a topology configuration
Deploying a topics hierarchy
Related reference
mqsimigratetables command
mqsistart command
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah13800_ |