NonStop SOAP 4.1 User's Manual

.
</operation>
3. Save and close the services.xml configuration file.
The TMFTransactionSupport attribute is an optional attribute. The default value of the
TMFTransactionSupport attribute is Supports. Thus, if a client request includes a transaction
header block in the SOAP request header, then NonStop SOAP 4 will process the Command
attribute contained within it, even if the TMFTransactionSupport attribute is not set in the
services.xml file.
NOTE:
• When developing a service the TMFTransactionSupport attribute can be set as an
operation level attribute in the SDL file.
• When deploying a service using the SoapAdminCL tool, the services.xml configuration
file will have the TMFTransactionSupport attribute set to a value specified in the SDL file.
For more information about setting the TMFTransactionSupport attribute in the SDL file,
see “NonStop SOAP 4 Service Description Language” (page 153).
Transaction Timeouts
During the processing of a transaction, it is typical for resources in the database to be locked (for
example, a table row, or even a complete table) until the transaction is committed (or aborted) to
ensure data integrity. For a multi-step transaction, this can pose a problem in the event that the
client that started the transaction does not continue or end the transaction in a reasonably short
timeframe. There could be many reasons, including loss of communication between the client and
the NonStop server, or it could be as simple as a client-side operator stepping away from his/her
desk in mid-transaction for a while. In the meantime, database resources remain locked and could
potentially cause significant performance degradation and loss of service for other clients. It is
therefore important that an application have a variety of tools available to cause a transaction to
timeout and be aborted. NonStop SOAP 4 allows several configuration options to set timeout
values at the operation level from the client or on the server using the services.xml file, or
globally at a system level within TMF:
• TimeOut:
The TimeOut attribute can be set to a timeout value by the client in the transaction header
block of the SOAP request header element, which is used to begin a transaction.
• TMFTimeout:
The TMFTimeout attribute can be specified at the operation level within the services.xml
file. For more information on how to configure the TMFTimeout attribute, see “Configuring
Transaction Timeout” (page 247).
• TMFAutoAbort:
TMFAutoAbort is a system-defined timeout that specifies the time duration, after which all
TMF transactions are aborted automatically by the TMF subsystem. The system default value
is 2 hours. This timeout value can be changed by the system administrator using the TMFCOM
utility.
For information on customizing the TMFAutoAbort timeout value using the TMFCOM utility,
see the TMF Reference Manual.
After comparing the values of TimeOut and TMFTimeout, if specified, the SOAP server takes
the minimum value and uses it in the call to TMF that begins the transaction. If neither is specified,
the value of TMFAutoAbort will determine transaction timeout.
246 Transaction Management