NonStop SOAP 4.1 User's Manual

ManualsBrandsHP ManualsServerHP Integrity NonStop H-Series

131

132

133

134

135

136

137

138

139

140

4. Edit the module.xml file as follows:

• Set the value of the phase attribute of the order element in the inflow to

PostDispatch. The loggingInHandler is invoked in the PostDispatch phase.

• Set the value of the phase attribute of the order element in outflow to MessageOut.

The loggingOutHandler is invoked in the MessageOut phase.

</handler>

</inflow>

</handler>

</outflow>

</module>

NOTE: If you encounter an error while building the logging module, repeat the steps listed

in “Running the SoapAdminCL Tool to Generate the Module Handler Stub Files” (page 133)

and “Implementing the Business Logic in the Module Handler Stub Files” (page 134).

Engaging the Module Handler at the Service Level

After the DLL for the libaxis2_mod_logging.so module is built, you must engage the DLL with

NonStop SOAP 4. The module can be engaged in NonStop SOAP 4 only if the module.xml

and DLL files are present in <NonStop SOAP 4 Deployment Directory>.

NOTE: If you do not generate the module handler stub files in <NonStop SOAP 4 Deployment

Directory>, you must:

1. Create the <NonStop SOAP 4 Deployment Directory>/modules/<module_name>

directory.

2. Copy the module.xml file and the generated DLL file in the <NonStop SOAP 4 Deployment

Directory>/modules/<module_name> directory. For information about generating DLL

files, see “Implementing the Business Logic in the Module Handler Stub Files” (page 134).

If the module.xml and the libaxis2_mod_logging.so DLL files are not present in <NonStop

SOAP 4 Deployment Directory>/modules/mod_logging, complete the following steps:

1. Create the <module_name> directory in the <NonStop SOAP 4 Deployment

Directory>/modules directory.

OSS> mkdir <NonStop SOAP 4 deployment location>/modules/mod_logging

2. Copy the libaxis2_mod_logging.so DLL file and the module.xml file from the <output

directory> to the <NonStop SOAP 4 Deployment Directory>.

OSS> cp <output directory>/modules/mod_logging/libaxis2_mod_logging.so <NonStop SOAP 4 deployment

location>/modules/mod_logging/.

OSS> cp <output directory>/modules/mod_logging/module.xml <NonStop SOAP 4 deployment

location>/modules/mod_logging/.

The module.xml file and the libaxis2_mod_logging.so DLL file is now present in the

<NonStop SOAP 4 Deployment Directory>.

To engage the module handler at the service level, add the following entry to the services.xml

file located in the <NonStop SOAP 4 Deployment Directory>/services/empdb directory:

The value of the ref attribute of the module element must refer to the name of a directory in the

modules folder of the NonStop SOAP 4 deployment location.

136 Customizing NonStop SOAP 4 Message Processing