NonStop SOAP 4.1 User's Manual

<parameter name="MessageReceiverUserFunctions">axis2_MRUF_logging</parameter>
where,
axis2_MRUF_logging
is the name of the DLL containing the Message Receiver User Functions.
NOTE: You can also engage the module at the global level, which makes the module intercept
messages for every service. To engage the module at the global level, add the following entry in
the axis2.xml file.
<parameter name="MessageReceiverUserFunctions">axis2_MRUF_logging</parameter>
Verifying the Message Receiver User Functions Output
To verify the Message Receiver User Functions output, complete the following steps:
1. Remove the log files using the following OSS command:
OSS> cd <NonStop SOAP 4 Deployment Directory>/logs
OSS> rm –rf *
2. Set the LOG_MODE environment variable to 4 in the itp_axis2.config file to enable the
debug level log setting.
Server $Axis2c {
CWD $AXIS2_DEPLOYMENT_ROOT/bin
Env AXIS2C_HOME=$AXIS2_DEPLOYMENT_ROOT
Env LOG_MODE=4
3. Restart the iTP WebServer on which NonStop SOAP 4 is deployed, using the following
command:
OSS> <iTP WebServer Deployment Directory>/conf/restart
4. Send a request to the empdb service using the empdb HTML client.
The empdb HTML client can be accessed using the following Web address:
http://<ip address>:<port>/<url_pattern>/client/empdb/SoapPW_EmpInfo.html
where,
<ip address>:<port>
is the location of the iTP WebServer in which NonStop SOAP 4 is deployed.
url_pattern
is the pattern string specified while installing NonStop SOAP 4.
5. Verify that the following output is present in the soaperror.log file to confirm that the
Message Receiver User Functions are attached to the service:
Input buffer: <request buffer>
Output Buffer: <response buffer>
NonStop SOAP 4 is now customized to log input and output buffers using MRUFs.
152 Customizing NonStop SOAP 4 Message Processing