Output nodes

If you want to send the messages that are produced by the message flow to a target application, include one or more output nodes in the flow.

CallableReply node: Use a CallableReply in a callable flow to return a response to the CallableFlowInvoke node in the message flow that called the callable flow.
EmailOutput node: Use the EmailOutput node to send an email message to one or more recipients.
FileOutput node: Use a FileOutput node if a file is the target of the output messages.
FTEOutput node: Use the FTEOutput node to write messages to files using the WebSphere® MQ File Transfer Edition.
HTTPReply node: Use an HTTPReply node if the messages are in response to a web services client request.
JMSOutput and JMSReply nodes: Use a JMSOutput node if the messages are for a JMS destination.; The JMSReply node has a similar function to the JMSOutput node, but the JMSReply node sends JMS messages only to the reply destination that is supplied in the JMSReplyTo header field of the JMS message tree. Use the JMSReply node to treat a JMS message that is produced from a message flow as a reply to a JMS input message, and when you have no other routing requirements.
KafkaProducer node: Use the KafkaProducer node to connect to the Apache Kafka messaging system, and to publish messages from a message flow to a topic on a Kafka server.
MQOutput and MQReply nodes: Use an MQOutput node if the target application expects to receive messages on a WebSphere MQ queue, or on the WebSphere MQ reply-to queue that is specified in the input message MQMD.; Use an MQReply node if the target application expects to receive messages on the WebSphere MQ reply-to queue that is specified in the input message MQMD.
MQTTPublish node: Use the MQTTPublish node to publish an output message from a message flow to a topic that you specify on an MQ Telemetry Transport (MQTT) server.
Output node: If you are creating a message flow that you want to embed in another message flow (a subflow) that you will not deploy as a stand-alone message flow, you must include at least one Output node to propagate messages to subsequent nodes that you connect to the subflow.
An instance of the Output node represents an Out terminal. For example, if you have included two instances of the Output node, the subflow icon shows two Out terminals, which you can connect to other nodes in the main flow in the same way that you connect any other node.
Publication node: Use a Publication node to distribute the messages using the publish/subscribe network for applications that subscribe to the integration node across all supported protocols. A Publication node is an output node that uses output destinations that are identified by subscribers whose subscriptions match the characteristics of the current message.
SAPReply node: Use this node with the SAPInput node to respond to an incoming SAP event.
SOAPReply node: Use a SOAPReply node if the target application expects to receive SOAP messages in response to a message sent to the SOAPInput node.
SCAReply node: Use the SCAReply node to send a message from the integration node to the originating client in response to a message received by a SCAInput node.
TCPIPClientOutput or TCPIPServerOutput node: Use a TCPIPClientOutput node or a TCPIPServerOutput node if the messages are to be sent to the target application through raw TCP/IP sockets.
User-defined output node: Use a user-defined output node if the target is a client or application that uses a different protocol or transport.