Why IDOC and HTTP doesnu0092t have a sender agreement,

[Former Member]

Why IDOC and HTTP doesn’t have a sender agreement,

[vikas_agarwal]

Hi Manoj,

The IDOC and HTTP Adapter resides directly on the Integration Server (ABAP Stack).

SO the message will be automatically put into XI pipeline.So sender agreement is not required.

But we can create them and sometimes we need too

(if we want to use Adapter-Specific Message Attributes

for the http adapter for example)

check

section Obligatory Sender Agreements

http://help.sap.com/saphelp_nw04/helpdata/en/b1/f29e7a56e18a439984a3c6630951d2/content.htm

regards

Vikas

[Former Member]

Hi manoj ,

The straight answer is IDOC and HTTP adapter are in ABAP stack.And for adaptors which are in ABAP stack ..u need not create the communication channel..these are already linked to Integration Engine.

In sender agreement we give sender communication channel right....

but since no communication channel is required for IDoc and HTTP so we dont need sender agreement...

Tha ABAP stack consists of the Integration Server which in turn contains your Integration Engine and Business Process Engine.

The J2EE stack contains the Adapter Engine and your IR and ID run on the J2EE engine.

Ever wondered how and where the XI pipeline gets executed? It happens in the ABAP stack.

All messsages picked by the Adapter Framework running on the J2EE engine are passed to the Integration Engine, which does the routing. The mapping program again gets executed on the Java stack and the rest of the pipeline servies are executed again on the ABAP stack and so on.

Take a look at the XI overview doc to understand this better,

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a3d3c390-0201-0010-c490-bd8...

Regards

Biplab

<i>note:reward with points if helpfull</i>

[Former Member]

>>Why IDOC and HTTP doesn’t have a sender agreement,

The sender HTTP-adapter is an ICF service on the Integration Server. No Sender agreement or sender communication channel is required, since the HTTP client connects to the Integration Server (ABAP) directly, and the HTTP request should contain all relevant header information about the server.

The IDOC Adapter is implemented in ABAP and resides directly on the Integration Server. You cannot define a sender IDOC channel in directory due to the fact that the IDOC adapter does not run in J2EE Application Framework but is an built-in adapter

Regards

[Former Member]

Hey,

Both IDOC and HTTP adapter sit on the ABAP stack so when the message is triggered from the source application it directly pushes them on the abap stack. That is the reason we don't have sender agreement or communication channel.

Cheers,

*RAJ*

[prateek]

IDOC and HTTP r the only adapters residing on ABAP stack and direclty on the Integration Server.

Purpose of sender agreement is to communicate with Integration Server. Since these adapters and IS both resides on ABAP stack, for their communication no agreement is required.

Regards,

Prateek

[Former Member]

Hi

Go through this

we can create them and sometimes we need too

(if we want to use Adapter-Specific Message Attributes

for the http adapter for example)

check

section Obligatory Sender Agreements

http://help.sap.com/saphelp_nw04/helpdata/en/b1/f29e7a56e18a439984a3c6630951d2/content.htm

read the link above to understand why we use

sender agreements

Additionally

for IDOC

http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm

for http -

http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm

Thanks