NonStop SOAP 4.1 User's Manual

NOTE:
• For information on the TMFTransactionSupport, AbortTransactionOnFault, and
TMFTimeout attributes, see “Configuring the Level of Transaction Support” (page 245) and
“Transaction Timeouts” (page 246).
• Previous versions of NonStop SOAP (SOAP 3 and earlier) defined the need to contain a
multi-step transaction within a session, which was defined in a session header block in the
SOAP message. With NonStop SOAP 4, sessions are no longer required (which enables
transaction management to be greatly simplified). NonStop SOAP 4 will continue to process
session attributes and commands for compatibility with previous releases, and the syntax and
semantics of this mechanism is described in “Session Management and Transactions” (page 249).
There is an intent to discontinue the session construct in a future release of NonStop SOAP,
though no date has been set for this action.
This chapter describes the following topics:
• “Transaction Module Configuration” (page 237)
• “SOAP Server Transaction Management” (page 238)
• “SOAP Client Transaction Management” (page 238)
• “Configuring the Level of Transaction Support” (page 245)
• “Transaction Timeouts” (page 246)
• “Session Management and Transactions” (page 249)
NOTE: It must be remembered that NonStop SOAP 4 runs as a TS/MP server class, so throughout
this chapter and elsewhere in this manual, when the term SOAP server is used it is not referring to
a single process instance.
Transaction Module Configuration
To enable NonStop SOAP 4 to recognize and correctly process the transaction (and session)
header blocks in the SOAP request header, you must configure it to include the Transaction Module
that is part of the product distribution.
To configure the transaction module in NonStop SOAP 4, complete the following steps:
1. Open the <NonStop SOAP 4 Deployment Directory>/axis2.xml file and locate
the following commented section:
<!-- ============================ -->
<!-- Global Modules -->
<!-- ============================ -->
2. After the Global Modules section, add the module element and set its ref attribute value
to transaction.
<module ref=”transaction”/>
NOTE: When defining the module element, do not add a space between < and the module
element.
3. Save and close the axis2.xml file.
4. Restart the iTP WebServer.
OSS>./<iTP WebServer Deployment Directory>/conf/restart
The transaction module is now attached with your NonStop SOAP 4 deployment and can intercept
each request and perform the requested transaction related operations.
Transaction Module Configuration 237