Splitting the processing of message flows
Process parts of your message flow in different locations by creating one message flow that calls another message flow.
Before you begin
About this task
Callable flows allow you to split your message flow processing between different locations. Callable message flows also facilitate reuse because they can be called by multiple message flows. You can split your processing between IBM App Connect Enterprise and IBM App Connect Enterprise as a Service, or between different locations in App Connect Enterprise.
In App Connect Enterprise message flows, the calling flow uses a CallableFlowInvoke node to call a CallableInput node in the callable flow. The callable flow then uses a CallableReply node to return information to the CallableFlowInvoke node in the original flow.
If your calling and callable flows are in the same integration server, they can communicate with each other as soon as you deploy them. If your flows are in different integration servers, or one is in App Connect Enterprise while the other is in App Connect Enterprise as a Service, you must configure communication between them. The flows use a Switch server to route data, and connectivity agents to connect securely to the Switch server.
You can split flows into multiple callable flows. However, for simplicity, the following tasks describe how to create two flows only: a calling flow and a callable flow.
Procedure
To split the processing of your message flows, complete the following steps.
- Create your initial and callable flows. For more information, see Developing synchronously callable message flows and Developing asynchronously callable message flows.
- If your flows are split between different integration servers in App Connect Enterprise, configure connectivity between the flows. For more information, see Preparing the environment to split processing between different integration servers.
- If your flows are split between App Connect Enterprise and App Connect Enterprise as a Service, configure connectivity between the flows. For more information, see Preparing the environment to split processing between IBM App Connect Enterprise and IBM App Connect Enterprise as a Service.