WebSphere Message Brokers
File: ac00440_
Writer: Jane Brockbank

Concept topic

This build: July 31, 2007 21:16:40

End-user application support

You can connect a variety of end-user applications to the WebSphere Message Broker brokers, and take advantage of the routing, aggregation, and transformation facilities that it provides.

WebSphere Message Broker supports two application communication models:

  1. Point-to-point
  2. Publish/subscribe

These are defined in Application communication models.

Applications that use these models can connect to the broker using the following transports and protocols:

You can configure message flows to support these communication models and clients connecting over any one of these transports. Your message flows can be specific to one protocol, or can receive messages from applications communicating across one protocol and deliver messages to applications connecting across any one or more alternative protocols, with the broker providing automatic conversion between these protocols. You can also provide point-to-point and publish/subscribe support in a single message flow.

All message flows can support messages crossing from all transports to all other supported transports, Therefore if you start the message flow with an input node that supports messages from clients that connect through one transport, you can end it with any of the supported output nodes (including user-defined output nodes); you do not have to include the complementary output node.

For example, you can design the flow to receive WebSphere MQ messages and generate output messages to SCADA devices, or to receive messages from SCADA devices and generate output messages for real-time or multicast application clients. However, certain restrictions do apply depending on the transport being used: for example, messages published persistently through an MQInput node are not guaranteed to be delivered to the subscribers over WebSphere MQ Real-time Transport, because this transport does not support assured delivery.

For example, you can create a message flow that receives a message from a WebSphere MQ application. The message flow constructs a publication message from its contents, and publishes the message through a Publication node from where real-time subscribers that use JMS can register their interest in the publications. The message flow can also include an MQReply or MQOutput node to provide a confirmation message that indicates to another application that the publication has been implemented.

Related concepts
Message flows overview
Publish/Subscribe
Related tasks
Supporting end-user applications
Developing message flows
Developing publish/subscribe applications
Related reference
WebSphere MQ Enterprise Transport
WebSphere MQ Mobile Transport
WebSphere MQ Multicast Transport
WebSphere MQ Real-time Transport
WebSphere MQ Telemetry Transport
WebSphere MQ Web Services Transport
WebSphere Broker JMS Transport
Built-in nodes
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:16:40

ac00440_ This topic's URL is: