This topic describes a sample configuration sequence for connecting a WebSphere MQ link messaging engine on a WebSphere Application Server to a WebSphere MQ gateway queue manager in a WebSphere MQ network.
This sample shows a set up required to achieve connectivity between a WebSphere Application Server messaging engine (ME), and a WebSphere MQ (Version 5.3 and above) network. Connectivity is achieved using WebSphere MQ link definitions (on a WebSphere Application Server) and WebSphere MQ channels (on a WebSphere MQ network). A WebSphere MQ link definition can be thought of as synonymous with a WebSphere MQ channel definition. A WebSphere MQ link defines the properties of both the sending and receiving ends of the link on a WebSphere Application Server.
The figure below shows an overview of the sample configuration.
The figure below shows the resources and their properties.
Note: In this example context security is not set.
Routing definition can be created from the foreign bus collection panel which you navigate to through Buses>busname. The name you supply is for administration purposes only, it has no effect on routing capacity or operation.
These examples use the syntax of the runmqsc definitional program for WebSphere MQ.
DEFINE CHL(QM01.TO.BUS1) CHLTYPE(SDR) TRPTYPE(TCP) CONNAME('LONDON(5558)') XMITQ(BUS1)
Define a TCP sender channel called 'QM01.TO.BUS1' with transmission queue 'BUS1' to WebSphere MQ.
Let all other channel properties default.
DEFINE CHL(BUS1.TO.QM01) CHLTYPE(RCVR) TRPTYPE(TCP)
Define a TCP receiver channel called 'BUS1.TO.QM01'.
Let all other channel properties default.
DEFINE QL(BUS1) USAGE(XMITQ)
Define a local queue called 'BUS1' which will be used as the transmission queue for the sender channel.
Let all other channel properties default.
To send messages from WebSphere MQ to WebSphere Application Server, the following resources are defined.
DEFINE QR(RQ1) RNAME(Q1) RQMNAME(BUS1) XMITQ(BUS1)
Define a remote queue definition called 'RQ1'. This definition specifies that the remote queue name is 'Q1' and the remote queue manager name is 'BUS1'. The transmission queue associated with the remote queue definition is 'BUS1'.
Let all other channel properties default.
Let this default to the local bus and server1 (london:server1).
An application connected to queue manager QM01 would put messages to remote queue RQ1. These messages would be routed to Q1 on the target messaging engine.
To send messages from WebSphere Application Server to WebSphere MQ, the following resources were defined.
DEFINE QL(LQ1)
Let all other channel properties default.
An application connected to server1 would put messages to alias destination AQ1. These messages would be routed to LQ1 on target queue manager QM01.