NonStop SOAP User's Manual

NonStop SOAP Features and Functions
NonStop SOAP User’s Manual—520501-012
4-12
Server-Side Cookie File
SoapServerCL
is the executable name of the server.
options
can have any of these values:
(empty)
prints a page of help text about the use of the command-line executable.
[-s < SessionID > ] < input-xml-file > ...
produces an output message, on the standard output file, for each specified
<input-xml-file >. The server processes the input files in the order in
which you specify them.
The optional parameter -s lets you specify a session ID for session testing. If
you specify a session ID, that value overrides the session ID specified in the
SOAP header of each input file. As a result, all input files that contain a
Session element will be associated with the same session context, even if the
input files themselves specify different session IDs.
-v
displays the contents of the cookie file, including SessionID, last access time,
creation time, and timeout value (in minutes) of each session. If a subsession
is in progress, the display also identifies the SOAP server that started the
subsession. The -v option is used for diagnostics purposes, when necessary.
-x [ < deletion-threshold > ]
deletes expired session records and aborts suspended transactions associated
with expired sessions, except that if a subsession is in progress for a session,
the session is not deleted but rather marked for later deletion by the server.
< deletion-threshold > is an optional parameter indicating a time interval in
minutes. If you do not specify < deletion-threshold >, a session will be
considered to have expired if the interval specified by
SOAP_SESSION_TIMEOUT (in the NonStop SOAP configuration file) has
elapsed. If you do specify < deletion-threshold >, its value supersedes the
value of SOAP_SESSION_TIMEOUT if the value of < deletion-
threshold > is less than the value of SOAP_SESSION_TIMEOUT.
Note. The -s option adds the convenience for session testing. However, you need to
make sure the session ID supplied to -s is unique. Make sure you do not begin a
sequence of new sessions using the same session ID. SOAPServerCL does not
always flag an error when the session ID supplied to the -s option has already been
used by another session.