BpmPatternSyncAsyncBridge

I am trying to do the following scenario with bpm ( synch/asynch bridge) BpmPatternSyncAsyncBridge pattern.
Scenario:
1. Http client calls BPM synchronously (open the S/A bridge).
2. BPM sends the received message to file adapter.
3. Another process reads the files and produces an output file (or I can do this manually).
4. The output file is sent back to BPM.
5. BPM returns the output message back to http synch (closes S/A bridge)
I am using the existing design objects in IR. I am not sure how to configure in ID
Should the http client call the integration process BpmPatternSyncAsyncBridge directly using the interface BpmPatternBridgeSyncIf? If so do I need a business service for that?
Or should it call the BpmPatternBridgeRequest interface?
I have searched all the blogs as far I can, but nowhere there is sample configuration for synch/asynch bridge.
Please help.
Thanks

Thanks Krishna. That is the first thing I tried, it didn't work that is why I am using this existing design obecjts provided by SAP.
<i>Then do the configuration as you do for normal Source->BPM->Target Scenario.</i>
This doesn't seem to be a normal configuration, becasue usually the first receive step will accept an asynchronous abstract message interface, but in this case the first receive step accepts asynchronous abstract message interface and a synchronous abstract message interface.
So which one needs to be sent to the BPM, asynchronous abstract message interface or the synchronous abstract message interface?
<i>
1) Source to BPM
2) BPM to File
3) File to BPM
4) BPM to File</i>
I have configured this way only, but for Source to BPM
Reciever determination I am not sure what are the message interfaces I need to use?

Similar Messages

Time-out Exception with S/A Bridge BpmPatternSyncAsyncBridge pattern

Receiving a Time-out Exception when the BpmPatternSyncAsyncBridge pattern in software component SAP_BASIS 6.40, is waiting on Synchronous response. We are using the BpmPatternSyncAsyncBridge pattern and need to send a synchronous response back to client and continue with the Asynchronous backend processing. It appears that the Synchronous send step is waiting for the previos Asynchronous receive step to complete.

Hi Dan,
probably the correlation during the asynchron receive step did not work well.
Regards Udo

About interfact mapping.

can anybody tell me!
how many types interface mapping according to the mode of both interface?
sync 2 async
sync 2 sync
async 2 async
async 2 sync
the case above must be appeared?
please describe them respectively via each concrete scenario!
thanks a lot!

Sync2Async:
Refer this step by step
http://help.sap.com/saphelp_nw04/helpdata/en/43/65d4dab39b0398e10000000a1553f6/frameset.htm
You can find the examples in the Integration Repository under SAP Basis , namespace http://sap.com/xi/XI/System/Patterns under BpmPatternSyncAsyncBridge
Also check Usage of Sync-Async when both Sender and Receiver are Synchronous Apps
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
sync 2 sync
Here the INterface maping will be 1 which contains both the reuest mapping and response mapping
async 2 async
Here also the interfce mapping is 1 ( normal design)
async 2 sync
difference between syn/asyn vs asyn/syn Bridge
might be helpfull

Doc on Async and Sync using BPM

Hi all
Can anyone send some docs explaining the steps involved in bridging async and sync interface using BPM. The source adapter is JDBC and target is proxy. I've already checked one blog by krishna moorthy (File-File using BPM) and based on that i tried but coudnt get the expected result for my scenario.
Thkx

Hi PS,
in your Integration Repository go to:
Software Component: SAP BASIS
Namespace: http://sap.com/xi/XI/System/Patterns
Process: BpmPatternSyncAsyncBridge
This is a very good example!
Regards Mario

Is it possible to create soap to file sync/async bridge

Hi All,
I am balakrishna, I have one requirement, at sender side we have ep system and at receiver side having http system. from ep side we are using soap req/res as sync communication. At reciver side we have to use the reciver file adapter as a dummy because receiver file adapter doesn't pick the file from the http links. so, again we have to use the sender file adapter to pick the files (text/excel) from the http links directly using wget os command. how can i implement this scenario using bpm.

Hi,
You will find a sample BPM for sync/async bridge under
SAP BASIS --> http://sap.com/xi/XI/System/Patterns --> Integration Process --> BpmPatternSyncAsyncBridge.
Your requirement would be similar to this.
Regards

BPM correlation and Sync-Asyn Bridge....

Regarding Sync-Asyn ,I have gone thru these blogs...
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] [original link is broken] [original link is broken] - Use of Synch - Asynch bridge in ccBPM
I am not able to do a end to end scenario...using this ....So could any one give me a step by step guide for the syn-asyn Bridge.
And also step by step for correlation...
Please help me in this regard....

