WebSphere WebSphere Application Server Version 6.1.x Feature Pack for Web Services Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

WebSphere MQ link sample configuration

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.

Sample configuration context

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 graphic shows a high-level view of the sample configuration. On the left is a WebSphere Application Server called 'Server1', which has a bus called 'Bus1'. On the bus there are three messaging engines 'ME1', 'ME2', and 'ME3'. ME1 has a WebSphere MQ link. On the right is a WebSphere MQ network which has a foreign bus called 'FB.QM01'.  On the foreign bus there is a gateway queue manager 'QM01' which is connected to two queue managers outside the foreign bus: 'QM02' and 'QM03'. The messaging engine with the WebSphere MQ link, 'ME1' on Server 1, has a connection flowing to the gateway queue manager 'QM01' on the foreign bus FB.QM01 in the WebSphere MQ network.    The gateway queue manager 'QM01' on FB.QM01 has a connection flowing to the messaging engine with the WebSphere MQ link, 'ME1' on Server 1.

Configuration

Overview of resource properties

The figure below shows the resources and their properties.

This graphic shows a detailed view of the sample configuration. On the left is a local host called 'London' with a WebSphere Application Server called 'Server1', which has a bus called 'Bus1'. On the bus there is a messaging engine: London Server1-London (QMGR: BUS1). There is an application sending to ALIASDEST(AQ1) with TARGID: LQ1 at QM01 and TARG.BUS FB.QM01. The local destination is LOCALDEST(Q1). The messaging engine has a WebSphere MQ link: MQLINK (TO.QM01). The WebSphere MQ link has a sender channel BUS1.TO.QM01, and a receiver channel QM01.TO.BUS1. The WebSphere MQ link sender channel BUS1.TO.QM01 flows to the receiver channel in the WebSphere MQ network. The WebSphere MQ link receiver channel QM01.TO.BUS1 receives from the sender channel in the WebSphere MQ network. On the right is (a WebSphere MQ network) foreign bus FB.QM01. On the foreign bus there is a gateway queue manager 'QM01'. Messages flowing from the WebSphere MQ link go into a local queue LQ1.  There is an application in the WebSphere MQ network putting messages to a remote queue RQ1: RNAME(Q1) RQMNAME(BUS1) XMITQ(BUS1). From RQ1 messages are put on the transmit queue BUS1. From there they are transmitted to the receiver on the WebSphere MQ link.

Properties of resources defined in WebSphere Application Server

Properties of resources defined in WebSphere MQ

These examples use the syntax of the runmqsc definitional program for WebSphere MQ.

  1. Sender Channel
    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.

  2. Receiver Channel
    DEFINE    CHL(BUS1.TO.QM01)
              CHLTYPE(RCVR)
              TRPTYPE(TCP)

    Define a TCP receiver channel called 'BUS1.TO.QM01'.

    Let all other channel properties default.

  3. Transmission Queue
    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.

Sending messages from WebSphere MQ to a WebSphere Application Server destination

To send messages from WebSphere MQ to WebSphere Application Server, the following resources are defined.

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.

Sending messages from WebSphere Application Server to a target local queue on WebSphere MQ

To send messages from WebSphere Application Server to WebSphere MQ, the following resources were defined.

An application connected to server1 would put messages to alias destination AQ1. These messages would be routed to LQ1 on target queue manager QM01.


Reference topic

Terms of use | Feedback


Timestamp icon Last updated: 27 November 2008
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.wsfep.multiplatform.doc/ref/rjc0222_.html

Copyright IBM Corporation 2004, 2008. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)