Adding or modifying topic mappings on the WebSphere MQ link publish/subscribe broker

Define topic mappings on a publish/subscribe broker profile, part of the publish/subscribe bridge on a WebSphere® MQ link. A topic mapping is a mapping between a topic on a service integration bus and a stream queue and subscription point provided by a WebSphere MQ broker.

Before you begin

You have to know the bus name, messaging engine name, WebSphere MQ link name and the name of the broker profile on which you intend to define the topic mappings.

About this task

Topic mappings are associated with a WebSphere MQ link publish/subscribe broker profile. Together, the profile and topic mappings enable publication and subscription with a broker in a WebSphere MQ network.

Note: Publication messages forwarded to a message broker in the WebSphere MQ network are republished on the same topic as they were originally published to in the service integration bus topic space, and vice versa.

To define topic mappings, use the administrative console to complete the following steps:

Procedure

  1. In the navigation pane, click Service integration > Buses > bus_name > [Topology] Messaging engines > engine_name > [Additional properties] WebSphere MQ links > link_name > [Additional Properties] Publish/subscribe broker profiles > profile_name > [Additional Properties] Topic mappings
  2. In the content pane, either click New to add a new topic mapping, or click the name of a existing topic mapping that you want to modify. The Topic Mapping [Settings] form is displayed.
  3. Type the topic name.

    The name of the topic on the service integration bus. The name must be the same as the topic name on the message broker in a WebSphere MQ network.

    The topic name can contain wild cards that are in the service integration bus syntax. For more information, see Wild cards in topic mapping.

  4. Select the name of the topic space that contains the topic. If you don't select a name the default is used.
  5. Select the direction of publication flow. The direction of publication flow can be:
    Bi-directional
    Messages flow in both directions between the bus and WebSphere MQ.
    To WebSphere MQ
    Messages flow only from the bus to WebSphere MQ. That is, from WebSphere Application Server to a message broker in the WebSphere MQ network.
    From WebSphere MQ
    Messages flow only to the bus from WebSphere MQ. That is, from a message broker in the WebSphere MQ network to WebSphere Application Server.
  6. Select the broker stream queue you want to use. If the queue you require is not on the list, click other, please specify then enter the name of the broker stream queue.

    The broker stream queue in this instance is a queue on the WebSphere MQ queue manager to which the message broker is connected. This queue is being used as the input node for a message flow containing a publication node. Messages sent to this queue are processed by the message broker, then published to applications that have subscribed on the topic specified in the message.

    Stream names are case sensitive.

    After you type a new name, then save your changes, the name becomes available for selection in the drop-down list.

  7. Select the WebSphere MQ message broker subscription point from which the service integration bus receives messages. If the subscription point you require is not on the list, click other, please specify then enter the name of the subscription point.

    The default subscription point is used if no value is specified.

    After you type a new name, then save your changes, the name becomes available for selection in the drop-down list.

  8. Click OK.
  9. Save your changes to the master configuration.
  10. Optional: If you have enabled dynamic configuration updates, the changes take effect immediately. Otherwise, restart the application server.
Task topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 10:04:34 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=tjc0026_
File name: tjc0026_.html