WebSphere Business Integration Message Broker Basics

126 WebSphere Business Integration Message Broker Basics

subflow in the Error Handler sample demonstrate the Input node. The Scribble

sample demonstrates the Real-timeInput node.

4.4.2 Getting output from a message flow

So that business applications can receive messages from the message flow, the

message flow must have at least one output node. The BookstoreFlow message

flow contains an MQOutput node because the message flow puts the messages

on a WebSphere MQ queue.

The output node that is used in a message flow depends on the type of

application that receives the message from the broker:

򐂰 If the message flow puts the message to the application by means of a

WebSphere MQ queue, use an

MQOutput node.

򐂰 If you want the message flow to put different messages on different

WebSphere MQ queues, depending on the queue name in the Reply-to

queue field of the message header WebSphere MQ, use an

MQReply node.

Using the MQReply node means that the name of the output queue is not

hardcoded in the message flow.

򐂰 If the messages are received by a telemetry device, use a

SCADAOutput

node

.

򐂰 If the messages are received by a Web services client, use an

HTTPReply

node

.

򐂰 If the message flow interacts with a Web services client, use an

HTTPRequest

node

.

򐂰 If the messages are received by a JMS or multicast application, use a

Real-timeOptimizedFlow node. This node performs as both an input and an

output node.

򐂰 If the message flow is to be reused as part of one or more other message

flows, use an

Output node.

򐂰 If you want to distribute the messages, using Publish/Subscribe, to many

unknown applications that have subscribed to receive the data, use a

Publication node.

All of the output nodes that are available in WebSphere Business Integration

Message Broker Version 5.0 are shown in Figure 4-30 on page 127. The node

called Output node, like the Input node, is slightly different from the others

because it is used exclusively in subflows. The Publication node is also different

because the destination of the messages depends entirely on whether the

receiving applications have subscribed to the information that the messages