NonStop SOAP 4.1 User's Manual

When the SOAP server receives a request to commit an active TMF transaction, the following
occurs:
1. The SOAP server resumes the TMF transaction specified in the TransactionID attribute of
the transaction header block of the SOAP request.
2. The SOAP server invokes the operation (if specified in the body of the request) under the
resumed TMF transaction.
3. When the service responds back to NonStop SOAP 4, a commit transaction request is sent
to TMF and the SOAP response is sent back to the client. The response message will not
contain a transaction header block because there is no TransactionID value to communicate
back to the client.
4. If the service returns a fault and the AbortTransactionOnFault attribute is set to no, the
transaction is not aborted. The TransactionID is sent back to the client in a Transaction
header block in the response message along with the fault returned by the operation. This
allows the client to decide whether to abort the transaction, or retry the operation.
5. If the service returns a fault and the AbortTransactionOnFault attribute is set to yes,
the SOAP server aborts the transaction and returns the SOAP fault to the client. The response
message will not contain a transaction header block because there is no TransactionID
value to communicate back to the client.
Example 23 shows a request/response pair of messages to commit a transaction.
Example 23 Commit 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 TransactionID="234567" Command="Commit"/>
</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>
</soapenv:Header>
<soapenv:Body>
.
.
.
</soapenv:Body>
</soapenv:Envelope>
where,
234567
is the identifier of the transaction to be committed, and was provided in a previous response
from NonStop SOAP.
SOAP Client Transaction Management 243