NonStop SOAP User's Manual
Using NonStop SOAP with a TS/MP Application and
NonStop Processes
NonStop SOAP User’s Manual—520501-012
6-18
Annotated Example SDL Files for NonStop Process
Annotated Example SDL Files for NonStop
Process
This example is a valid SDL input file describing Process named “$PROC” that has a
service “EmpInfo.”
These lines specify that this is an SDL input file for a NonStop process and $PROC
represents the name of a valid NonStop process under the OSS/Guardian operating
system.
<sdl>
<Process>
<ProcessEnvironment Name="$PROC>
These lines specify the ProcessDetails name. The attributes indicate that the server is
written in C and that the strings are nonnull terminated. The DDLDictionaryLocation
attribute specifies the location of the DDL dictionary that defines the request and
response message formats:
<ProcessDetails Name="EmpInfo"
language="C"
stringTermination="NonNull"
DDLDictionaryLocation="$VOL.SUBVOL">
These lines specify one service, EmpInfo. The ServiceName attribute specifies that the
immediate child node of the Body element of the SOAP message has a tag name
EmpInfo.The attributes specify that the input is SOAP compliant, and that the service
does inherit TMF transactions started by the client. The AbortTransactionOnFault
specifies the transaction is aborted when a fault is received. The Caching attribute in
set to "on". The SOAP response is not namespace qualified, the SOAP message type
is document, the server must validate input against the DTD. The DDL comments are
not processed and the DDL default value is not used. The DeployOption attribute is set
to “addUpdate” which adds the interface as a Web service if it does not exist. The
Generate attribute adds the new and modified service definitions and the