Configuration Manager

Start of changeThe Configuration Manager is the interface between the workbench, the configuration repository, and an executing set of brokers. It provides brokers with their initial configuration, and updates them with any subsequent changes. It maintains the broker domain configuration. End of change

The Configuration Manager is the central runtime component that manages the components and resources that constitute the broker domain.

The Configuration Manager has four main functions:

You must install, create, and start a Configuration Manager for each broker domain. on one or more machines.

You install and configure the Configuration Manager runtime component on Windows platforms only. For more information about which Windows platforms are supported see Supported operating environments.

You administer one or more Configuration Managers in the Broker Administration perspective in the workbench. More than one instance of the workbench can access a Configuration Manager concurrently.

The Configuration Manager can share a host queue manager with one broker in the broker domain. To communicate with other brokers in the broker domain, the Configuration Manager requires sender and receiver channels.

Resources associated with a Configuration Manager

When you create the Configuration Manager runtime component, the following resources are also created:
  • Start of changeA set of database tables, known as the configuration repository. You must use DB2 for these tables.End of change
  • A WebSphere MQ queue manager (unless one exists already) on the same physical system as the Configuration Manager. A queue manager can be shared with a single broker.
  • A set of fixed-name queues, defined to the queue manager that hosts the Configuration Manager.