Sync-Async communication

Hi!
Is it possible to have a sync-async communication like this:
receive - open s/a bridge
send (async idoc with acknowledgement in return)
send - close s/a bridge?
or do I have to use a receive step after the send step in the middle?
I am trying to get a confirmation of Idoc posted to application and send this back to calling application, but I get a timeout error after the send (async idoc with acknowledgement) step...
Thanks!
regards Marianne

Hi
Thanks for you answer. I trust you here, but I have seen someone using this approach here on sdn.
Is it not possible to have the send step wait for acknowledgement and if ack is received then send a message back to the synchronous process. And also have a timeout exception that sends back a fault if acknowledgement is not received?
I know that some have been able to return to sync process wether the Idoc was posted correct or not...
regards Marianne

Similar Messages

Sync/Async communication in JMS adapter without BPM

Hi,
as of SP19 XI's JMS adapter offers this new feature for Sync/Async communication through JMS Adapter modules instead of using a BPE.
Now I would be interested to know if anybody has already successfully used this feature especially using WebSphere MQ as a JMS Provider (preferredly in the mode JMS Compliant: WebSphere MQ (non-JMS)).
I experienced some issues with the XI Message ID being used as the JMS Correlation ID which is then mapped to the MQ Correlation ID being truncated after 24 characters. So I don't exactly know whether this is due to wrong setup or some general issues with this messaging system.
Please let me know if you have any experiences at all with this new feature (please do not just post links to the following blogs, which I have thoroughly studied as well as the How-to Guide concerning this topic)
/people/venkataramanan.parameswaran/blog/2007/01/18/syncasync-communication-in-jms-adapter-without-bpm-sp19
/people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
thanks & regards,
Peter

Hi Peter,
we working on the same Problem. Using IBM Websphere MQ as JMS Provider for the new feature: sync/async bridge without BPE.
we switched on a high level trace for the adapter framework and saw a problem in the receiving Object of the JMS correlation id. The notify bean receives the JMS correlationid in hex format. so the beans have two different correlations, which could not find together.
did you have any solution to get this new feature works with IBM Websphere ?
thanks
joachim

Sync/Async communication in JMS

HI all,
i configured scenario as mentioned in the blog
"Sync/Async communication in JMS adapter without BPM (SP19)
Venkataramanan Parameswaran".
now i am working on PI 7.0
but i am getting the error as fallows.....
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Object not found in lookup of
RequestOnewayBean.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
can anybody tell me why it is?
Thanks,
Kumar

Please refer these links
Sync/Async scenarios without BPM
Async/Sync Communication using JMS adapter without BPM (SP 19)
http://help.sap.com/saphelp_nw70/helpdata/en/45/20d1dec20a0732e10000000a155369/frameset.htm

Monitoring inbound processing and Sync/ Async communication on PI7.11

Hi All,
I am new to PI. We have following two requirements to be done on PI 7.11
1)     Monitoring inbound processing (Txn Code SWF_INB_MON)
2)     Monitoring Sync/ Async communication (Txn Code SXMS_SAMON)
Kindly let me know how should I proceed or what document should I follow or any scenario is to be configured.

Hi,
    1. Start inbound processing monitoring with transaction SWF_INB_MON or SWF_INB_ADM.
           Note that you require administrator authorization for transaction SWF_INB_ADM
    2. You can monitor the throughput of the inbound processing either on the basis of individual process system or system-wide. In this way you can display the throughput figures in any discrete time range, right down to seconds. A similar display for message packages allows you to monitor inbound processing with the same detail."
     3. You can display runtime information about individual messages, for example, the total runtime of a message in inbound processing or just the runtime of a specific section of the inbound processing. For monitoring individual messages click on "Display Message Packages".
regards,
ganesh.

Sync/Async communication with JMS Receiver

