Configuring the Sender SOAP
Adapter
You need to configure the sender SOAP adapter to send content from remote clients or Web service servers to the Integration Server/PCK.
● You configure the adapter on the Parameters tab page during the definition of a communication channel in the Integration Server or in the PCK. You cannot enhance this adapter with your own modules on the Module tab page in the module processor.
● The inbound address for SOAP messages is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
...
1. You have created a new communication channel or have opened an existing one.
2. On the Parameters tab page you have selected the adapter type SOAP.
3. You have selected the Sender radio button to define the adapter as a sender adapter.
To configure the adapter, specify the following:
HTTP
SOAP 1.1
Select the Adapter Engine on the Integration Server, or select a non-centrally installed Adapter Engine. This selection is not available in the PCK.
Select the HTTP security level for inbound messages:
● HTTP
● HTTPS without client authentication
● HTTPS with client authentication
See:
HTTP and SSL and
then Enforcing HTTP Security for Incoming
Messages
● 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. See: Security Settings for Sender SOAP Adapter

If you set the indicator, there must be exactly one sender agreement for the defined communication channel.
● Under Security Profile, select whether you want to use Web Services Security or S/MIME.
● Also specify the Persist Duration for the messages.
Parameter |
Details |
Do Not Use SOAP Envelope |
If the indicator is set, the adapter expects a message without a SOAP envelope. If you set the indicator, you must also enter nosoap=true in the URL. The adapter puts the whole message in the XI payloads. |
Keep Headers |
If the header of the Web service message is to be included in the XI message, set the indicator. |
Keep Attachments |
If attachments of the Web service message are to be included in the XI message, set the indicator. |
Use Encoded Headers |
If the XI header information is to be included in the encoded string, set the indicator. |
Use Query String |
If the XI header information is to be included in a query string, set the indicator. |
Set the values for the following parameters:
● Interface namespace
● Interface name
Under Quality of Service, specify how the message is to be processed by the Integration Engine/PCK.
● Best Effort (synchronous processing)
● Exactly Once (asynchronous processing)
If the client sends a GUID, execution is guaranteed exactly once. See also: Ensuring Exactly Once Processing
● Exactly Once In Order (asynchronous processing using queues)
If the client sends a GUID, execution is guaranteed exactly once maintaining the sequence of successive messages.
Specify the Queue Name.
To store adapter attributes in the message header of the XI message, set the Set Adapter-Specific Message Attributes indicator.
The following attributes are added to the XI message header if the sender makes them available, and if the Variable Transport Binding indicator is set.
Name |
Technical Name |
Remote User |
SRemoteUser |
Remote Host |
SRemoteHost |
To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:
Name |
Technical Name |
Variable Header |
XHeaderName1 |
Variable Header |
XHeaderName2 |
Variable Header |
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 http://sap.com/xi/XI/System/SOAP.
Set the adapter to Active to enable messages to be exchanged.