NonStop SOAP User's Manual

Introduction to NonStop SOAP
NonStop SOAP User’s Manual520501-012
1-4
Design-Time Architecture
2. The SOAP Admin tool reads the request and response definitions from the DDL
Dictionary. If a problem arises in reading the DDL Dictionary, the SOAP Admin tool
displays an error message.
3. Generates code for these user-exit methods, as appropriate:
A pre_process() method allows you to modify the input XML/SOAP document
sent from the client.
A pre_service() method allows you to modify the request buffer using methods
in the class ServiceReqResponse.
A pre_marshal() method allows you to modify the response buffer using
methods in the class ServiceReqResponse.
A pre_marshal header() method allows you to modify the output XML
document.
A post_process() method allows you to modify the XML/SOAP response to the
client.
4. Generates WSDL.
5. Optionally creates a Makefile for building the server process.
6. Creates DTDs and schemas for the requests and responses described in the DDL.
DTDs cannot contain type information, so the SOAP Admin tool generates
comments that describe the data type of each leaf element.
7. Creates a sample HTML/JavaScript client for each service.
Figure 1-3 on page 1-5 represents the inputs and outputs of the SOAP Admin tool.
Note. NonStop SOAP does not support DDL figurative constants. The workaround is to
specify the literal alphanumeric string (" ", 0, ....) in place of the DDL keywords
(SPACES, ZEROES, .....).
Note. For detailed information about generated classes and methods, see Files Released
and Generated on page 8-46.