Hi all,
I am working on one Sync/Async model without BPM. Sender is RFC which is expecting some response, but we know receiver jms doesnt support response message directly. For this i used modules provided by SAP.
While developing interface i used below objects.
One Outbound Synchronous interface--> for Sender RFC channel
Inbound Synchronous Interface----->for Receiver JMS Channel
outbound asynchronous interface--->for Sender JMS channel
one request mapping and one response mapping
Operational mapping between outbound Synchronous to inbound synchronous.
ID Objects:
2 sender agreements: one with sender jms channel
one with sender rfc channel
1 receiver agreement: with jms receiver channel
1 receiver determination
1 interface determination
In receiver jms and sender jms channels i used modules as specified in the document http://help.sap.com/saphelp_nw04/helpdata/EN/45/20d2b4c20a0732e10000000a155369/content.htm
But my interface is not working end to end successfully.
Please confirm below points
1)do i need to have other external application put response message to response queue or will the MQ automatically generates the response message and put into response queue
2)In receiver jms channel is it ok if i will put response queue(Q2) name in the field JMS ReplyTo Queue Name or do i need to put in the form queue://<ReplyToQMgr>/<ReplyToQ>
3). what is the format of data type for asynchronous outbound interface which i used for sender agreement of jms sender channel.
4). Do i need to do any other special settings at MQ settings in MQ server.
Note: i am using PI7.1 and i selected the option JMS-compliant for target client in jms channels.
Thanks,
Madhu
Edited by: Madhusudana Reddy on Nov 4, 2009 9:38 AM

1)do i need to have other external application put response message to response queue or will the MQ automatically generates the response message and put into response queue
The following information is available in SAP note-
Message correlation implies correlating a response message with a request message. With respect to the JMS adapter, this means that you sent have sent a message through a JMS receiver channel to some JMS queue (say queueA) , some external application processes this message and puts the response onto another JMS queue(say queueB) which is then picked up by a JMS sender channel. You need to relate this response message with the original request message.
In the simple case, for all JMS compliant providers this can be done in a straightforward manner:
a) In the JMS receiver channel configuration, set the JMSCorrelationID to the XIMessageID. (or some other XI header which is applicable)
b) Ensure that your external application does not change the value of the JMSCorrelation
c) In the JMS sender channel configuration, set the XIConversationID to the JMSCorrelationID
d) The XIConversationID header of the response XI message now contains the XIMessageID of the request XI message.
For some providers such as Websphere MQ in legacy/native mode this is not so straightforward.
Do i need to do any other special settings at MQ settings in MQ server.
If your using Websphere MQ, refer que#4 in sap note :1086303
Edited by: nagarjuna _s on Nov 4, 2009 11:02 AM

Sync-Async Gotchaa

Hi Friends, 
I am in a problem, I have one jpd published as a webservice to a poral [synchronous] client. This jpd is asynchronous,meaning it have separate client request and client response node, but the same jpd is calling one more process control[async again] to do the dirty work of tranforming incoming request and then sending to legacy system using JMS control[async activity]. The question is, can we call the outer jpd [that is published as a web-service] synchronously from a portal page. I seen the weblogic docs they say to make sync-async wsdl file and define client callback method,I tried it but it doesn't work. I think my design fall in some limitation that the doc is talking about as in between pair of client request and client response node I have another client request to the process control [for transforming and sendng receiving message]. 
 Is there anyother way to make it work? 
 Did anyone got the same problem before? 
 Guys, you need to help me in this pls I already tried lots of permutation and combination to arrive at this design so pls don't ask me to change this now. :( 
Cheers, 
Shailesh

Hi Rohini,
Sync/async communication enables a synchronous sender system to communicate with a receiver system that cannot process synchronous messages.
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.
There is an example of the Sync/Async Bridge in th SWCV: SAP BASIS.
Namespace: http://sap.com/xi/XI/System/Patterns
Go through this link to get a good idea as to how to <a href="http://help.sap.com/saphelp_nw04/helpdata/en/43/65d4dab39b0398e10000000a1553f6/frameset.htm">Define Sync/Async Communication</a>
This blog also should give you some idea...
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1403 [original link is broken]
Also go through these links:
http://help.sap.com/saphelp_nw04/helpdata/en/83/d2a84028c9e469e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c4/dc06418752ef6fe10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f9/66bf40ad090366e10000000a1550b0/RN_XI_DE_neu.pdf
I hope it helps.
Regards,
Abhy
Message was edited by: Abhy Thomas

Sync/Async bridge

