Configuring the Receiver Axis SOAP
Adapter
Use
You configure the receiver Axis SOAP adapter to send information from the Integration Server or the PCK to remote clients or Web service servers.
Integration
You configure the adapter on the Parameters tab page during the definition of a communication channel in the Integration Server or in the PCK.
In addition to the adapter configuration, you can use the Module tab page in the module processor to specify generic modules, which give the adapter additional functions.
Prerequisites
...
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 Receiver radio button to define the adapter as a receiver adapter.
Activities
To configure the adapter, specify the following:
Transport Protocol
● HTTP (Axis)
● SMTP (Axis)
The adapter uses this transport protocol to send SOAP messages as e-mails.
● File (Axis)
● Generic (Axis)
Message Protocol
Axis
Adapter Engine
Select the Adapter Engine on the Integration Server, or select a non-centrally installed Adapter Engine. This selection is not available in the PCK.
Connection Parameters
● Under URL, enter the complete address of the Web service provider that you want to send the message to.
To use a secure connection, enter https.
● Under Authentication, select:
○ None
Supported by the following handlers:
■ com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
■ com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender
○ Basic
Supported by the following handlers:
■ com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
■ com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender
○ Digest
Supported by the following handlers:
■ com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender
○ NTLM
Microsoft NT LAN Manager authentication schema
Supported by the following handlers:
■ com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender
○ Certificate
Supported by the following handlers:
■ com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
■ com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender
■ com.sap.aii.adapter.axis.ra.transport.http.SAPDestinationSender
○ SAP Assertion Ticket
Supported by the following handlers:
■ com.sap.aii.adapter.axis.ra.transport.http.SAPDestinationSender
If you are using the handler com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender, the commons-httpclient of Apache Commons HTTP Client must be contained in axisproviderlib.
● Enter the User and Password, and confirm.
If the server requires a certificate from the client, enter the Keystore View and the Keystore Entry.
Mail Parameters for Transport Protocol SMTP (Axis)
● Enter the Subject of the e-mail message.
● Under From, specify the e-mail address from which the message is sent.
● Under To, specify the e-mail address that will receive the message.
If you enter more than one address, you must separate them with a semicolon.
● Under Cc, specify the other addresses to which the e-mail is to be sent.
These addresses are visible to the receiver.
● Under Bcc, specify the other addresses to which the e-mail is to be sent.
These addresses are not visible to the receiver.
● Under Response, select the response the receiver is to send after receipt of the e-mail.
○ Empty
The receiver sends an empty e-mail.
○ Echo
The receiver sends the received message as the response.
○ Status
The receiver sends a status report:
<t:TransportStatus xmlns:t="http://sap.com/aii/axis/type/transport">
<protocol>protocol</protocol>
<time>2007-03-05T09:42:43Z</time>
<host>hostname</host>
<information>
<value type="type">value</value>
</information>
</t:TransportStatus>
schema:
<xsd:schema targetNamespace="http://sap.com/aii/axis/type/transport">
<xsd:element name="TransportStatus" type="tns:TransportStatusType"/>
<xsd:complexType name="TransportStatusType">
<xsd:sequence>
<xsd:element name="protocol" type="xsd:string"/>
<xsd:element name="time" type="xsd:dateTime"/>
<xsd:element name="host" type="xsd:string"/>
<xsd:element name="information" type="tns:InformationType"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="Response" type="tns:ResponseType"/>
<xsd:complexType name="ResponseType">
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="InformationType">
<xsd:sequence>
<xsd:element name="value" type="tns:ValueType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ValueType">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="type" type="xsd:string" />
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:schema>
File Parameters for Transport Protocol File (Axis)
● Select the File Format:
○ Parts
The main payload and any attachments are put into separate files.
○ Encapsulated
The main payload and any attachments are put into one file.
Outbound Parameters
● If you have selected Encapsulated as the file format, select the Encapsulation Format:
○ MIME
○ DIME
○ MTOM
XI Parameters
● To include the header of the XI message in the Web service message, select Keep XI Headers.
● To include attachments of the XI message in the Web service message, select Keep Attachments.
● Under Payload Extraction, select which part of the XI message to take the payload of the SOAP message from:
○ SOAP Body Child
○ SOAP Body
○ SOAP Envelope
○ Attachments