NonStop SOAP User's Manual

Using NonStop SOAP with a TS/MP Application and
NonStop Processes
NonStop SOAP User’s Manual—520501-012
6-29
Sessions and Transactions with TS/MP Servers and
NonStop Processes
Request to End the Session and Commit the Transaction
To end the session and commit the transaction, the client sends this message:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<Id:Session SessionID="B4UY7899988"
CurrentTransactionCommand="End"
SessionCommand="End"
xmlns:Id="urn:compaq_nsk_oss_SoapHeader/">
</SOAP-ENV:Header>
<SOAP-ENV:Body>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Sessions and Transactions with Context-Sensitive TS/MP
Servers
Context-sensitive TS/MP servers maintain context between requests sent by clients.
When a SOAP client first invokes a context-sensitive service within a session, the
NonStop SOAP server initiates a SOAP subsession: a subsession between the client
and the SOAP server results in a dialog between the SOAP server and the target
server class. Within the scope of the session, the SOAP server ensures that all
requests to a context-sensitive server class are handled by the same server process
within the class. A session can include requests to multiple context-free and context-
sensitive server classes, but only one subsession can be in progress at a given time:
therefore within a session, a client can have a subsession with server class A, then a
subsession with server class B, then another subsession with server class A, but
cannot interrupt a subsession with server class A to make a request to server class B.
A SOAP client explicitly begins and ends (or, if necessary, aborts) a session with a
SOAP server, using header attributes described in Session Management on page 4-3.
The server indicates that a session is in progress by including a Session ID in
response messages. After the client ends a session, responses do not include a
Session ID.
In contrast to sessions, a subsession with a specific context-sensitive server class
begins and ends implicitly, except in one case:
•
The SOAP server begins the subsession implicitly when the client makes it first
request to the context-sensitive server class.
Note. This section is not applicable for NonStop processes.