Hey
My task is to have an Idoc sent to a Web Service. I have heard that this can be solved using a sync/async bridge in BPM, but from what I can read (help.sap.com) it always say that the first receive step is from a synchronous application. My question is then: Can I use the sync/async bridge to call a web service - i.e. changing from asynchronous (Idoc) to synchronous (WS call)?
Anyone knows a blog that shows some good examples of sync/async communication? I have read the inital blogs on BPM, but not found anyone good at async/sync communiation...
thanks a lot!
regards Marianne

Hi,
If you want to receive the response from Webservice means you need to use BPM here.
Otherwise no need of any BPM,
That too if u want to response from WS also u dont require any Sync/Async Step here.
You can configure the BPM with Async receive-Sync Send-Async Send
REgards
Seshagiri

Need help with scenario BPM Http-RFC Sync/async bridge

hi all!
i've got the following scenario: HTTP-BPM(XI)-RFC synchronous both of them. for that, i'm using S/A bridge in the BPM, but i'm getting the error 'Timeout condition of pipeline reached'. i think the problem is that the process gets lost in the sync/async communication, because in the trace level shows CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV" and after that every message are 'wait time starting'.
don't know the reason of the error. Maybe I missed something to configure?
the BPM is like this:
Receiver(Open Sync/Async bridge) -> Transformation (mapping from http request to RFC request) -> SyncSend (RFC request and response) -> Transformation (mapping from rfc response to http response) -> Send (Close S/A Bridge)
the IR is configured like this:
Message Types u2013 External Definitions u2013 Imported Objects
mt_cxml_request -> contains xsd of xcml request template.
mt_cxml_response -> contains xsd of xcml response template.
zintegracion_pedidos -> imported RFC from R/3
zintegracion_pedidos.response -> imported RFC from R/3
Message Interfaces
mi_cxml_request_async_abs
mi_cxml_request_sync_abs
mi_cxml_request_sync_out
mi_xcml_response_async
mi_rfc_request_asyn_abs
mi_rfc_request_sync_abs
mi_rfc_request_sync_in
mi_rfc_response_async_abs
Message Mappings
mm_cxml_request_to_rfc_request -> mapping from http request (cxml) to rfc request.
mm_rfc_response_to_cxml_response -> mapping from rfc response to http response (cxml).
Interface Mappings
im_cxml_request_async_abs_to_rfc_request_async_abs
im_rfc_response_async_abs_to_cxml_response_async_abs
and the ID is configured like this:
Business system DES -> created business system for RFC adapter with interface mi_rfc_request_sync_in as receiver. Comunication channel u2018RFC Receiveru2019
Businnes service VW -> created businnes service for HTTP adapter with interface mi_cxml_request_sync_out as sender. Comunication channel u2018HTTP Senderu2019
Receiver Determination
two receiver determinations. One for BPM and the other one for RFC(R/3):
|VW| mi_cxml_request_sync_out:
|BPM_PO| mi_rfc_request_sync_abs:
Interface Determination
two interface determinations:
|VW| mi_cxml_request_sync_out | | BPM_PO:
|BPM_PO| mi_rfc_request_sync_abs | * | * :
Sender Agreement
VW
mi_cxml_request_sync_out
Receiver Agreement
|BPM_PO| |DES| mi_rfc_request_sync_in

hi all,
i've removed the transformations from the BPM, and i've created:
in IR:
- interface mapping: im_xcml_request_to_rfc_request_sync_abs
                                source interface: mi_cxml_request-sync_abs
                                target interface: mi_rfc_request_sync_abs
in ID:
- receiver determination: |VW| mi_cxml_request_sync_abs
                                  sender service: VW
                                  interface: mi_cxml_request_sync_abs
                                  receiver: DES
                                  interface mapping:im_xcml_request_to_rfc_request_sync_abs
- interface determination: |VW| mi_cxml_erquest_sync_abs ||
                                     sender service: VW
                                     interface: mi_cxml_request_sync_abs
                                     inbound interface: mi_rfc_request_sync_abs
                                     interface mapping: im_xcml_request_to_rfc_request_sync_abs
- receiver agreement: |VW| |DES| mi_rfc_request_sync_abs
                               sender service: VW
                               receiver service: DES
                               receiver interface: mi_rfc_request_sync_abs
