Sync/async communication enables a synchronous sender system to communicate with a receiver system that cannot process synchronous messages (typically a mainframe system). For more information, see the following example.
The central component of sync/async communication is the sync/async bridge, which enables the Integration Server to receive synchronous messages from a sender and send them to a receiver as asynchronous messages. Conversely, it can send the asynchronous response from the receiver back to the sender as a synchronous response.
To do this, you define an integration process, which is started as soon as a synchronous message is received from the sender system. The process uses a special receive step to open the sync/async bridge, sends the received message to the receiver system asynchronously, and waits for the asynchronous response to arrive from the receiver.
The Business Process Engine receives the asynchronous response from the receiver, correlates it with the corresponding query, and activates the waiting process, which then sends the response back to the sender synchronously.
Example
Availability checks (ATP checks) between an SAP system and a mainframe system.
· Your sender system is an SAP system and uses the RFC adapter to send synchronous RFC calls (ATP checks) to the Integration Server.
· Your receiver system is a mainframe that is already connected to a messaging system. You use the JMS adapter to send asynchronous messages from the Integration Server to this system.
No comments:
Post a Comment