You configure a receiver SOAP adapter to send information from the Integration Server/PCK to remote clients or Web service servers.
Select the Transport Protocol :
HTTP (including HTTPS)
SMTP (including SMTPS)
The adapter uses this transport protocol to send SOAP messages as e-mails.
If you want to send information from Integration Server/PCK to remote clients or Web servers, select the Message Protocol as SOAP 1.1 . If you want to send an XI message to a legacy system or AAE, then select the Message Protocol as XI 3.0 .
Using the XI 3.0 message protocol, you can, for example, configure the communication between the Advanced Adapter Engine and ABAP proxies generated in back-end systems. Note that there are restrictions when this option is used. For more information, see SAP note 1247043.
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 Connection Parameters
Under Target URL , enter the complete address (URL) of the Web service provider that you want to send the message to.
If the server requires a user authentication, select Configure User Authentication and specify the following:
For transport protocol SMTP/SMTPS, select the Authentication Method :
Plain
CRAM-MD5
User
Password with confirmation
Configure User Authentication option is available only if you select the Message Protocol as SOAP 1.1 .
If the server requests a certificate from the client, select Configure Certificate Authentication .
Specify the following:
Keystore Entry
Keystore View
The Configure Certificate Authentication option is available under Authentication data if you select the Message Protocol as XI 3.0 .
For transport protocol HTTP/HTTPS, make the following entries for the HTTP proxy server:
If the Web service provider can only be reached by using an HTTP proxy server and not directly, set the Configure Proxy indicator and enter the following:
Host
Port that proxy uses to receive HTTP requests
If the proxy requires user authentication, select Configure Proxy User Authentication .
Enter the User and Password , and confirm.
The Configure Proxy option is available under Proxy Settings if you select the Message Protocol as XI 3.0 .
2. Define Authentication Data for Message Protocol XI 3.0
Select Authentication mode:
Use logon data for SAP system
You make these entries in the PCK as well, under User Name / Password .
If you want to exchange messages with an ABAP-based receiver, specify the following:
User name
User password
Logon language
Logon client
In case the target URL mentioned is an https URL and client authentication is required, then the certificate can be configured using:
Specify the certificate name
Specify the keystore
Use logon data for non-SAP system
If you want to exchange messages with a non-ABAP based receiver, specify the following:
User name
User password
Anonymous logon
If the receiver does not execute any authentication, choose this option.
3. Define Mail Attributes for Transport Protocol SMTP/S
If you have selected SMTP/S as the transport protocol, specify the following mail attributes:
From : E-mail address that message comes from
To : E-mail address that message is sent to
If you enter more than one address, separate them with a semicolon.
Cc : Additional e-mail addresses that e-mail is to be sent to.
The addresses you specify here are visible to the receiver.
Bcc : Additional e-mail addresses that e-mail is to be sent to.
The addresses you specify here are not visible to the receiver.
Enter the Subject of the e-mail message.
4. Define Security Parameters
If you want to make additional settings for security in the relevant receiver agreement on the Integration Server or in the PCK, select Select Security Profile .
For more information, see SAP NetWeaver Library under .
Select the security profile Web Services Security or S/MIME .
Specify the Persist Duration for messages in days, hours, minutes, and seconds.
Security Parameters are available only if you select the Message Protocol as SOAP 1.1 .
5. Define Conversion Parameters
To send the payload of the message without a SOAP envelope, select Use No SOAP Envelope .
To include the header of the XI message in the Web service message, select Keep Headers .
To include attachments of the XI message in the Web service message, select Keep Attachments .
To encode the headers of the XI message, select Use Encoded Headers .
To specify a query string, select Use Query String .
Specify the SOAP Action .
The action species the value for the SOAPAction in Web service messages.
Conversion Parameters are available only if you select the Message Protocol as SOAP 1.1 .
6. Define Adapter-Specific Message Properties
Select the Advanced tab page.
To process adapter-specific attributes in the message header of the XI message, select Use Adapter-Specific Message Properties and Variable Transport Binding .
The following attributes are evaluated in the XI message header:
Server URL (technical name: TServerLocation )
You can set the entire URL.
Authentication key (technical name: TAuthKey )
Proxy URL (technical name: TProxyLocation )
Proxy authentication key (technical name: TProxyAuthKey )
SOAP action (technical name: THeaderSOAPACTION )
If you want to transfer header fields, select Variable Header .
The technical names of the fields are XHeaderName1 , XHeaderName2 , and XHeaderName3 .
The parameters are included in the HTTP request under the names specified here.
The attribute namespace for the adapter is http://sap.com/xi/XI/System/SOAP .
7. Enter and Display Authentication Keys
If authentication is required for the receiver system, you can enter a password with confirmation for each key value.
This means that you do not need to write passwords in the enhanced message header.
If you want to enter or display the respective authentication key, select View Authorization Keys .
You can enter and confirm passwords for each authentication key (TAuthKey or TproyxAuthKey).
8. 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 .