IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

User-defined output nodes

A user-defined output node is an extension to the broker that provides a new message flow output node in addition to the nodes supplied with the product.

If you want your message flow to send messages by using a protocol that is not supported by IBM® Integration Bus, you can create your own output node.

IBM Integration Bus provides the following output nodes:

MQOutput - delivers an output message from a message flow to a WebSphere® MQ queue
MQReply - sends a response to the originator of the input message.
SCADAOutput - sends a message to a client connecting using the MQIsdp protocol
Publication - filters output messages from a message flow and transmit them to subscribers who have registered an interest in a particular set of topics.
JMSOutput - sends a message to a JMS destination
EmailOutput - sends an email message to one or more recipients
FileOutput - writes a message to a file

If the target application expects to receive message in any other way, you must use a user-defined output node.

User-defined output nodes can be considered together with user-defined message processing nodes. Conceptually, these two kinds of user-defined nodes are the same. Although a message processing node is typically used to process a message, and an output node is used to provide an output, in the form of a bit stream, from a message, you construct output nodes and message processing nodes in a similar way, and you can use either type of node to perform either function.

You can also create a user-defined output node from a subflow, see Using a subflow as a user-defined node

For more information about user-defined output nodes, read the topics that cover user-defined message processing nodes, see User-defined message processing nodes.

as01396_.htm |

Last updated Friday, 21 July 2017