Start of Content Area

Function documentation Configuring the Sender Plain HTTP Adapter  Locate the document in its SAP Library structure


You communicate with the plain HTTP inbound channel of the Integration Engine using an HTTP address. The HTTP body is used as the payload for the message. The payload does not contain an envelope with control data for the message you want to create. You must code the control data in the HTTP address as parameters; these parameters are obligatory to be able to generate a message.


If you want to specify security checks or adapter-specific attributes in the message header for the plain HTTP inbound channel, create a communication channel for the party and service in the Integration Directory. You can configure the security level there. See below under Activities.


Queries entering the plain HTTP adapter must have the following syntax:


The query string contains the following data:

      Sender namespace ?namespace=<namespace>

      Sender interface &interface=<interface>

These details define the sender interface.

      Sender service &service=<service>

Specifies the sender service.

      Sender party (optional) &party=<party>

      Sender agency (optional) &agency=<agency>

      Sender scheme (optional) &scheme=<scheme>

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



      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.

      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.

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

This 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.


Security Check for Inbound Messages

If you want to specify an increased HTTP security level for inbound messages, perform the following steps:

Create an adapter of type HTTP and Sender for the plain HTTP inbound channel in the communication channel in the Integration Directory.

The Transport Protocol, Message Protocol, and Adapter Engine are predefined.

      Under Security Check for Inbound Messages, you can specify which HTTP Security Level is to be assumed for incoming messages. You can choose from the following security levels:

       HTTP (default value)

       HTTPS without client authentication

       HTTPS with client authentication

Create a corresponding sender agreements.

See also: SAP Security Guide XI, HTTP and SSL, under Enforcing HTTP Security for Incoming Messages

Adapter-Specific Message Attributes

      To store adapter attributes in the message header of the XI message, choose Set Adapter-Specific Message Attributes.

      To use the non-XI-specific HTTP Header Fields or URL Parameters, set the respective indicator. You can then store the following attributes and their values in the XI message header:


Technical Name

Field 1, …, 6

HeaderFieldOne, .... HeaderFieldSix

Parameter 1, …, 6

URLParamOne, …, URLParamSix

The names of the fields and parameters must correspond to the names of the fields and parameters that are also to be sent by an HTTP request.

      To evaluate adapter attributes in the synchronous response, choose HTTP Header Fields (Synchronous Response) and enter the fields in the fields Field 1 to Field 6.

The fields are recorded in the HTTP response under the names you enter here.

The technical names of the fields are HeaderFieldOne,...,HeaderFieldSix.


The attribute namespace for the adapter is








End of Content Area