The following steps show you how to move the Configuration
Manager to
a new queue manager that is on the same computer or on a different computer:
- Use the mqsicreateconfigmgr command
to create a new Configuration
Manager that uses the new
queue manager. Do not specify a database name.
- If possible, stop all brokers in the domain using
the mqsistop command.
- Stop the original Configuration
Manager using
the mqsistop command.
- Back up the original Configuration
Manager using
the mqsibackupconfigmgr command.
- On the computer that contains the new Configuration
Manager,
use the mqsirestoreconfigmgr command
to overwrite the new Configuration
Manager's repository
with the one that you backed up.
- Start the new Configuration
Manager using the mqsistart command.
- Perform a complete deployment of the topology,
using the Message Brokers Toolkit, the mqsideploy command,
or the Configuration Manager Proxy. This tells all
the brokers in the domain to associate themselves with the new Configuration
Manager.
- If you stopped the brokers in the domain in Step 2, start them using the mqsistart command
as soon as deployment is initiated, so that the deployments can now be processed.
- If it was not possible to stop the brokers in Step 2, ensure that any messages on the original Configuration
Manager's
queue manager's SYSTEM.BROKER.ADMIN.QUEUE are transferred manually to the
new Configuration
Manager's queue manager's SYSTEM.BROKER.ADMIN.QUEUE. This is the queue that brokers use to communicate their status to the Configuration
Manager and if any status change event occurred
between stopping the original Configuration
Manager in
Step 3 and the
complete deployment in Step 7, any messages that report a change in status will have
been sent to the old Configuration
Manager.