NonStop SOAP 4.1 User's Manual

For example, use the following command to generate asynchronous client stubs using the
WSDL2C tool:
OSS> WSDL2C –o "/home/nssoap/test/client" –a –u
–uri "/home/nssoap/test/services/test_service/SoapPW_test.wsdl"
where,
/home/nssoap/test/client
is the output location.
-uri /home/nssoap/test/services/test_service/SoapPW_test.wsdl
specifies the WSDL Web address provided to the WSDL2C tool.
5. On successful execution, the following files will be generated:
• Client source stub files to implement the SOAP client application business logic.
• Header files that hold the declarations for the functions generated in the client source stub
files.
• Data binding header files that hold declarations for the data structures present in the
WSDL schema.
Generating NonStop SOAP 4 Service Skeleton Files
The WSDL2C tool generates the NonStop SOAP 4 service skeleton files in the C programming
language. The generated service skeleton files contain the basic interface code to be implemented
when developing services implemented as DLLs using NonStop SOAP 4 service APIs.
To generate the NonStop SOAP 4 service skeleton files using the WSDL2C tool, complete the
following steps:
1. Set the OSS environment variable NSSOAP_HOME to the OSS location where the NonStop
SOAP 4 installation directory is located:
OSS> export NSSOAP_HOME=<NonStop SOAP 4 Installation Directory>
For example:
OSS> export NSSOAP_HOME=/usr/tandem/nssoap/t0865h01
where,
/usr/tandem/nssoap/t0865h01
is the NonStop SOAP 4 installation directory.
2. Add the directory containing the WSDL2C executable image to the OSS PATH variable.
OSS> export PATH=<NonStop SOAP 4 Installation Directory>/tools:$PATH
For example:
OSS> export PATH=/usr/tandem/nssoap/t0865h01/tools:$PATH
3. Add the <Java Installation Directory>/bin directory to the PATH environment
variable, using the command:
OSS> export PATH=<Java Installation Directory>/bin:$PATH
For example:
OSS> export PATH=/usr/tandem/java/bin:$PATH
where,
/usr/tandem/java/
is the Java installation directory.
4. Generate the service skeleton files using the WSDL2C command:
OSS> WSDL2C [options] –u –uri [wsdl_path]
where,
The WSDL2C Tool 213