Show TOC

Configuring the Sender SOAP AdapterLocate this document in the navigation structure


Configure the sender SOAP adapter to send content from remote clients or Web service servers to the Integration Server/Partner Connectivity Kit (PCK).

  • If you want to handle acknowledgments, you must create a HTTP destination in the SAP NetWeaver Administrator (NWA)

    For more information, see Maintaining HTTP Destinations

  1. Select the Transport Protocol as HTTP .

  2. If you want to send information from a remote client or a Web service server to the Integration Server/PCK, then select the Message Protocol as SOAP 1.1 . If you want to send an XI message from a legacy system or AAE through the SOAP Adapter, then select the Message Protocol as XI 3.0 .

  3. Select the Adapter Engine on the Integration Server, or select a non-centrally installed Adapter Engine.

    This selection is not available in the PCK.

1. Define Inbound Security Checks

From the HTTP Security level drop-down, select the security level for the inbound message.

For more information, see the SAP NetWeaver Process Integration Security Guide.


You can only define inbound security checks for the SOAP 1.1 message protocol.

2. Define Security Parameters

  1. If you want to make additional settings for security in the relevant sender agreement on the Integration Server or in the PCK, select Select Security Profile .

    For more information, see SAP NetWeaver Library under Start of the navigation path Function-Oriented View Next navigation step Process Integration Next navigation step Integration Directory Next navigation step Defining Sender Agreements Next navigation step Security Settings for the Sender SOAP Adapter End of the navigation path.


    If you select Security Profile , there must be exactly one sender agreement for the defined communication channel.

  2. Under Security Profile select:

    • Web Services Security

    • S/MIME


    For XI 3.0 message protocol, you can use only web services security as the security profile.

  3. Specify the Persist Duration for messages in days, hours, minutes, and seconds.

3. Specify XI Bulk Message Handling

  1. Select the Message Protocol as XI 3.0 .

  2. Select the Split XI bulk Messages check-box if you want to:

    • Split the incoming bulk message into individual messages

    • Use module chain configurations for the messages that are split

4. Define Conversion Parameters

  1. If the adapter is to expect a message without a SOAP envelope, select Use No SOAP Envelope .

    In addition specify nosoap=true in the URL.

    The adapter puts the whole message in the XI payload.

  2. To include the header of the Web service message in the XI message, select Keep Headers .

  3. To include attachments of the Web service message in the XI message, select Keep Attachments .

  4. If the XI header information is to be included in the encoded string, select Use Encoded Headers .

  5. If the XI header information is to be included in a query string, select Use Query String .


Conversion Parameters are available only if you select the Message Protocol as SOAP 1.1 .

5. Define Processing Parameters

Under Quality of Service , specify how the message is to be processed by the Integration Engine/PCK.

For Exactly Once In Order Quality of Service enter the Queue Name .

For more information, see Quality of Service and

Ensuring Exactly Once in the Sender Adapter

6. Define Adapter-Specific Message Properties

  1. Select the Advanced tab page.

  2. To save adapter-specific attributes in the message header of the XI message, select Set Adapter-Specific Message Properties .

    • The following attributes are added to the XI message header if the sender makes them available, and if you select Variable Transport Binding .

      • Remote User : (technical name: SRemoteUser )

      • Remote Host : (technical name: SRemoteHost )

      • SOAP Action (technical name: SHeaderSOAPACTION )

      To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:

      • Variable Header : (technical name: XHeaderName1 )

      • Variable Header : (technical name: XHeaderName2 )

      • Variable Header : (technical name: XHeaderName3 )

      The names of the fields and parameters must correspond to the names of the fields and parameters that also go through the HTTP request.

    The attribute namespace for the adapter is .

7. Define the Adapter Status

Set the adapter to Active to enable messages to be exchanged.


Adapter Status is available only if you select the Message Protocol as SOAP 1.1 .

8. Define Acknowledgement Destinations


You can define acknowledgement destinations for external entities that communicate with AAE using SOAP XI adapter. Some of the examples of such entities are ABAP proxy applications, integration servers, and Partner Connectivity Kit (PCK).

  1. From the Message Protocol dropdown listbox, choose XI 3.0 .

  2. Choose the Acknowledgement Handling tab.

  3. In the HTTP destination (from NWA) field, specify the HTTP destination that you have created in the SAP NetWeaver Administrator.


You have configured the SOAP sender adapter. You can trigger a call to the sender SOAP adapter using either of the following URLs. However, SAP recommends you to use the second option.

  • http:// <host name> : <port name> /XISOAPAdapter/MessageServlet?channel= <party name> : <service name> : <channel name> . If you have not created a party, enter channel=: <service name> : <channel name>

  • http:// <host name> : <port name> /XISOAPAdapter/MessageServlet?senderParty= <name of the sender party> &senderService= <name of the sender service> &interface= <name of the interface> &receiverParty= <name of the receiver party> &receiverService= <name of the receiver service> &interfaceNamespace= <name of the interface namespace>


    You must specify the parameters in the URL even if some of them do not have values.