Article written by David Crighton, Philip Jones, and Marisa Lopez de SilanesYou define a subflow in IBM Integration Bus (or WebSphere Message Broker version 8) to provide a common sequence of actions to be used by several message flows, applications, or services. You can include subflows in your message flows in the same way as you include built-in or user-defined nodes. You can also connect subflows to other nodes in the same way.
For the latest information about using subflows in IBM Integration Bus, see the following pages of the product documentation in IBM Knowledge Center:
A subflow provides the following benefits:
You define a subflow once, and use it in more than one message flow, application, service, and Message Broker project. You define subflow content in the same way as you define message flow content, by adding, configuring, and connecting message flow nodes.
You deploy a subflow to an execution group by sending a broker archive (BAR) file to an execution group in a broker, which unpacks and stores the contents ready for when your message flows are started.
Use the Passthrough node to enable version control of a subflow at runtime.