Configuring the Sender Axis SOAP Adapter 

Use

You configure the sender Axis SOAP adapter to send content from remote clients or Web service servers to the Integration Server/PCK.

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.

More information: Adding Modules in the Axis SOAP Adapter

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 Sender radio button to define the adapter as a sender adapter.

Features

The sender Axis SOAP adapter allows you to receive inbound messages using a servlet or an active or passive task:

●      Messages can be sent to a servlet. It receives messages under the following address: http://host:port/XIAxisAdapter/MessageServlet?parameters

parameters ::= token ( ‘&’ token )*

token ::= name ‘=’ value

name ::= fieldname

value ::= fieldvalue

fileldname ::= ‘senderParty’ | ‘senderService’ | ‘receiverParty’ | ‘receiverService’ |

‘interface’ | ‘interfaceNamespace’ | ‘messageId’ | ‘queueName’

fieldvalue ::= urlencoded value

●      If you use an active task, you poll inbound messages at defined time intervals.

●      If you use a passive task, your sender Axis SOAP adapter waits for the message to arrive.

Activities

To configure the adapter, specify the following:

Transport Protocol

●      Servlet (Axis)

●      Task (Axis) Active

●      Task (Axis) Passive

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 for Transport Protocol Task

If you have selected Task (Axis) as the transport protocol, specify the following:

●      Enter the URL of the task.

●      Select the Authentication:

○       None

○       Basic

○       Digest

○       NTLM

Microsoft NT LAN Manager authentication schema

○       Certificate

○       SAP Assertion Ticket

○       Other

To define a different authentication method in the task, select Other.

You must also add the corresponding handlers for executing the authentication method on the Module tab page.

Task Parameters for Transport Protocol Task (Axis)

●      Under Task Class, enter the name of the task class.

●      Enter names and values for the parameters of the task class in the table.

●      If you have selected an active task, you can make entries for the poll procedure of the task:

○       Under Recurrences, specify how many attempts the task should make to poll a message.

The default value -1 means unlimited.

○       Under Interval (msec), specify the interval between poll procedures in milliseconds.

○       Under Timeout (msec), specify the time period after which to cancel the poll procedure.

XI Parameters

●      Select the Quality of Service.

See: Quality of Service

If you choose Best Effort, specify in the Adapter Framework Parameters under Timeout how many milliseconds to wait before canceling the delivery of the message.

●      To keep the XI header in the response message, select Keep XI Headers.

●      To include attachments from the Web service message in the XI message, choose Keep Attachments.

●      Under Payload Extraction, select which part of the Axis SOAP message to take the main payload of the XI message from:

○       SOAP Body Child

○       SOAP Body

○       SOAP Envelope

○       Attachments

The first attachment is put in the main payload; further attachments become attachments of the XI message.