NonStop SOAP 4.1 User's Manual
Validation Module
The SOAP messages sent by the clients must be validated against the WSDL schema to ensure that
correct data is received. The NonStop SOAP 4 validation module validates the received data. The
validation module is a global module, and it is enabled by default.
All the service requests to the NonStop SOAP 4 server are validated against the service WSDL
schema by default. If the requests confirm to the schema, then the NonStop SOAP 4 server processes
the requests. If the requests do not confirm to the schema, then the validation module sends back
a Module Validation Failed message to the client, and does not process the request. For
more information about the failure, see the log files in the <NonStop SOAP 4 Deployment
Directory>/logs folder.
The Global Modules section of axis2.xml file contains the configuration for the validation
module. To turn off this feature, comment the line in axis2.xmlfile.
<!-- ================================================= -->
<!-- Global Modules -->
<!-- ================================================= -->
!-- <module ref="validation”/> -->
NOTE: Even if the validation module is turned off, the NonStop SOAP 4 server validates for most
of the data type values. However, the validations for XML constructs are not very strict.
The validation module feature impacts performance. The first request for a service takes a longer
time than the subsequent requests as the schema has to be loaded into the memory for the first
request. The time taken by the validation module to process the request is directly proportional to
the size of the request (that is the number of XML elements in the request). In cases where the service
response time is extremely important, to gauge the overhead caused by the module, HP recommends
measuring the NonStop SOAP 4 server response times with and without this feature. Decide to
enable or disable this feature, based on these measurements.
SOAP_WSDL_NAME DDL Comment
The SoapAdminCL generates the WSDL file and DDL mapping file to display the TS/MP application
as a Web service. You can add a comment in DDL file that defines the WSDL file name to be used
in the WSDL file for a field.
The following example describes the use of the SOAP_WSDL_NAME DDL a comment in the DDL
definition and the generated WSDL and DDL mapping files:
DDL Definition
DEFINITION INPUTDEF
02 A1 PIC X(1)
*@SOAP_WSDL_NAME wsdlnamea2
02 A2 PIC X(4)
END
The following example displays a generated sample WSDL file:
<xsd:element name="REFLECTOR" type="tns1:REFLECTOR"/>
<xsd:complexType name="REFLECTOR">
<xsd:sequence>
<xsd:element name="a1" minOccurs="1" maxOccurs="1">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="wsdlnamea2" minOccurs="1" maxOccurs="1">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
Validation Module 233










