defining channels, definition, channel" /> Connecting to the generic interface
Home

 

Connecting to the generic interface

Connecting to the generic interface of a queue-sharing group will open a session with one of the queue managers in the group. The generic interface can be a WLM/DNS group name or a VTAM generic resource name, or another common interface to the queue-sharing group. See WebSphere MQ Intercommunication for more details on setting up a generic interface.

Connecting to the generic interface increases front-end availability, because the client queue manager can connect with any queue-manager in the group. You connect to the group using the generic interface when you do not want to connect to a specific queue manager within the queue-sharing group.

 

Creating channel definitions

To connect to the generic interface of a queue-sharing group we need to create channel definitions that can be accessed by any queue manager in the group. To do this we need to have the same definitions on each queue manager in the group.

Define the SVRCONN channel as follows:

DEFINE CHANNEL(CHAN1) CHLTYPE(SVRCONN) TRPTYPE(TCP) +
MCAUSER(' ') QSGDISP(GROUP)

Channel definitions on the server are stored in a shared DB2 repository. Each queue manager in the queue-sharing group makes a local copy of the definition, ensuring that you will always connect to the correct server-connection channel when you issue an MQCONN or MQCONNX call.

Define the CLNTCONN channel as follows:

DEFINE CHANNEL(CHAN1) CHLTYPE(CLNTCONN) TRPTYPE(TCP) +
CONNAME(WLM/DNS groupname) QMNAME(QSG1) +
DESCR('Client-connection to Queue Sharing Group QSG1') QSGDISP(GROUP)

Because the generic interface of the queue-sharing group is stored in the CONNAME field in the client-connection channel, we can now connect to any queue manager in the group, and put to shared queues owned by that group.



 

Home