This topic describes what you must do before you start to migrate a WebSphere MQ Event Broker Version 2.1 broker domain in any of the following tasks:
Before you start to migrate a WebSphere MQ Event Broker Version 2.1 broker domain, do the following:
For information about how to use the Control Center to perform this and other tasks, see WebSphere MQ Event Broker Version 2.1 Using the Control Center.
For advice on how to export the message flows, see Migrating a message flow.
You can view this information in a Control Center session and record it manually.
When you migrate, you delete all the components of WebSphere MQ Event Broker and drop all the database tables used by the Configuration Manager and the brokers. However, to simplify the task of configuring the new broker domain, you can preserve the databases and queue managers used by the brokers you want to migrate. If you are migrating a single broker domain from WebSphere MQ Event Broker to WebSphere Business Integration Message Broker, you can also preserve the database and queue manager used by the Configuration Manager, and the queue manager used by a User Name Server.
You do not need to change the configuration of a queue manager that is preserved during migration. You might, however, need to ensure that the WebSphere MQ product code is at the required release and service level to support WebSphere Business Integration Message Broker. At the same time, you might want to ensure that you have installed the other software prerequisites. See Checking software prerequisites for the details.
Related tasks
Migrating from WebSphere MQ Event Broker Version 2.1 to WebSphere Business Integration Message Broker Version 5.0
Migrating a message flow
Checking software prerequisites
Migrating from WebSphere MQ Event Broker Version 2.1 and WebSphere MQ Integrator Broker Version 2.1 to WebSphere Business Integration Message Broker Version 5.0
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah13810_ |