NonStop SOAP User's Manual
Introduction to NonStop SOAP
NonStop SOAP User’s Manual—520501-012
1-7
Transaction Management
In the case of context-sensitive access, a session can also encompass calls to multiple 
server classes. The dialog with each server class is a subsession within the session. A 
SOAP server class that provides access to context-sensitive services must consist of 
only one server process (Maxservers=1 in the server class configuration).
A client requests a session by including a specific element in the SOAP request 
header. The SOAP server returns a session ID, which the client must include in all 
subsequent requests until the end of the session. The response to a request to end the 
session does not include the session ID.
Figure 1-4 represents session context management by a SOAP server for TS/MP 
services. For more detailed information, see Session Management on page 4-3. 
Transaction Management
NonStop SOAP allows a client to begin, commit, or abort transactions within a session. 
The underlying technology for transaction control on a NonStop system is HP NonStop 
Transaction Management Facility (TMF).
Figure 1-4. Session Context Management for TS/MP Services or NonStop 
Process
SOAP
Client
SOAP
Client
SOAP
Client
VST008.vsd
NonStop TS/MP
Services
Pathsend
SOAP Server
SessionCommand
"Begin"
SessionID
Pathsend
SOAP Server
SessionID
NonStop TS/MP
Services
Pathsend
SOAP Server
SessionCommand
"End"
SessionID
NonStop TS/MP
Services
READ/WRITE
NonStop Process
READ/WRITE
NonStop Process
READ/WRITE
NonStop Process










