NonStop SOAP 4.1 User's Manual
NOTE: You can 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.
<module ref =“mod_logging"/>
Verifying the Module Handler Output
To verify the module handler 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 where 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
module handler is attached to the service:
Input Message: <SOAP request XML>
Output Message: <SOAP response XML>
Customizing the NonStop SOAP 4 Message Process Using Message
Receiver User Functions
The Message Receiver phase of NonStop SOAP 4 uses the information in the services.xml file
to convert the incoming SOAP message into a Pathsend buffer and send it to the $RECEIVE queue
of the designated server class. Message Receiver User Functions (MRUFs) serve the purpose of
accessing and modifying data that are not part of the SOAP message. This includes the destination
PATHMON and the server class name or the destination process name. MRUFs also have access to
the Pathsend buffer and only MRUFs can be attached to the Message Receiver phase of NonStop
SOAP 4.
Customizing the NonStop SOAP 4 message process using Message Receiver User Functions,
involves the following tasks:
1. “Configuring NonStop SOAP 4 Message Receiver User Functions” (page 138)
2. “Modifying the Data Buffer Passed to the Service using NonStop SOAP 4 Message Receiver
User Functions” (page 139)
3. “Modifying the Pathway or Process Attributes using NonStop SOAP 4 Message Receiver User
Functions” (page 143)
Customizing the NonStop SOAP 4 Message Process Using Message Receiver User Functions 137










