Asynchronous Callable Flows in IBM App Connect V12
Asynchronous message in IBM App Connect V12:
- Asynchronous Messaging means it is one-way communication, which means that it does not wait for a response message from the server.
- The asynchronous message will send messages continuously if the client is down also.
- Asynchronous messaging enables flexibility and offers higher availability – There is less pressure on the system to act on the information or immediately respond in some way. In addition, one system being down does not impact the other system
Synchronous message in IBM App Connect V12:
- Synchronous messaging in IBM App Connect V12 involves a client that waits for the server to respond to a message.
- Synchronous messaging is two-way communication. i.e. sender sends a message to the receiver and the receiver receives this message and gives a reply to the sender.
- The sender will not send any message until gets a response to the previous message.
Callable Flow Nodes in IBM App Connect V12:
- Sometimes we need to call and access data from different locations. At that time, if we use callable flows we can directly fetch the data synchronously or asynchronously.
- Using callable flows data can be transferred in a secured way
- Callable flows are used to call flows at different locations. If the IBM App Connect is available at IBM Cloud or remote locations, using callable flows, we connect to that App Connect and we can send & receive data from there.
- Here we have a synchronous and asynchronous way of transferring data from different locations. We use MQ for asynchronously transferring data so that the application cannot get that much pressure.
- Callable flows can complete different actions.
- If any of those are having a large amount of data. We can split that data and can be sent in parts from the main flow. Here data loss will not be there.
- Callable flows are reusable flows and can be called from multiple flows at a time. Callable flows can be at the same integration server or different servers or different nodes but should be in the application not to be in libraries.
- You can split processing between synchronously callable message flows by using the Callable Flow Invoke node in the calling flow, and Callable Input and Callable Reply nodes in the callable flow.
- Alternatively, you can split processing between asynchronously callable message flows, by using the Callable Flow Async Invoke node in the calling flow, Callable Input, and Callable Reply nodes in the callable flow, and the Callable Flow Async Response node in the response flow.
When you pass a message into the main message flow, the Callable Flow Async Invoke node sends the contents of the message body and local environment folders to the Callable Input node of the callable flow and then completes. When the callable flow completes processing, the Callable Reply node sends the message body and local environment folder data to the Callable Flow Async Response node in the separate response flow.