Adding a broker to a broker domain

Before you start:

You must have completed the following tasks:

Adding a broker to the broker topology creates a reference to the broker in the configuration repository; it does not create the physical broker. When you add a broker, be sure to use the same name that you used to create the broker.

To add a broker to a broker domain:

  1. Switch to the Broker Administration perspective.
  2. Right-click in the Domains view, and click New > Broker.
  3. In the Create a Broker wizard:
    1. Select the broker domain to which you want to add the broker. If the selected broker domain is not connected, you are prompted to connect to the domain. Click OK.
    2. Enter the name of the broker.
    3. Enter the name of the WebSphere MQ queue manager that the broker uses.
      Note:
      1. If the WebSphere MQ queue manager is on a separate machine, make sure that you have performed the steps listed in Connecting components.
      2. You can associate a WebSphere MQ queue manager with only one broker, even if the brokers are in different broker domains.
  4. Click Next.
  5. Optional: Enter a short or long description for the broker.
  6. Click Finish to add the broker to the broker domain.
  7. You are prompted to deploy the updated topology configuration. Click Delta to perform a delta topology deploy, and save the changes to the Configuration Manager. If user preferences are not set to prompt, the topology deploy is automatic.

    A BIP08921 information message is displayed to show that the request was received by the Configuration Manager. Verify the results of the deployment by opening the Event Log.

In the Domains view, the broker is added to the broker domain and a default execution group is added to the broker.

Adding a broker to the broker topology creates security ACL groups, which give the user ID full control of the broker and its default execution group. These ACL groups exist until this broker is removed from the broker domain. This means that the user ID can be removed from the mqbr* groups, but the user still has the full control access level for the broker and its default execution group.

Next:

Continue to add further execution groups to the broker if necessary. Then create, modify, or reuse message flows, message sets and other required files, and add them to the broker archive for deploying to the broker.

Related concepts
Brokers
Execution groups
Broker domains
Broker archive
Related tasks
Creating a broker
Copying a broker
Modifying broker properties
Removing a broker from a broker domain
Renaming a broker
Deploying a broker archive file
Connecting to and disconnecting from the broker domain
Adding an execution group to a broker
Changing Broker Administration preferences
Connecting components
Viewing broker domain log information
Deploying
Related reference
Broker Administration perspective
Broker Topology editor