WebSphere Message Brokers
File: ae03390_
Writer: Bill Oppenheimer

Task topic

This build: July 31, 2007 21:27:20

Adding a broker to a broker domain

This topic describes how to add a broker to a broker domain.

Before you start:

Adding a broker to the broker topology creates a broker reference in the configuration repository; it does not create the physical broker. When you add a broker, you must 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. In the Domains view, right-click the default configuration manager, and click New > Broker Reference.
  3. In the Create a Broker Reference 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. If you click Cancel at this prompt, the wizard remains open.
    2. Type the name of the broker.
    3. Type the WebSphere MQ Queue Manager Name that the Configuration Manager is using.
      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 Name 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, by default, prompted to deploy the updated publish/subscribe topology configuration.

    You only need to deploy the topology (either Complete or Delta) if you are using publish/subscribe and want to share publications or subscriptions. For more information see Publish/subscribe topology deployment.

    If you are not using publish/subscribe, click None. A deployment now (to associate the broker with the Configuration Manager) is not necessary; the broker is automatically associated with the Configuration Manager the first time a broker archive (bar) file is deployed. See Deploying a broker archive file.

    You can set user preferences so that you are not prompted to deploy the publish/subscribe topology. See Changing Broker Administration preferences. Instead, you can choose for either a complete or delta deployment to be performed automatically. Alternatively, if you are not using publish/subscribe, you might want to set the preference so that no automatic deployment takes place.

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. 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:

Add any further execution groups to the broker that you require. 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
Connecting to and disconnecting from the broker domain
Adding an execution group to a broker
Changing Broker Administration preferences
Connecting components
Deploying a broker archive file
Viewing broker domain log information
Deploying
Related reference
Broker Administration perspective
Broker Topology editor
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:27:20

ae03390_ This topic's URL is: