IDOC and HTTP adapter

[Former Member]

Dear All,

Could you tell me why IDOC and HTTP adapter don't need sender agreement. I know that they are on ABAP stack and the other adapters are on Java stack. Is that the only reason.

Regards,

Ashish

[bhavesh_kantilal · Accepted solution]

Ashish,

HTTP and IDoc adapters send the message directly to the Integration Engine of XI.

When the message comes from the adapter engine in the case of other adapters , the information in the sender agreement ( Sender Service, Message Interface , Interface Namespace) are used to fill up the Header of the message by the adapter engine and then the message is passed to the integration engine. In simple words, Sender Agreement is the means in which the message from the adapter engine to the integration engine is filled with all the appropriate details.

In case of HTTP adapters and Idoc adapters, the Sender Details are already available in the URL and so the message hits the integration engine directly and so you do not need a sender adapter and a sender agreement.

Regards

Bhavesh

Regards

Bhavesh

[STALANKI]

Ashish To answer your question right you have an Idoc adapter in ABAP stack and they are triggered using the RFC destination and we donot require to have a sender agreement as we will be able to read it from the client and system information from the control record of payload.You can see the sample code SAPLIDOC_ADAPTER_MB in the ABAP stack for you to understand what exactly happens and XI_GET_BS_SENDER_HTTPS_INFO FM can easily get the sender info that will be given in the URL you are posting.It automatically listens as it is pipeline URL and calls the API's in ABAP stack for performing the relevant steps.

[former_member192798]

Hi Ashish,

IDOC Adapters do not require Sender Communication Channel due to the fact that it does not run in J2EE AF framework. All IDOCs are tranferred to the Integration Server pipeline. The Sender System identifies itself at the Integration Server, with the fields SNDPOR and Client of the Control Record.

The same is the case with HTTP Adapter. No Sender Agreement or Sender Communication Channel is required, since the HTTP client connects directly to the Integration Server (ABAP), and the HTTP request should contain all relevant header information about the sender.

Regards.

Praveen

[Former Member]

Hi Ashish,

from http://help.sap.com/saphelp_nw04/helpdata/en/2b/d5653fd1d3b81ae10000000a114084/content.htm:

If you have selected the adapter type HTTP or IDoc, the direction of the communication channel is automatically set to Receiver. You do not need to configure inbound message processing when using either of these adapter types, because the relevant settings have already been made in the SAP Web Application Server configuration (see Sender Agreement).

Hope this help

Francesco

[Former Member]

Hi,

In case of HTTP adapter XI server has one in built service (on ABAP stack)(xi/adapter_plain) which listens to any HTTP requests coming to XI.

So whenever any request comes from HTTP sender it is directly listened by this service and then sent to Integration pipline,so we dont need any sender agreement.

Again in case of IDOC, idocs are sent directly to ABAP stack so no need of sender agreement.