not sure these are the steps i had to do for mapping xml to rfc. but the result is the same error as before, the timeout.
i couldn't test with RTW because i'm getting an error 401 unauthorized.
i'd do it without BPM but the issue is that i wanted to add another step that would be to send the response from rfc to mail too once i got this BPM running. i mean, the response from RFC would be sent to http response and mail both.
the only way i can imagine to do it is with BPM but i'm really fed up with it.
thank u very much folks

Sync/Async bridge timeout?

Hi,
a ccBPM process produces some timeouts during the last week and i dont know why. The process produces the timeout in the third step:
Step 1: Receive synchronous message via HTTP, open sync/async bridge
Step 2: Mapping
STep 3: Send back response for synchronous message and close sync/async bridge
in step 3 the timeout occurs (we have 1 minute configured for ccBMP processes):
<Trace level="1" type="B" name="SA_COMM">
<Trace level="1" type="T">Start Sync/Async Communication</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:51:50Z UTC Starting Processing</Trace>
<Trace level="1" type="T">Pipeline Timeout: 2008-10-19 08:52:50 UTC</Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">Message type BEST EFFORT. -> No determination</Trace>
<Trace level="1" type="T">Set interface action INIT into MAST</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:51:50Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:51:51Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:51:52Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:51:53Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:51:54Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:51:55Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:51:56Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:51:57Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:51:58Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:51:59Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:00Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:01Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:02Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:03Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:04Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:05Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:06Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:07Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:08Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:09Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:10Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:11Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:12Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:13Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:14Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:15Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:16Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:17Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:18Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:19Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:20Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:21Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:22Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:23Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:24Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:25Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:26Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:27Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:28Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:29Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:30Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:31Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:32Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:33Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:34Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:35Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:36Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:37Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:38Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:39Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:40Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:41Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:42Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:43Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:44Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:45Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:46Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:47Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:48Z UTC Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-10-19T08:52:49Z UTC Wait time starting.</Trace>
<Trace level="1" type="System_Error">Pipeline Timeout at 2008-10-19 08:52:50,3247440 UTC</Trace>
</Trace>
</Trace>
Does anyone know why this happens?
Does step 3 wait until the sender system releases the synchronous message? So only when step 3 is done, the process will be processed asynchronous?
regards,
MS

