NonStop SOAP 4.1 User's Manual

Example 32 Commit a Transaction and End a Session
Client Request
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:urn="urn:compaq_nsk_oss_SoapHeader">
<soapenv:Header>
<urn:Session SessionCommand="End" SessionID="234567"
CurrentTransactionCommand="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_SoapHeader">
<soapenv:Header>
</soapenv:Header>
<soapenv:Body>
.
.
.
</soapenv:Body>
</soapenv:Envelope>
Again, the response does not contain a session header block because there is no relevant session
information to be communicated back to the client now that the session closed.
The Cookie File
The implementation of sessions in previous releases (NonStop SOAP 3 and earlier) used an Enscribe
key-sequenced file (the Cookie file) to maintain a relationship between a unique SessionID
generated by NonStop SOAP and the TMF transaction ID. This was required because the NonStop
SOAP server runs as a TS/MP server class under iTP WebServer and each process instance is
context-free.
Transaction management within NonStop SOAP 4 no longer requires the presence of a session,
and therefore, you do not have to maintain the relationship between session and transaction. While
the session concept has been retained for compatibility with earlier releases, the examples in this
chapter show that the value placed in the SessionID attribute is the actual TMF transaction ID.
New users of NonStop SOAP 4 do not have to use the session construct.
As a result of this new implementation, the Cookie file is no longer required and will not be seen
in this and future NonStop SOAP releases. This improves performance and simplifies management
of the product.
Session Timeout
In NonStop SOAP 3 and earlier releases, the SOAP_SESSION_TIMEOUT attribute was used to
terminate a session. This was an ineffective mechanism, because it did not result in the abort of
any active transaction contained within that session. As a result, SOAP 3 was updated to improve
the meaning of this attribute and use it as the timeout parameter to TMF when a transaction was
started in addition to its previous role of triggering the end of a session.
In NonStop SOAP 4, the SOAP_SESSION_TIMEOUT attribute is no longer used. Instead, the
TMFTimeout attribute is used. The SOAP_SESSION_TIMEOUT attribute is no longer required
258 Transaction Management