A2A and B2B Scenarios

[Former Member]

Hello Friends,

Can any one explain what is A2A and B2B Scenarios and please explain what is asynchronous and synchronous communication.

Thnks&Rgds,

Dinesh

[Former Member · Accepted solution]

Hi Dinesh,

1. A2A integration involves configuring your system landscape, designing your integration scenarios, configuration of the scenarios, handling messages. In which you communicate at application level.

2. B2B Integration

Its something in which two business are integrated like: we develop scenario like legacy system to MDM using XI.

Now two businesses are communicating. See the link:

http://resources.ecommercetimes.com/search/keyword/ecommercetimes/Definition%20B2B/Definition%20B2B

3. Asynchronous communication:

Means you will send the data but no response will come from the receving end called Asynchronous communication. You will just send, disadv: your data may lost.

4. Synchronous:

Every time sender will send the data, receiver will give a response say acknowledgement to the sender that data received.

Adv: if data is not going to receiver it can be delivered again.

Rewrads if found helpful.

BR,

Alok Sharma

[Former Member]

thx !

[Former Member]

Dinesh,

A2A - application 2 application:

this is a integration like let's say, you have 2 systems in your company: ERP & accounting system. And you want to send data from ERP to acconting system. This happens inside your company, so it is sol called A2A.

B2B - business 2 business

Let's say, there are 2 companies, and they have a different systems, which need to be integrated. (Now I don't have any good example in my mind, but I think, you are getting the point.)

BUT:

in spite some scenarios in real life are B2B, they can be implemented in XI/PI like A2A - for example, you want to exchange some data via Web Services with your partner company, but you can implement it like a Business Service and not under a Party. So, it is a B2B scenario, but is implemented like A2A. (this is just an example, it shouldn't be done like that).

BUT:

Using Parties for B2B scenarios is essential in some cases, because it allows you to identify partners in some way - you can use identifiers. This is used for example with Seeburger adapters.

Peter

[Former Member]

Hi Dinesh

A2A: Communication possible within an Organization

B2B: Communication possible beyond the Organization

Asynchronous: Sending the data without waiting for response.

Synchronous: Sending the data with some response as well.

Reward some point if helpful

Adhir

[Former Member]

Thanks for your reply friends. I have rewarded with points

[Former Member]

Hi Dinesh!

asynchronous scenario:

let's say , you just want to send some data somewhere. So you send them asynchronously - you don't need a response message.

synchronous scenario:

let's say, you need some data from some system - you send a reqest message and you receive a data in a response message.

But: a synchronous scenario can be also the one, when you send data to some target systema and you request also a response about the processing.

So: sync scenario: reqeust/answer, async: just request

Peter