NonStop SOAP 4.1 User's Manual
NOTE: The same <DDLDefinitionName> element must not be used more than once in a single
<RequestInfo> or <ResponseInfo> element. For example, the following sample implementation
is incorrect:
<RequestInfo>
<DDLDefinitionName>A1</DDLDefinitionName>
<DDLDefinitionName>A1</DDLDefinitionName>
</RequestInfo>
Check on SOAP Service Deployment
The SoapAdminCL tool uses DDL Dictionaries and the SDL as an input to deploy a service under
the SOAP server. In SDL DTD, the SDL element contains two attributes that denote the location of
the SOAP server.
<sdl Url="/axis2c"> ServerAddress = "http://15.146.233.43:3001">
In NonStop SOAP 4 server, the SoapAdminCL tool detects whether the server is running at the
defined location and also generates a warning message if the server is not running at the defined
location.
You can trigger this facility by providing -w option along with -i and -o options to the SoapAdminCL
tool.
Unbounded data elements support
The NonStop SOAP 4 server supports unbounded data elements for Contract-First SOAP services.
The C services can process data greater than 2 MB with unbounded data elements. For enabling
the unbounded data elements feature, configure the message receiver
(axis2_pway_xml_receiver) in the services.xml file.
Earlier versions of NonStop SOAP 4 server convert the XML message in the SOAP body to a
character buffer, and dispatch the message to a TS/MP service as shown in “NonStop SOAP 4
Request Processing Flow for TS/MP or NonStop process-based Web Services” (page 34). This
conversion causes buffer size variations for unbounded XML, which cannot be processed by the
TS/MP service. Also, the data cannot be greater than 2 MB.
For more information, see “The WSDL2PWY Tool” (page 203).
Check on SOAP Service Deployment 235










