Hi Ravi,
Defining Sync/Async Communication
Use
To enable the communication between a synchronously calling business system (synchronous outbound interface) and an asynchronously called business system (asynchronous inbound and outbound interface), you can define a sync/async bridge in an integration process. You can only define one sync/async bridge for each integration process.
You can also achieve sync/async communication by using the JMS adapter. If you do not have any particular demand for monitoring or for troubleshooting, SAP recommends that you use sync/async communication in the JMS adapter instead. The advantage of using the JMS adapter over synch/async communication using an integration process is a significant increase in system performance.
See: Async/Sync and Sync/Async Bridge in JMS Adapter
Structure of a Sync/Async Bridge
The following table outlines the minimum components of a sync/async bridge:
Step
Use
Receive step to open the sync/async bridge
Receives the message request from the synchronously calling business system and opens the sync/async bridge
Asynchronous send step
Sends the received message asynchronously to the asynchronously called business system
Receive step
Receives the message from the asynchronously called business system
Send step to close the sync/async bridge
Sends, for example, the response from the asynchronously called business system to the synchronously calling business system
Performance Considerations
If you insert additional steps in the sync/async bridge, the synchronous time is increased correspondingly. If the time that elapses before the sync/async bridge is closed is too long, this can lead to problems.
Fault Messages
It is currently not possible to send fault messages back to the synchronously calling business system. If you want to return error statuses to the synchronously calling business system, you can define a field for an error indicator in the message that is sent to the synchronous interface.
Procedure
Define a Receive Step to Open the Sync/Async Bridge
1. Insert the receive step to open the sync/async bridge in the integration process.
You can do this at the following points:
○ Directly after the start marker
○ As the first step in a block if the block is the first step of the integration process and if it has the mode Standard
○ As the first step in a fork. If the fork already contains some starting receive steps, the Start Process indicator is automatically reset for these steps.
2. In the object area, define the container element that receives the synchronously sent message.
Specify an asynchronous, abstract interface in the container element. The message must correspond to the request message of the synchronous interface used to receive the message.
3. Select this container element in the Message field in the properties area of the receive step.
4. In the Mode field, select Open S/A Bridge.
5. Select the Start Process field.
The receive step to open the sync/async bridge must start the integration process. There must be no other receive steps to start the integration process.
6. Specify the synchronous interface for receiving the message from the synchronously calling business system. The message type of the message to be received and the request message from the synchronous interface must be identical.
Define an Asynchronous Send Step
7. Insert a send step that sends the received message asynchronously to the asynchronously called business system.
See also: Sending Messages from Integration Processes Asynchronously
Define a Receive Step
8. Insert a receive step that receives the message from the asynchronously called business system.
Define a Send Step to Close the Sync/Async Bridge
9. Insert the send step at the required position in the process definition.
Do not insert the send step in a loop, block, or fork.
10. In the Mode field, select Close S/A Bridge.
The integration process must not contain any further send steps to close a sync/async bridge.
11. In the Opened By field, specify the receive step that opened the sync/async bridge.
12. In the message field, specify the message that is sent to the synchronous interface.
This message must be of the same type as the response message from the synchronous interface that you specified in the opening receive step.
Example
You can find an example of a sync/async bridge in the Integration Repository under SAP Basis à SAP Basis 6.40, namespace http://sap.com/xi/XI/System/Patterns under BpmPatternSyncAsyncBridge.
For a description of the example, see Example: Sync/Async Communication.
BPM is an additional advantage of Netweaver XI. it provides features like Sync-Async Bridge, Async-Sync Bridge, stateful msgt processing.....so on.
Sync-Async Bridge acts as a bridge between a synchronous Business system and Asynchronous business system.
forex: if u r communicating with a synchronous RFC to a File system(always asynchronous, which is not able to send any response to synchronous RFC Interface).
In this kind of scenarios BPM Sync-Async Bridge enables communication between a Synchronous RFC to Asynchronous File system or vice versa..
Sync/async communication enables a synchronous sender system to communicate with a receiver system that cannot process synchronous messages
Plz go thru the following:
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - Use of Synch - Asynch bridge in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] - Use of Synch - Asynch bridge in ccBPM
Asyn - Synch BPM - /people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
http://help.sap.com/saphelp_nw70/helpdata/en/83/d2a84028c9e469e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/43/65d4dab39b0398e10000000a1553f6/content.htm
Example on Sync/Async communication:
http://help.sap.com/saphelp_nw04s/helpdata/en/43/65d4dab39b0398e10000000a1553f6/frameset.htm
Sync/async communication enables a synchronous sender system to communicate with a receiver system that cannot process synchronous messages
Refer this blog
/people/ravikumar.allampallam/blog/2005/02/17/bridging-the-sync-async-bridge-with-fork-xi
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi
There is an example of the Sync/Async Bridge in th SWCV: SAP BASIS.
Namespace: http://sap.com/xi/XI/System/Patterns
Asyn - Synch BPM - /people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - Use of Synch - Asynch bridge in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] - Use of Synch - Asynch bridge in ccBPM
Regards,
Vinod.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.