An existing Windows® Configuration Manager can
be migrated to a Version 6.1 Configuration Manager on
any of the supported operating systems via a JDBC Type 4 Universal DB2® connection.
To
migrate a Configuration Manager to a different computer
that has a JDBC Type 4 Universal DB2 connection
installed, complete the following steps:
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 Broker Toolkit and connect it
to the domain of the migrated Configuration Manager.
- 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:
When you have completed these tasks, see the post-migration
tasks for information about tasks that you might want to perform after
migration.