Configuring the Receiver SOAP
Adapter
You configure a receiver SOAP adapter to send information from the Integration Server/PCK to remote clients or Web service servers.
...
1. Select the Transport Protocol:
○ HTTP (including HTTPS)
○ SMTP (including SMTPS)
The adapter uses this transport protocol to send SOAP messages as e-mails.
2. The Message Protocol is SOAP 1.1.
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.
4. Under Target URL, enter the complete address (URL) of the Web service provider that you want to send the message to.
5. 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
6. If the server requests a certificate from the client, select Configure Certificate Authentication.
Specify the following:
○ Keystore Entry
○ Keystore View
7. 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 Proxyindicator 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.
8. 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.
9. 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.
More
information:
Security Settings for
the Receiver SOAP Adapter
10. Select the security profile Web Services Security or S/MIME.
11. Specify the Persist Duration for messages in days, hours, minutes, and seconds.
12. To send the payload of the message without a SOAP envelope, select Do Not Use SOAP Envelope.
13. To include the header of the XI message in the Web service message, select Keep Headers.
14. To include attachments of the XI message in the Web service message, select Keep Attachments.
15. To encode the headers of the XI message, select Use Encoded Headers.
16. To specify a query string, select Use Query String.
17. Specify the SOAP Action.
The action species the value for the SOAPAction in Web service messages.
18. Select the Advanced tab page.
19. To process adapter-specific attributes in the message header of the XI message, select Use Adapter-Specific Message Attributes 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)
20. 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.
21. 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).
22. Set the adapter to Active to enable messages to be exchanged.