NonStop SOAP 4.1 User's Manual

.
.
</operation>
3. Save and close the services.xml configuration file.
NOTE:
• When developing a service, the AbortTransactionOnFault 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 AbortTransactionOnFault attribute set to a value specified in the SDL
file.
For more information about setting the TMFTimeoutattribute in the SDL file, see “NonStop
SOAP 4 Service Description Language” (page 153).
Session Management and Transactions
Previous versions of NonStop SOAP (SOAP 3 and earlier), defined the concept of a session as a
logical grouping of a series of requests and were required for transaction control; a transaction
could occur only within a session. However, with the release of NonStop SOAP 4, the logical
grouping of requests is now defined as a transaction, and sessions are no longer required to
perform a multi-step transaction.
NOTE: If you are new to NonStop SOAP, you need not read further in this chapter because the
remaining sections describe features that are simply retained to aid in compatibility and migration
from earlier releases.
NonStop SOAP 4 defines the concept of a session header block that can be contained within a
SOAP request, and may include the use of the attributes listed in Table 20.
Table 20 Session Header Attributes
DescriptionValuesAttribute
Used to begin or end a session.Begin, EndSessionCommand
Contains a unique value set by the SOAP server
in a response message to a begin session request
Set by SOAP serverSessionID
to act as a 'handle' for the session in subsequent
client requests.
Starts a new transaction within an active session.yesBeginNewTransaction
Commits or aborts a transaction.End, AbortCurrentTransactionCommand
The session header block can be defined in the WSDL file for a service by setting the service-level
attribute GenerateSessionHeader to yes in the SDL file for the service.
NOTE: For any given service, the WSDL file generated by the SoapAdminCL tool will not define
both session header blocks and transaction header blocks. The inclusion of the session and
transaction header blocks in the WSDL file is controlled by the GenerateSessionHeader and
GenerateTransactionHeader attributes of the Service element in the SDL file. Only one of
these attributes may be set to yes for a given service. An error is issued by SoapAdminCL if both
the attributes are set to yes for a particular service.
The following sections describe how each of these session attributes may be used to start and end
sessions, and to begin and end transactions within these sessions.
Session Management and Transactions 249