Topic mapping on a WebSphere MQ link

A topic mapping is an association that defines which messages published in WebSphere® Application Server or the WebSphere MQ network, should be forwarded to the other publish/subscribe system.

You define one or more topic mappings for a broker profile. The broker profile defines the connection between WebSphere Application Server and a WebSphere MQ queue manager or separate publish/subscribe broker. The topic mapping links a specific topic in the WebSphere Application Server service integration bus with its equivalent in the WebSphere MQ network.

When you define a topic mapping, you choose if messages are to flow from WebSphere MQ to WebSphere Application Server, or from WebSphere Application Server to WebSphere MQ, or if the flow is two-way, or bidirectional. If a topic mapping is bidirectional, a message is safeguarded from being continually republished on alternating sides of the publish/subscribe bridge.

In your topic mapping, the topic name and its position in the hierarchy (or tree) of topics must be the same in WebSphere Application Server and in the WebSphere MQ network. You can use wild cards, as described in Wild cards in topic mapping. For example, if you set up a topic mapping for "stock/IBM" with a direction from the WebSphere Application Server service integration bus to WebSphere MQ, the publish/subscribe bridge subscribes to the topic "stock/IBM" in WebSphere Application Server, and receives the messages published to the topic. The publish/subscribe bridge then publishes the messages to the topic "stock/IBM" in the WebSphere MQ network.

Messages published by a service integration JMS client are transferred to a WebSphere MQ network if an appropriate topic mapping has been created. This is presented to the WebSphere MQ network as only the topic name, for example, "sports/football". A suitably configured WebSphere MQ JMS application can use this information to publish further information to the same topic, but the original WebSphere Application Server JMS application receives these messages only if appropriate topic mapping has been configured.

If you delete a WebSphere MQ link, you must first unsubscribe and delete your topic mappings, to ensure there are no outstanding subscriptions in WebSphere Application Server or the WebSphere MQ network. For the process to unsubscribe, see Preparing to remove a foreign bus connection between a service integration bus and a WebSphere MQ network.




Related tasks
Adding or modifying topic mappings on the WebSphere MQ link publish/subscribe broker
Preparing to remove a foreign bus connection between a service integration bus and a WebSphere MQ network
Concept topic Concept topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 6:15:55 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-express-dist&topic=cjc0015_
File name: cjc0015_.html