NonStop SOAP 4.1 User's Manual

the client. The NonStop SOAP 4 server generates a temporary session identifier because the
current SessionID is no longer valid. The NonStop SOAP 4 server returns the session identifier
in the session block header of the response message and sets this value for the SessionID
attribute.
5. If the invoked service returns a fault and the AbortTransactionOnFault attribute is set
to yes, NonStop SOAP 4 aborts the transaction and returns a SOAP fault to the client. The
SOAP message does not contain a Transaction header block because there is no
TransactionID to return back to the client.
6. This series of request/response actions can continue until the client decides that the transaction
needs to be ended with either a commit or an abort request.
Example 22 shows a request/response pair of messages to continue a transaction.
Example 22 Continue a Transaction
Client Request
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:compaq_nsk_oss_TransactionHeader">
<soapenv:Header>
<urn:Transaction Command="Continue" TransactionID="234567"/>
</soapenv:Header>
<soapenv:Body>
.
.
.
</soapenv:Body>
</soapenv:Envelope>
NonStop SOAP 4 Response
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:compaq_nsk_oss_TransactionHeader">
<soapenv:Header>
<urn:Transaction TransactionID="234567"/>
</soapenv:Header>
<soapenv:Body>
.
.
.
</soapenv:Body>
</soapenv:Envelope>
where,
234567
is the value assigned to the TransactionID attribute that was provided in a previous response
by NonStop SOAP for this transaction.
Commit a Transaction
To commit an active TMF transaction, the client must include a Transaction header block that sets
the Command attribute to Commit and sets the value of the TransactionID attribute to the value
of the TransactionID attribute provided by a previous response from NonStop SOAP 4
associated with this transaction.
NOTE: If the SOAP request invokes a target service, the operation in the request will be executed
as a part of the active TMF transaction.
242 Transaction Management