WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Overview of interoperation with WebSphere MQ

This topic provides an overview of what is involved in sending messages between a WebSphere MQ network and a WebSphere Application Server.

If you work in a WebSphere Application Server environment, where messages are exchanged between applications across a service integration bus, you might want to connect to applications in another messaging environment, WebSphere MQ. Using the WebSphere MQ link, exchange of point-to-point messages, and publish and subscribe is possible between WebSphere Application Server and a WebSphere MQ network, where the WebSphere MQ network is regarded as a "foreign bus". To identify the a supported version of WebSphere MQ, see the supported hardware and software Web page at http://www.ibm.com/support/docview.wss?rs=180&uid=swg27006921.

The WebSphere MQ link is defined on a messaging engine in a service integration bus. This simplifies message exchange because the messages are automatically converted so that their characteristics are either retained, or mapped to similar settings. There are some situations where the two systems work differently, and it is possible to select from the available conversion options.

Messages can flow in the following ways: It is also possible to send messages between two different buses or networks:

Whichever route you implement, the requirements are the same: the requirements of the receiving WebSphere MQ destination must be recognized, and the message must be properly transformed. This is what the WebSphere MQ link is designed for. WebSphere MQ link operates on a destination in a service integration bus, and interoperates with the WebSphere MQ network, which it regards as a foreign bus. It handles both point-to-point and publish and subscribe messaging.

WebSphere MQ Version 6 provides a new encoding format for the body of JMS Map messages. The new encoding format allows you to allocate Map entries names which are not valid XML tags, and can interoperate with WebSphere MQ Version 5.3 and above, and with WebSphere Application Server Version 6.0.2 (with the fixpack) and above, but not with the earlier WebSphere MQ versions or earlier WebSphere Application Server Version 6.0 messaging. For details of the fixpack, see the WebSphere Application Server APAR reference number PK21652. All WebSphere MQ JMS clients use the Version 6 encoding format by default; To specify the encoding format, you use the administrative console to set the encoding name/value pair as custom properties of the connection factory, queue connection factory or topic connection factory. If you specify TRUE the Version 5 encoding format is used. If you specify FALSE, the Version 6 encoding format is used. To set the encoding format, complete the following steps:
  1. From the administrative console, navigate Resources > JMS > JMS Providers > WebSphere MQ messaging provider > Queue|Topic |Connection factories > [connection factory name] > Custom properties.
  2. Specify the encoding name and value in the Name and Value fields. The encoding name is MAPNAMESTYLE and the value is a boolean, where TRUE is the v5 compatible format and FALSE is the Version 6 format.
  3. Restart the application server for the properties to take effect.
For related information, see the WebSphere MQ Using Java book in the WebSphere MQ library
http://www.ibm.com/software/integration/wmq/library/

Because it is necessary to know the properties of the WebSphere MQ applications with which your applications will interoperate, you should work with your counterpart (either an administrator or a programmer), when designing applications. Also refer to the WebSphere MQ publications library at the WebSphere MQ publications site.

For related information, see Interoperating with WebSphere MQ.


Concept topic

Terms of Use | Feedback

Last updated: 15 Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\concepts\cjc1003_.html

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