NonStop SOAP 4.1 User's Manual

-uri
specifies the location where the WSDL file is available.
For example:
OSS> WSDL2PWY -o "/home/usr/my_nssoap/services/reflector" -ss
-uri "/home/usr/my_nssoap/services/reflector/SoapPW_reflector.wsdl"
where,
/home/usr/my_nssoap/services/reflector is the location where the service skeleton
files will be generated.
NOTE: Verify that the location of the Java executable object is included in the PATH
environment variable. If not included, the WSDL2PWY tool will not be able to detect the Java
object during runtime and will return an error.
On successful execution, the following files are generated:
• Service skeleton files
The following service skeleton files are generated under the src directory in the location
specified in the -o option of the WSDL2PWY command:
◦ Service skeleton source file to implement your application business logic.
◦ Header file that holds the declarations for the functions generated in the service
skeleton source file.
NOTE: If the -o option is not specified, the files are generated in the src directory
under the current directory.
For example:
In case of the reflector service, the following files are generated in the <NonStop
SOAP 4 Deployment Directory>/services/reflector/src directory:
◦ pwayreflectorService.c
◦ pwayreflectorService.h
• Makefile
The Makefile_service Makefile is generated in the location specified in the –o option
of the WSDL2PWY command. If the -o option is not specified, the file is generated in the
current directory.
5. Update the service skeleton files with the service business logic.
The WSDL2PWY tool generates a source code file and a header file for each service specified
in the WSDL file. The source code file for the service contains the following functions:
a. main()
The main function expects two arguments, a character pointer array (char *argv[])
and an integer value (int argc). argv includes arguments passed to the function while
starting the server executable, whereas argc includes a value equivalent to the number
of arguments passed to the function.
i. The main()function opens the $RECEIVE file and waits till a request is received by
the service using the READUPDATEX procedure call.
ii. After a request is received, the main()function checks if any error occurred while
reading the request.
iii. If no error is found, the request buffer is passed to the
process_application_message()function.
Developing a NonStop SOAP 4 Pathway Web Service Using the WSDL2PWY Tool 263