hi,
[Re: BPM SA bridge timeout;
might be some help.
Siddhesh

Sync/Async without BPM

Hello Experts,
Can you please post your experiences on this issue.
I am working on this SYNC/ASYNC scenario.
REQUEST
ABAP Proxy -> PI -> JMS receiver adatper -> IBM MQ
RESPONSE
IBM MQ --> JMS Sender adapter -> JMS receiver adapter
Here it is going into a loop. The JMS sender adapter sends response back to the JMS receiver, but the JMS receiver thinks it is from the source sender SAP and sends it back toe IBM MQ, and this goes into a loop. Meaning, MQ receives this as a new request and proceses it and sends back a new response going into a loop.
The reponse is sent back to the receiver, which is waiting. How does the JMS receiver know the message is a response not from Request. Please post your experiences.
I need to know based on help.sap.com-http://help.sap.com/saphelp_nw04/helpdata/en/45/20d2b4c20a0732e10000000a155369/content.htm, the correct Receiver Agreements, and Receiver determinations for this scenario.
Thanks for your answers.
-praveen

Hi Praveen,
This looks straightforward if you are using the sync-async bridge modules.
Sync/Async Bridge in the Receiver JMS Adapter
http://help.sap.com/saphelp_tm70/helpdata/en/45/20d2b4c20a0732e10000000a155369/frameset.htm
Sync/Async communication in JMS adapter without BPM
/people/venkataramanan.parameswaran/blog/2007/01/18/syncasync-communication-in-jms-adapter-without-bpm-sp19
Basically, in one configuration, you use RequestOnewayBean to send a request to your JMS receiver and then wait for a response at WaitResponeBean. In another configuration, where you are sending back a response, you use NotifyResponeBean to send this response back to the waiting call.
Regards, Yza

Sync - Async Bridge example

Hello,
Pls provide Sync - Async Bridge example document.
Regards

HI
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
The Integration Server receives 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.
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 BPE 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.
This blog also should give you some idea...
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Also go through these links:
http://help.sap.com/saphelp_nw04/helpdata/en/83/d2a84028c9e469e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c4/dc06418752ef6fe10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f9/66bf40ad090366e10000000a1550b0/RN_XI_DE_neu.pdf

Regd NWBPM Sync/Async Bridge

Hi,
I have a synchronous to Asynchronous interface. Customer sending the data through SOAP and he is expecting the response. From PI we are sending the data to ECC through IDoc.
I checked couple of blogs but those are related to Sync-to-Async (Async request and Async Response at target side). Can you please help me how to achieve this.
I checked below links
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80f96dbf-adca-3010-ffb5-daf2d1f0e276?QuickLink=index&…
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50be5f78-c84d-3010-32ac-ea68b7202932?QuickLink=index&…
Thank you.
Regards,
Venkat

Hi Rohini,
Sync/async communication enables a synchronous sender system to communicate with a receiver system that cannot process synchronous messages.
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.
There is an example of the Sync/Async Bridge in th SWCV: SAP BASIS.
Namespace: http://sap.com/xi/XI/System/Patterns
Go through this link to get a good idea as to how to <a href="http://help.sap.com/saphelp_nw04/helpdata/en/43/65d4dab39b0398e10000000a1553f6/frameset.htm">Define Sync/Async Communication</a>
This blog also should give you some idea...
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1403 [original link is broken]
Also go through these links:
http://help.sap.com/saphelp_nw04/helpdata/en/83/d2a84028c9e469e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c4/dc06418752ef6fe10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f9/66bf40ad090366e10000000a1550b0/RN_XI_DE_neu.pdf
I hope it helps.
Regards,
Abhy
Message was edited by: Abhy Thomas

Need help with Sync/Async BPM Scenario

I have an R/3 RFC -> XI -> HTTP (to vendor A) scenario that is working fine. It is a totally synchronous call event. The Integration Directory pieces sit in a scenario named HotkeyOutbound.
Now I need to create a process for RFC -> XI -> HTTP (to vendor Panduit). The R/3 RFC is the same sender, but vendor Panduit only supports an asynchronous HTTP connection. I followed the Sriram Vasudevan weblog on Sync/Async Bridge and created my BPM. I am stuck on trying to determine what to set up in the Integration Directory.
First off, should I be able to use the same HotkeyOutbound scenario as with vendor A so all hotkey stuff can stay together? Or do I have to create a new scenario with a copy of the R/3 business system for the sender? I moved forward with a new scenario (PanduitHotkeyOutbound).
I also need to know how many config Agreements and Determinations to use. The image at http://webpages.charter.net/kpwendel/keith1.html shows what I have so far. Which are not needed? What is missing?
And I tried setting up an HTTP communication channel for outbound async to vendor Panduit and another for inbound async from vendor Panduit. XI won't let me set up a sender HTTP channel. Why not?
Thank you in advance.

I have yet to figure this out, and probably need to go back to my Integration Repository setup since my problems may start there. This screenshot shows my Repository objects.
http://webpages.charter.net/kpwendel/intProcess.jpg
HELP! These are the steps I took, with questions embedded.
(1) Created data type and message type for xml document (note that same format is used for request and reply).
(2) Created PANRequestAbstractInterfaceSync (abstract and sync) for first part of Integration Process. Should the input message be the RFC or XML message type?
(3) Created PANRequestAbstractInterfaceAsync (abstract and async) for 2nd part of Integration Process.
(4) Created PANResponseToBPM_MessageInterface (outbound async) for interface back into XI from partner. Is this needed?
(5) Created PANHotkeySync_to_Async_IntProc Integration Process to handle sync to async bridge.
- Wondering why PANRequestAbstractInterfaceAsync is the only message interface available when I make container object (PANMessage)?
(6) Created two Message Mappings to handle RFC data to XML mappings (outbound RFC-> XML and inbound XML -> RFC).
(7) Created Interface Mapping that includes both the Request and Response message mapping programs from step six. Source is the RFC and Target is PANRequestAbstractInterfaceSync.
- Do I need another interface mapping with Source being PANRequestAbstractInterfaceAsync and Target being the RFC?
Link to these steps and app diagram:
http://webpages.charter.net/kpwendel/PAN_Hotkey_Diagram.jpg
Thank you very much for your time.

Sync/Async bridge via JMS with FAULT messages

Hello all, 
I set up a sync/async bridge scenario with using of JMS communication channel (SAP - JMSReceiverCC - JMSServer and application - JMSSenderCC - SAP). The normal communication works fine. 
But what we can not solve is the Fault Message handling. If there is a application error behind the JMS, a fault message is generated instead of proper application response and sent back to XI. Without any additional setup of JMS Sender CC the processing of the message ends with "MAPPING - EXCEPTION_DURING_EXECUTE", because normal "response mapping" is executed instead of "fault message mapping". This is correct behavior without any discussion. 
[SAPhelp|http://help.sap.com/saphelp_nw70/helpdata/en/45/202845de34072ce10000000a155369/frameset.htm] says that there are 2 module parameters to be set : fault, faultNamespace. The description is rather vague, so let's see, what the "NotifyResponseBean" does, when parameters fault/faultNamespace are filled: 
<pre>if(fault != null && faultNamespace != null)
if(faultNamespace.equals("http://sap.com/xi/XI/System"))
 ((XIMessage)message1).setMessageClass(MessageClass.SYSTEM_ERROR);
 ((XIMessage)message1).setError(fault, "no additional information");
} else
 ((XIMessage)message1).setMessageClass(MessageClass.APPLICATION_ERROR);
 ErrorInfo errorinfo = message1.createErrorInfo();
 errorinfo.setAttribute("ApplicationFaultInterface", fault);
 errorinfo.setAttribute("ApplicationFaultInterfaceNamespace", faultNamespace);
 errorinfo.setAttribute("ErrorCode", fault);
 errorinfo.setAttribute("AdditionalErrorText", "no additional information");
 message1.setErrorInfo(errorinfo);
} else
((XIMessage)message1).setMessageClass(MessageClass.APPLICATION_RESPONSE);
}</pre> 
The code is pretty straight forward so one could assume, that it's the name and namespace of inbound synchronnous message interface what is supposed to be filled in the values of each parameter. And from that kind of information SAP XI can evolve how to handle the response, actually the fault. 
Unfortunatelly the real situation is different - every time the fault message is generated and sent back to XI, the response is correctly corelated with the request message, "WaitResponseBean" and "NotifyResponseBean" are finished correctly and the processing crashes in messaging class on following exception: 
java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:592) at
com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at
com.sap.aii.adapter.xi.ms.XIMessage.updateHeaders(XIMessage.java:4244) at
com.sap.aii.adapter.xi.ms.XIMessage.getTransportHeaders(XIMessage.java:570) at
com.sap.aii.af.ra.ms.impl.ServerConnectionImpl.request(ServerConnectionImpl.java:212) at
com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:337) at ...
 
