NonStop SOAP User's Manual
Using the SOAP Admin Tool
NonStop SOAP User’s Manual—520501-012
5-8
Generated Files
name, use a back slash (\) to escape the dollar sign ($) and any other back slash. For
example:
SoapAdmin -multicast -p \\ALPINE.\$PM -s MySoapServer -m
"UPDATE SDR FlightInfo BookItinerary"
Generated Files
The SOAP Admin tool generates a file of each of these types for each request and
response definition defined for a service in the SDL file. These files are generated if the
Generate attribute is set to “yes”:
•
A document type definition, with the extension .dtd
•
An html client, with the extension .html (for each request definition)
•
An xml document containing a request with empty tag values (for each request
definition), and an xml document containing a response with empty tag values (for
each response definition), with the extension .xml
•
A WSDL file, with the extension .wsdl
•
A schema file, with the extension .xsd
In addition, the SOAP Admin tool generates these files:
•
SoapUEClassFactory.cpp
•
SoapUEHandler_impl.h
•
Makefile
•
SDR files
SoapUEClassFactory.cpp
The SoapUEClassFactory.cpp file is used to instantiate a user-exit object. The SOAP
server takes the responsibility to release the object when appropriate.
SoapUEHandler_impl.h
The SoapUEHandler_impl.h file consists of class declarations of all user-exits. For
example, suppose user-exits need to be generated for this TS/MP service.
Note. The SOAP Admin tool validates the message to be multicast. To prevent validation,
append bang (!) to the multicast switch.
Note. The SOAP Admin tool translates the DDL field defined as "TYPE LOGICAL 1" into a
schema type "xsd:boolean" in the generated files.
Note. You can customize the generated files as necessary. You can provide implementations
for classes declared in SoapUEHandler_impl.h.