NonStop SOAP User's Manual

NonStop SOAP Features and Functions
NonStop SOAP User’s Manual—520501-012
4-11
Server-Side Cookie File
If you specify an existing file, ensure that the SOAP server has read and write access
to the file.
The SOAP server reads a record from the cookie file whenever a SOAP request
specifies a session ID. The SOAP server also locks the records exclusively until it
responds to the client. While the session record is locked, other SOAP servers trying to
access the same session record are blocked. Deadlock does not occur because a
SOAP server locks (at most) one record at a time.The server deletes the associated
record when the session ends by client request, or after the session times out (as
described in Session Timeout on page 4-9).
The SOAP server deletes a session record from the server-side cookie file only in
response to an input SOAP message (either a request to end the session, or a request
that arrives after the session has timed out). Therefore, if a SOAP client initiates a
session and then dies or never ends the session, orphan session records will remain,
occupying space in the file. To solve this problem, NonStop SOAP provides a way to
display and delete session records in the server-side cookie file (see Maintaining the
Cookie File and Simulating Sessions on page 4-11).
If you specify the same cookie file for multiple SOAP servers, those servers share the
same set of sessions. Such a configuration can provide load-balancing across
command-line servers or, in the case of SOAP server classes, increase the total
number of servers capable of sharing the workload.
Maintaining the Cookie File and Simulating Sessions
You can run the SOAP server as a command-line executable to simulate a session,
display session records, and delete session records that have expired. The server
reads the NonStop SOAP configuration file, described in NonStop SOAP Configuration
File on page 4-60, to discover the location of the cookie file. If the variable
SOAP_COOKIE_FILE is not set, the server uses the file
$SYSTEM.NSSOAP.SSCOOKIE.
If you are running the server to delete expired records from the cookie file, the
configuration file must specify the location of the cookie file you wish to maintain.
If you are running the server to simulate a session, consider using a dedicated cookie
file so as not to interfere with the operation of other SOAP servers.
For general information about running the SOAP server as a command-line
executable, see Running the Server from the Command Line on page 6-66.
Syntax
To run the server for the purpose of maintaining the cookie file, use this syntax:
SoapServerCL [ options ]