NonStop SOAP User's Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

171

172

173

174

175

176

177

178

179

180

Using NonStop SOAP with a TS/MP Application and

NonStop Processes

NonStop SOAP User’s Manual—520501-012

6-12

Annotated Example SDL Files for TS/MP

These lines specify a response structure ErrorReply, used when the first 2 bytes of the

response have the value “03.”The value of the Fault attribute is “yes,” indicating an

error response, which will cause the running process to generate a SOAP fault.

<DDLDefinitionName>ErrorReply</DDLDefinitionName>

<ResponseSelection Start="0" End="2" BufVal="03"

Fault="yes"/>

</ResponseInfo>

These lines specify an error message to be generated. Here there is no associated

DDL Definition representing the response from the target TS/MP service. This error

message is used when the first 2 bytes of the response have the value “04.” The value

of Fault attribute is “yes,” indicating an error response, which will cause the running

process to generate a SOAP fault.

<ErrorMessage>Invalid Employee Number</ErrorMessage>

<ResponseSelection Start="0" End="2" BufVal="04"

Fault="yes"/>

</ResponseInfo>

These lines are closing tags:

</Service>

</ServerClass>

These lines specify the server class HeadlineSvr. The attributes indicate that the

server is written in C or 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="HeadlineSvr"

language="C"

stringTermination="NullTerminated"

DDLDictionaryLocation="$DATA00.DDLSV">

These lines specify a service called HdlnInfo. The ServiceName attribute specifies that

the immediate child node of the Body element of the SOAP message has the tag name

HdlnInfo.The attributes specify that the input is SOAP compliant, that requests require

the client to initiate transactions, that all descendant elements of the SOAP response

are namespace qualified, operation is RPC-oriented (messages containing parameters

and return values), supports one transaction per dialog, the XML parser need not