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.

Procedure

...

       1.      Select the Transport Protocol:

○       HTTP (Axis)

○       SMTP (Axis)

The adapter uses this transport protocol to send SOAP messages as e-mails.

○       File (Axis)

○       Generic (Axis)

       2.      The Message Protocol is Axis.

       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.

Define Connection Parameters

       4.      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.

       5.      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.

       6.      Enter the User and Password, and confirm.

If the server requires a certificate from the client, enter the Keystore View and the Keystore Entry.

Define Mail Parameters for Transport Protocol SMTP (Axis)

       7.      Enter the Subject of the e-mail message.

       8.      Under From, specify the e-mail address from which the message is sent.

       9.      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.

   10.      Under Cc, specify the other addresses to which the e-mail is to be sent.

These addresses are visible to the receiver.

   11.      Under Bcc, specify the other addresses to which the e-mail is to be sent.

These addresses are not visible to the receiver.

   12.      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>

Define File Parameters for Transport Protocol File (Axis)

   13.      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.

Define Outbound Parameters

   14.      If you have selected Encapsulated as the file format, select the Encapsulation Format:

○       MIME

○       DIME

○       MTOM

Define XI Parameters

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

   16.      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