NonStop SOAP User's Manual

Using NonStop SOAP with a TS/MP Application and

NonStop Processes

NonStop SOAP User’s Manual—520501-012

6-6

Annotated Example SDL Files for TS/MP

conversion operator (in case the value in the buffer must be converted before

comparison).

You also specify whether a given response is the default (used if the response

does not satisfy any other criteria) and whether the response denotes a fault. A

fault response from a server class causes a SOAP fault to be returned to client.

If the algorithm to determine the response type is too complex to express in the

SDL DTD, you might have to modify the generated classes to implement response

selection.

Annotated Example SDL Files for TS/MP

Example 1: One Service, No Client-Initiated Transactions

This example is a valid SDL input file describing a TS/MP service. Text in Courier

font is SDL. Text in Times font is supplementary.

These lines specify that this is an SDL input file for a TS/MP service in the

configuration controlled by the specified PATHMON process.

<sdl>

These lines specify the server class. The attributes indicate that the server is written in

C++ and that the strings are null terminated. The DDLDictionaryLocation attribute

specifies the location of the DDL dictionary that defines the request and response

message formats:

<ServerClass Name="EmpSvr"

language="C"

stringTermination="NullTerminated"

DDLDictionaryLocation="$DATA00.DDLSV">

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 not inherit TMF transactions started by the client. The Type attribute is not

present, so by default the service is context free. The SOAP response is not