NonStop SOAP User's Manual

Using NonStop SOAP with a TS/MP Application and
NonStop Processes
NonStop SOAP User’s Manual—520501-012
6-63
Configuring and Running the Server in a WebServer
Environment
map-def-value
sets the value for map-def as “strict” or “lenient.” The value “strict” specifies a
classic NonStop SOAP server which is the default value. The value “lenient”
ignores the absence of leaf elements.
The presence of this environment variable with the value set to yes (on the
shell) alter the WSDL and schema generated by SOAPAdminCL. For the
elements in the <types> section of a WSDL, the value of the attribute
minOccurs is set to 0 instead of 1. Before running the SoapAdminCL, the
corresponding SOAP configuration attribute SOAP_MAP_DEF has to be
exported to the OSS shell:
OSS>export SOAP_MAP_DEF="lenient"
OSS>SoapAdminCL -i <sdl>
If @SUPPRESS_IN is specified and the corresponding XML element is
present in the input, then a SOAP fault would be returned back (unmarshal
error).
multiple-trace-value
sets multiple trace files. This attribute is used with the Pathway_CGI SOAP
server. The default behavior is to create a trace file per instance of the SOAP
server's Pathway server class (<soap trace file name>.<process name>). If the
value of this attribute is “no” then all instances of the SOAP server's server
class use the same trace file. In this case, the trace messages from different
instances could be interleaved, but the messages in the trace file also contain
the process id of the SOAP server instance. For example, a line from the trace
file:
>> 2002/11/25 17:47:35::Z7N9:<< Locating service name EmpInfo
The default value is "yes."
parser-api
sets the api to “dom” or “sax.” This attribute is used to specify the SAX API for
parsing a SOAP request (instead of the DOM APIs). Using the SAX API
improves the performance of the SOAP server, because it does not have to
build a DOM tree (which involves allocating memory and performing
associated housekeeping tasks) which takes time especially with large SOAP
requests.
Note. The attributes specified in a <service> element have a higher precedence over
those in the SOAP configuration file. So, if the value specified for the
SOAP_MAP_DEF attribute in the SOAP configuration file is “strict” but the <service>
element has the ProcessSoapDDLComments attribute set to “yes,” and there are
comment tags @SOAPOPTIONAL in the DDL definition, then the SOAP server will
process the comment tag.