Showing results for 
Search instead for 
Did you mean: 

http adapter

Former Member
0 Kudos


how will the sender external system will connect to xi when we use http adapter since we dont create sender communication channel.



Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Raghu,

Incase of HTTP adapter ..

The message is sent using HTTP directly to XI integration engine . That is the reason no adapter is required.

Just to give you an example..

File Adapter reads the file and then sends it to Integration Engine. So if you send the file directly to IE you wont need a adapter..Right?



Answers (3)

Answers (3)

Former Member
0 Kudos

hi Raghu,

you dont require sender agreement or sender communication channel for HTTP adapter since the HTTP client connects to the Integration server(ABAP Stack) directly and the HTTP request should contain all relevant header information about the sender

reward if helpful.



Active Contributor
0 Kudos

Bcoz HTTP adapter is based on ABAP stack and lies directly on the Integration Server. The integration engine therefore readily understands the format of data send by the sender HTTP. And hence the sender communication channel and sender agreement is not required.



Former Member
0 Kudos

Hi Raghu,

No sender agreement or sender communication channel is required.,since HTTP client connects to the integration server directly and the HTTP request should contain all relevant information about sender.

Hope this is helpful.


Sidhvin Mada

Former Member
0 Kudos


If you have seen the HTTP information

This is the URL of HTTP which has all the below information.


The query string contains the following data:

&#9679; Sender namespace ?namespace=<namespace>

&#9679; Sender interface &interface=<interface>

These details define the sender interface.

&#9679; Sender service &service=<service>

Specifies the sender service.

&#9679; Sender party (optional) &party=<party>

&#9679; Sender agency (optional) &agency=

&#9679; Sender scheme (optional) &scheme=<scheme>

If you do not enter values for agency and scheme, the following default values are used:

&#9675; agency=

&#9675; scheme=XIParty

&#9679; Quality of Service (BE, EO, or EOIO) (optional) &qos=<EO|BE|EOIO>

In the case of BE, the client is sent the end status for the processing; in the case of EO and EOIO, processing occurs asynchronously and the client only receives a confirmation of receipt with HTTP status ‘200’.

If a value is not specified for this parameter, it is given the default value BE.

&#9679; Message ID (optional) &msgguid=<msgguid>

For EO and EOIO, the message ID can be passed for Exactly Once processing using the parameter msgguid. If an ID is used more than once, an HTTP status ‘500’ is returned from the server.

The message ID is 32 characters long and must only comprise the characters 0 to 9 and A to F. It is persisted and can therefore be checked for duplication. If the HTTP client (the sender system) cannot provide a message ID, the plain HTTP adapter generates a message ID and forwards it to the application through the Integration Engine. You can then carry out a duplication check in the application at document level, for example, by using the order number.

&#9679; Queue ID (only if quality of service is EOIO) (optional) &queueid=<queueid>

The queue ID can have a maximum of 16 characters. If the first eight characters contain 'SAP_ALE_', this is removed since this value is reserved by SAP and is used internally.

So no need to have the sender adaper for HTTP.

Testing part can be done through the test message tab through the RWB component monitoring tab.

or u need to use the HTTP client for the same.

This link gives you a sample HTML code to create HTTP Client: