CallableInput node

You can split message flows so that you do processing in different locations. You can split your processing between different locations in IBM® Integration Bus, between IBM Integration Bus and IBM App Connect on IBM Cloud. You can split your flows between different applications in the same integration server, or between different integration servers, which can be in different integration nodes. A calling flow processes information in one location, then calls another flow in another location. The calling flow includes either a CallableFlowInvoke node or a CallableFlowAsyncInvoke node, depending on whether the flow will be invoked synchronously or asynchronously. The node that you have included in the calling flow (the CallableFlowInvoke or CallableFlowAsyncInvoke node) calls a CallableInput node in a second (callable) flow.

When the message is processed by the callable flow, a CallableReply node returns message body and local environment folder data to either the CallableFlowInvoke node in the original flow (if a CallableFlowInvoke node was used to call the CallableInput node) or to the CallableFlowAsyncResponse node in a separate response flow (if a CallableFlowAsyncInvoke node was used to call the CallableInput node).

You specify an endpoint name on the CallableInput node of the callable flow. The CallableFlowInvoke or CallableFlowAsyncInvoke node calls the correct callable flow by specifying the application that contains the callable flow, and the endpoint name that is specified on the CallableInput node. Therefore, you must deploy all callable flows in applications.

Application and endpoint name pairs must be unique on a single integration server. You can have multiple callable flows that share the same application and endpoint names, but they must be in different integration servers. In this case, the Switch server acts as a load balancer.

The CallableInput node is contained in the Callable Flow drawer of the palette, and is represented in the IBM Integration Toolkit by the following icon:

When you have put an instance of the CallableInput node into a message flow, you can configure it; see Configuring a message flow node. The properties of the node are displayed in the Properties view. All mandatory properties for which you must enter a value (those that do not have a default value defined) are marked with an asterisk.

The following tables describe the node properties. The column headed M indicates whether the property is mandatory (marked with an asterisk if you must enter a value when no default is defined); the column headed C indicates whether the property is configurable (you can change the value when you add the message flow to the BAR file to deploy it).