Recovering after the Configuration Manager fails

Try to get to the root of the problem first, using the diagnosis techniques described throughout the Troubleshooting and support section of the information center. If your problem cannot be resolved using these techniques, contact your IBM Support Center. Use the procedure in this section only as a last resort.

If the Configuration Manager environment is damaged, or the configuration repository is corrupted, and the problem cannot be corrected using problem determination, or by the IBM Support Center, perform the following sequence of operations to re-create the Configuration Manager.

The following sequence of operations applies to Windows, Linux, and UNIX systems. For z/OS, use the JCL equivalents of the commands.

  1. Ensure that all workbench sessions are stopped.
  2. Stop the Configuration Manager using the mqsistop command.
  3. Stop the Configuration Manager's queue manager using the endmqm command.
  4. Delete the Configuration Manager using the mqsideleteconfigmgr command:
    1. If you are recovering the Configuration Manager because the configuration repository is damaged, delete it when you delete the Configuration Manager. This destroys all information pertinent to the broker domain (not just data internal to the Configuration Manager). You must export everything you can from the domain before you issue the mqsideleteconfigmgr command specifying the -n parameter.
    2. If the configuration repository is undamaged, omit the -n parameter. This preserves your configuration data in the repository.
    The mqsideleteconfigmgr command:
    • Stops the service that runs the Configuration Manager.
    • Stops and deletes the WebSphere MQ queue manager for the Configuration Manager, if requested.
    • Removes the tables from the configuration repository, if requested.
    • Removes the record for the component in the broker registry.
  5. If you are recovering the Configuration Manager because the configuration repository is damaged, restore the repository from a previously successful backup version using the mqsirestoreconfigmgr command.
  6. Recreate the Configuration Manager using the mqsicreateconfigmgr command.
  7. Start the Configuration Manager using the mqsistart command.
  8. Restart the workbench if it is not currently running, and switch to the Broker Administration perspective.
  9. If you have completed step 4a and step 5, you must also redeploy the domain configuration to ensure that the configuration across the broker domain is consistent.
Related tasks
Creating a Configuration Manager
Deleting a Configuration Manager
Deploying
Deploying a publish/subscribe topology
Recovering after failure
Related reference
mqsicreateconfigmgr command
mqsideleteconfigmgr command
mqsirestoreconfigmgr command
mqsistart command
mqsistop command