Asynchronous and synchronous service operation in XI

[Former Member]

Hi all,

could anyone explain why it is important to define asynchronous/synchronous for service operation in XI? What are the rules for these?

Is asynchro/synchro only related to a service operation call? or the service operation itself?

Why is asynchronous a prefered XI-based service?

Does that have sth to do with consumer, or both consumer and provider?

Thank you and best regards

Jing

[Former Member · Accepted solution]

Hi Jing,

the decision, sync or asncy depends on

a) the adapter. Sample: If you have to use the IDOC Adapter, then it is async per definition

b) restarting aspects. You can't restart a asnyc process out of SXMB_MONI

c) usability: Sample: A user triggers a webService via XI to receive some information. This process should be sync because you don't want the user to wait

Regards Mario

[Former Member · Accepted solution]

Hi Mario,

a good point for Adapter. In our scenario we need an "adapter", but this is not available from SAP currently, so we use another solution to connect this with XI. What would be the consequence?

Thanks

Jing

[Former Member · Accepted solution]

Hi Jing,

it is NOT possible to send a message to XI without adapter.

Background: The adapter has to transform the incoming message in SOAP with payload (This is the dediceted format the XI works with).

OK, the easiest and fastest - I guess - is SOAP adapter.

Regards Mario

[Former Member · Accepted solution]

Hi Mario,

About Adapter it is another story. Till now we use a kind of converstiont tool to do the message mapping into XML and sent it into XI. But a special protocol adapter is still needed, and this is an external solution.

If the communication mode of an adapter would be on the transport level, which is on the protocol adapter side, is there any risk for the service operation?

regards

Jing

[Former Member]

Chen,

A distinction is made between synchronous and asynchronous communication for both imported interfaces and message interfaces. You define the mode of communication when you define an interface.

In the case of synchronous communication, a response message is expected from the receiver after a request has been sent. Once the request message has been sent, no further messages can be sent until the response to the request has arrived back at the sender system.

However, in asynchronous communication a (immediate) response is not expected. A sending process can send multiple messages to a receiver in a bundle and then continue executing the process.

Check this url for further help:

http://help.sap.com/saphelp_nw2004s/helpdata/en/4b/d26b3d32390968e10000000a114084/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/e8/8e2d4233c8db2ce10000000a1550b0/frameset.htm

Also check this weblogs;

/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi

https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]

/people/ravikumar.allampallam/blog/2005/02/17/bridging-the-sync-async-bridge-with-fork-xi

---Satish