NonStop SOAP 4.1 User's Manual

1. “Running the SoapAdminCL Tool to Generate the Module Handler Stub Files” (page 133)
2. “Implementing the Business Logic in the Module Handler Stub Files” (page 134)
3. “Engaging the Module Handler at the Service Level” (page 136)
4. “Verifying the Module Handler Output” (page 137)
Running the SoapAdminCL Tool to Generate the Module Handler Stub Files
The SoapAdminCL tool enables you to generate the module handler stub files and the module.xml
file. The SoapAdminCL tool generates the skeleton files for handlers in the inflow and outflow.
To run the SoapAdminCL tool, complete the following steps:
1. Add the directory that includes the SoapAdminCL 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
2. Run the SoapAdminCL tool to generate the module handler stub files:
OSS> SoapAdminCL -o <output directory>
-mod <module_name>
where,
<output directory>
specifies the output directory where the module handler stub files will be generated.
<module_name>
specifies the name of the generated module.
For example:
OSS> SoapAdminCL –o /home/user1/mynssoap –mod logging
3. Verify that the following directory structure is created in the <output directory>:
modules
/mod_logging
module.xml
/src
mod_logging.h
mod_logging.c
logging_in_handler.c
logging_out_handler.c
Makefile
where,
module.xml
is the configuration file for the logging module.
mod_logging.h
is the header file for the mod_logging.c source.
mod_logging.c
is the C stub file that implements the interface between the NonStop SOAP 4 server and
the logging module.
logging_in_handler.c
is the C stub file where you must implement the loggingInHandler business logic for
the handler. For the logging module, the business logic is designed to log the input XML
message.
Customizing the NonStop SOAP 4 Message Process Using Handlers 133