Hi,
Defining Sync/Async Communication
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.
Reg,
suresh

Webservice to IDOC : Bridge sync/async

Hi,
I have a simple scenario where we send data synchronously via webservices and idoc would be created in target system.
So I need to create a sync/async bridge.
But i have a doubt in first receiver step and its properties:
Syncronous interfaces --> it must be a SYNC and abstract message interface
Message --> It must be an element of container. When i create element in container, only abstract ASYNC message interface could be selected.
Then, with this configuration, error " Message to be received and synchronous interface do not have identical types " is returned.
How to do it?
Thanks, in advance
Carme.

Hi Carme,
Just make sure you are making a SYNC/ASYNC bridge in BPM as explained in the following doc's
saptechnical. com/Tutorials/XI/SYNCASYNC/Page2.htm
Alternatively you can use the BPM pattern; BpmPatternSyncAsyncBridge for the same.
http://help.sap.com/saphelp_nw04/helpdata/en/83/d2a84028c9e469e10000000a1550b0/frameset.htm

Supported SP for BPM in XI 3.0

Hi All
i want to do the FILE RFC FILE using BPM in XI 3.0 with the help of following blog
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
what SP should my XI 3.0 should have?
Regards
bhasker

Hi Bhakser
XI 3.0 SP16 is a very old release but yes, it is possible to configure a sync/async bridge.
Defining Sync/Async Communication
http://help.sap.com/saphelp_nw04/helpdata/en/43/65d4dab39b0398e10000000a1553f6/content.htm
As per this link you will be able to find an example in your SP16 release.
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.
Regards
Mark

Sycn/Async Bridge?

Hi Experts,
Can anyone explain me the importance of Sync/Async bridge and in which type of scenarios it is mostly used.....plz suggest any web blog which explains in detail abt Sync/Async bridge.........
Cheers
Faisal
Points will b rewarded for useful answers.....

Hello Abdul,
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
Thanks,
Satya Kumar
Reward points if it is useful..
Edited by: SATYA KUMAR AKKARABOYANA on Apr 18, 2008 3:00 PM

Correlation

hi all.
i cant finish understand when to use a correlation in BPM. i was reading at Help Sap but the idea still is not clear.
can anyone explain me with your own word what is a correlation and when for example i can use it.
im watching BpmPatternSyncAsyncBridge and i cant understand why receive step use correlation.
Rgds

Rodrigo,,
Correlation allows you to hold the messages in BPM before processing..
But we need to some criteria / field value to hold messages in BPM depending on the requirement...
For eg..
Consider a scenario where Purchase order header and purhcase order items are coming from different files...and you have to generate one complete message in XI before passing to R/3 for posting..
Also i know that both files having purchase order number ( Heade / Line Items)....
Now there could be "N" number of Header files and correpponding "Line Item" files.... Hence here I will create a correlation on Purchase order number..so my Business process can related / hold receving Purhcase order header / line items before processing / passing to R/3. ( You will have some condition before pushing data to R/3. You can set this condition either on Time Base / Payload base...)
So here you will set correlation on Purchase order number..
Check out this blog for eg.
/people/daniel.graversen/blog/2006/09/07/using-a-bpm-to-collect-messages-for-a-set-interval-of-time
Hope this wull give you better idea...
Nilesh

Regarding BPM Syncronus process

Hello,
If suppose i want to design the syncronus process thru BPM.Then how can i design the Integration process steps for this scenario.
Is it possible to receive the response from reciever to sender by means of same BPM which already configured.
Thank you

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.

Sync to Asyn Message interface mapping

Hi all,
I have a scenario where source message interface is a sync interface and target is async. Can any body suggest if it is possible to map the request message structure of source to target (async) and the response need to have a fixed value.
Is it required to use BPM or is it possible without BPM. Can any body please suggest? Any help will be appreciated.
Thanks
-Kulwant

Hi,
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
We use Sync/Async bridge to establish the Sync communication between the Applications.
Normally the Technical adapters like File will not support the Sync communication to send back the Response to the Sender system from the File system.
So in this case we will use Sync/Async bridge to establish the connection using BPM.
Check these
Bridging the Sync-Async bridge with Fork (XI)
Use of Synchronous-Asynchronous Bridge to Integrate Synchronous and Asynchronous systems using ccBPM in SAP Xi
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:
- 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 -
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
Thanks,
Swathi

Async -Synch Bridge

Hi,
I need the process for Asynch -synch Bridge.
Scenario -> FileBAPI---SQL Server
Regards,
Jayasimha Jangam

Hi,
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
Reward points if helpful..
Regards,
Soumya

BpmPatternSyncAsyncBridge

Similar Messages

Maybe you are looking for