If you do not have additional hardware available but want to confirm
the successful migration of the
Configuration
Manager before
replacing the
Version
5.0 Configuration
Manager,
migrate the
Configuration
Manager to a different location
on the same computer. If you use this method, you can also change the name
of the
Configuration
Manager. Complete the following steps:
- Install WebSphere
Event Broker Version 6.0 in a location other
than where WebSphere Business Integration Event Broker Version 5.0 is installed.
- Stop the Version
5.0 Configuration
Manager.
- Create a Version 6.0 Configuration
Manager using
the mqsicreateconfigmgr command.
Make sure that the Version 6.0 Configuration
Manager has
a different name and a different queue manager name to the Version
5.0 Configuration
Manager. Use the -n parameter
of the mqsicreateconfigmgr command
to specify the Version
5.0 Configuration
Manager's
database.
- Configure WebSphere MQ to allow the Version 6.0 Configuration
Manager to communicate with the broker network.
For example, you might need to configure channels and transmission queue definitions.
- Start the Version 6.0 Configuration
Manager.
- In order to associate all brokers in the domain with the new Configuration
Manager,
so that the brokers publish their status messages to the correct queue manager,
a complete topology deploy of the new Configuration
Manager is
required. Deploy the topology using either the Message Brokers Toolkit or
the command-line interface. When the topology deploy has completed re-subscribing
to the brokers in the domain, the brokers are managed by the new Configuration
Manager;
do not use the previous Configuration
Manager. You can
now delete the previous Configuration
Manager.
If you have configured MCA users on the WebSphere MQ channels to the Configuration
Manager,
you might encounter problems when you try to connect to the migrated Configuration
Manager from
the Version 6.0 Message Brokers Toolkit.
To resolve this, configure access control lists (ACLs) for users who are running
the Version 6.0 Message Brokers Toolkit.
Follow the instructions in Considering security for the workbench.
Before
you migrate your brokers, or make any configuration changes, ensure that your
Configuration
Manager has been migrated correctly by performing
the following checks:
- Start the migrated Configuration
Manager.
- Start the Message Brokers Toolkit and connect it
to the Configuration
Manager's domain.
- Check the list of domain components and see if any errors are produced.
- Check the list of alerts for the domain and see if anything has stopped.
- Check that you can open the Event Log.
- Optional: If you have a broker running, stop and start a message flow,
and check for a successful response; check that the Alerts view is updated
when the message flow is stopped, and clear when the message flow is started.
If these steps are successful, your
Configuration
Manager has
been migrated successfully. If they are unsuccessful, resolve any problems
before you migrate further components or make configuration changes.
When you have migrated the
Configuration
Manager,
ensure that you have migrated the rest of the components:
then see the
post-migration tasks for
information about tasks that you might want to perform after migration.