NonStop SOAP 4.1 User's Manual

to” and the default conversion operator is “string”. If the buffers match, the response structure

in Response0 is selected to return the response to the client.

Controlling TMF Transaction Support

NonStop SOAP 4 enables you to specify whether a TMF transaction must be started for a given

operation. To achieve this, specify the TMFTransactionSupport parameter in the name attribute

of the parameter element in the services.xml file. This is an optional element. For example:

where,

<parameter-value> [Required | Supports | Never]

is the parameter value. The options are Required, Supports,or Never. The default value

is Supports.

Required

indicates that the operation in the SOAP request will always be performed within a TMF

transaction.

• If the client request does not have the Transaction element as a part of the SOAP

request header, NonStop SOAP server will begin a TMF transaction before invoking

the service and commit or abort the transaction.

• If the client request has a Transaction element in the SOAP request header, NonStop

SOAP will process the transaction element.

• For server initiated transactions, NonStop SOAP 4 will set the transaction timeout equal

to the value of the TransactionTimeOut parameter in the services.xml file

(effective timeout will be lower than the timeout set in the services.xml file and

TMFAutoAbort timeout system configuration).

Supports

indicates that the operation in the SOAP request will be performed within a client-initiated

TMF transaction. If the client request does not have the transaction or session element in

the SOAP request header, NonStop SOAP 4 will perform the operation in the SOAP request

without starting any transaction.

Never

indicates that NonStop SOAP 4 will not initiate a transaction.

NOTE: For more information about transaction initiated by the client request, see Transaction

Management (page 236) .

Example 2 shows a sample services.xml configuration file.

188 NonStop SOAP 4 Configuration Files