NonStop SOAP User's Manual

Introduction to NonStop SOAP
NonStop SOAP User’s Manual—520501-012
1-6
Run-Time Architecture
Run-Time Architecture
The prebuilt server, or a custom server you build with output from the SOAP Admin
tool, can use existing TS/MP services or NonStop processes without requiring you to
do programming on the server side. This manual discusses how to make
customizations to a server, but most applications do not require such customizations.
At run time, the SOAP server:
1. Checks whether the request is a well-formed XML document.
2. Parses an XML or SOAP request, using the NonStop XML parser.
3. Determines the type of service requested and then locates the service details for
the target service.
4. Unmarshals the request.
•
Creates a DDL buffer with the input values.
•
Invokes the TS/MP service with a Pathsend call or a NonStop process with a
READ/WRITE call.
5. Creates an XML response based on the response from the target service.
6. Sends the SOAP/XML response back to the requesting client.
Common Services for SOAP Servers
The section describes the features that are available for use with TS/MP services and
NonStop processes.
These features are controlled by the client using SOAP headers:
•
Session context management
•
Transaction control
•
Internationalization
Session Context Management
NonStop SOAP allows a client to establish sessions with context-free and context-
sensitive TS/MP server classes. For NonStop processes only context-free sessions are
supported.
In the case of context-free access, a client can invoke multiple services within a
particular session. Session context is stored in a file, allowing different members of a
SOAP server class to handle requests within the same session, and allowing a
transaction to span calls to multiple SOAP messages, as described in Transaction
Management on page 1-7.