NonStop SOAP 4.1 User's Manual

SoapPW_<operation1_name>.xsd
SoapPW_<operation1_name>Response0.xsd
SoapPW_<operation1_name>Response1.xsd
SoapPW_<operation2_name>.xsd
SoapPW_<operation2_name>Response0.xsd
SoapPW_<operation2_name>Response1.xsd
/services
/<service_name>
SoapPW_<service_name>.wsdl
services.xml
For example:
OSS> SoapAdminCL –o /home/soap_usr/nssoap -i soapapp.sdl -m
The directory appears as:
/home/soap_usr/nssoap
/client
/myservice
SoapPW_myoperation1.html
SoapPW_myoperation2.html
/wsdl
SoapPW_myoperation1.wsdl
SoapPW_myoperation2.wsdl
/pway-xml
SoapPW_myoperation1.xml
SoapPW_myoperation1Response0.xml
SoapPW_myoperation1Response1.xml
SoapPW_myoperation2.xml
SoapPW_myoperation2Response0.xml
SoapPW_myoperation2Response1.xml
/pway-xsd
SoapPW_myoperation1.xsd
SoapPW_myoperation1Response0.xsd
SoapPW_myoperation1Response1.xsd
SoapPW_myoperation2.xsd
SoapPW_myoperation2Response0.xsd
SoapPW_myoperation2Response1.xsd
/services
/myservice
SoapPW_myservice.wsdl
services.xml
In the example, myservice is the service name and myoperation1 and myoperation2
are the operation names.
The HTML client, the WSDL file, SOAP request and response XML files, XML schema files, and
the services.xml file is generated in the NonStop SOAP 4.1 deployment directory. The
service is now deployed in NonStop SOAP 4.1.
NOTE: Though the SDL file is not required during runtime, you must retain it in case the
HTML client, the WSDL file, SOAP request and response XML files, XML schema files, or the
services.xml file need to be regenerated.
3. Engage the Transaction module with NonStop SOAP.
Transaction management is implemented through a NonStop SOAP module. Therefore, the
NonStop SOAP server administrator needs to engage the transaction module for transaction
60 Migrating NonStop SOAP 3 Services to NonStop SOAP 4 or Higher Versions