Is there anyone, who can put more light on JMS sync/async bridge fault handling ???
 
Thank you ... 
Regards
Tomas

Hello again,
I proceed in investigation little more, but the main problem has not been solved. I found that the problem is not even in WaitResponseBean (placed in JMCReceiverCC). This bean is woken up properly on base of proper CorrelationID. See the log:
2009-10-15 11:00:33 Success WRB: entering WaitResponseBean
2009-10-15 11:00:33 Success WRB: retrieving the message for f1ea1fc0-b96d-11de-9b68-00144f4acd86 ...
2009-10-15 11:00:46 Success WRB: retrieved the message: ApplicationError
2009-10-15 11:00:46 Success WRB: leaving WaitResponseBean
I think, that the problem is somewhere within main messaging functionality. I suppose that on base of exception message:
com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at
which is generated.
Any ideas or comments ?
Thank you in advance.
Regards
Tomas

Sync Async without BPM and JMS.

Hi Guys,
Searched SDN a lot but in vain...
i have soap(Sync) to File(Async) synario...Soap response can have like this "PI system received message"..
How can i, with out BPM?
Thanks
Prabhakar

i have soap(Sync) to File(Async) synario...Soap response can have like this "PI system received message"..
If the SOAP is mandatorily working in SYNC mode then the above solution wont work (SOAP --> XI --> SOAP)....this will be treated as two different calls for the SOAP and the solution would have worked for ASYNC flow.
Why do you need PI system received message .... if i send a SOAP message and if it is successfully send from the SOAP application then I would get a 200 OK message which would indicate that everything was fine till sending the message to the XI/ PI system.
If SYNC communication is needed then implement a BPM with a SYNC-ASYNC bridge.
Regards,
Abhishek.

Sync-Async communication

Similar Messages

Maybe you are looking for