WebSphere Message Brokers
File: ae18060_
Writer: Bill Oppenheimer

Task topic

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

Connecting components

This topic describes how to make connections between the Configuration Manager, the brokers, and the User Name Server.

Before you start:

The steps below describe how to make connections between the Configuration Manager, the brokers, and the User Name Server.

If the components in your broker domain are supported by different queue managers, then you must establish WebSphere MQ connections between those queue managers to enable messages to be exchanged. It is important that each broker is able to exchange messages with the User Name Server that provides user name services for the broker.

If your broker domain components all run on the same system, and use a single queue manager, you do not need to create any WebSphere MQ connections between your brokers.

To achieve the required connection, complete the steps below. All of the steps are illustrated with MQSC examples. You can use any appropriate method for defining these resources. These examples assume that the queue managers are called COMP1 and COMP2.

In the steps below the value of 104857600 for maxmsgl is an example. Check the appropriate WebSphere MQ documentation to confirm the value for maxmsgl that you can use on your platforms.

You have to set the maxmsgl attribute only on the transmission queue that sends messages from the Configuration Manager's queue manager to the broker's queue manager.

  1. Define a transmission queue on each component's queue manager. These transmission queues collect messages ready for transmission between components. The transmission queue must have the same name as the queue manager to which it transmits messages (that is COMP1 and COMP2 for this example). Set the maxmsgl attribute to its maximum value.
    For example, on queue manager COMP1:
    define qlocal('COMP2') usage(XMITQ) maxmsgl (104857600) replace
    and on queue manager COMP2:
    define qlocal('COMP1') usage(XMITQ) replace
  2. Define the channels for the connection. Use sender-receiver pairs of channels for all two-way communications between queue managers that host WebSphere Message Broker components.
    1. Define the sender channel on the first component's queue manager (Sender(3)). This sender channel transports messages sent by the first component to the second component.

      Allocate connection names according to your WebSphere MQ network conventions, and specify the protocol that you are using for this connection and the port on which the listener is listening.

      For example, on queue manager COMP1:

      define channel('COMP1_TO_COMP2') chltype(sdr) trptype(tcp)
      conname('WBRKSYS1(1415)') xmitq('COMP2') 
      maxmsgl (104857600) replace
    2. Define a receiver channel on the first component's queue manager (Receiver(2)). Messages sent by the second component to the first component are received by this channel.
      This receiver channel must have the same name as the sender channel on COMP2, defined in Step 2c. For example, on queue manager COMP1:
      define channel('COMP2_TO_COMP1') chltype(rcvr) trptype(tcp)
      maxmsgl (104857600) replace
    3. Define the sender channel on the second component's queue manager (Sender(1)). This sender channel transports messages sent by the second component to the first component.

      Allocate connection names according to your WebSphere MQ network conventions, and you must specify the protocol you are using for this connection.

      For example, on queue manager COMP2:

      define channel('COMP2_TO_COMP1') chltype(sdr) trptype(tcp)
      conname('WBRKSYS1(1414)') xmitq('COMP1')
      maxmsgl (104857600) replace
    4. Define a receiver channel on the second component's queue manager (Receiver(4)). Messages sent by the first component to the second component are received by this receiver channel.

      This receiver channel must have the same name as the sender channel on COMP2, defined in Step 2a. For example, on queue manager COMP2:

      define channel('COMP1_TO_COMP2') chltype(rcvr) trptype(tcp)
      maxmsgl (104857600) replace
  3. Create and start a listener for each protocol in use. Create the listener in WebSphere MQ Explorer in WebSphere MQ v6, or use the DEFINE LISTENER MQSC command. For more information see Starting the WebSphere MQ channels and listeners.
  4. Start the sender channels (1) and (3) on the respective queue managers. You can set up channel initiators for these channels. Setting up receiver channels reduces overheads by allowing the channels to stop when there is no message traffic, but ensures automatic startup when there are messages to transport.

You can set up a single receiver channel on the Configuration Manager's queue manager to support all sender channels created for the brokers. Setting up a single receiver channel requires a single definition on the Configuration Manager and a single sender definition on each broker, the sender definitions on each broker must have the same name on each broker. You can also use this receiver channel on the Configuration Manager to support communications from the User Name Server.

All WebSphere MQ connections between WebSphere Message Broker components, and between clients and WebSphere Message Broker components, can be set up using any of the communications protocols supported by WebSphere MQ (TCP/IP and SNA on all operating systems; also, NetBIOS and SPX on Windows).

Related concepts
Brokers
Configuration Manager
User Name Server
Related tasks
Creating a Configuration Manager
Creating a broker
Creating a User Name Server
Connecting the User Name Server to the WebSphere Message Broker network
Enabling applications to use Publish/Subscribe
Starting the WebSphere MQ channels and listeners
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:47

ae18060_ This topic's URL is: