NonStop SOAP 4.1 User's Manual

class [axis2_pway_receiver | axis2_receivers ]
is the Message Receiver class to be attached with NonStop SOAP 4. This is a mandatory
attribute.
The NonStop SOAP 4 distribution supports the following Message Receivers:
axis2_pway_receiver
specifies the Pathway Message Receiver to be used for communication with NonStop
processes or Pathway services. The default value is axis2_pway_receiver.
axis2_receivers
specifies the XML Message Receiver to be used for services developed using server APIs.
mep [IN-OUT | IN-ONLY ]
specifies the message exchange pattern to be used when communicating with the client. This
is a mandatory attribute. The default value is IN-OUT.
Attaching a Module at the Global Level
A module can be attached at the global level so that its handlers are invoked every time a service
is called in the NonStop SOAP 4 deployment. For more information about modules, see Chapter 7:
“Customizing NonStop SOAP 4 Message Processing” (page 124).
The module element in the axis2.xml file is optional and is used to attach a particular module
with NonStop SOAP 4. This module is attached globally and will be invoked on every service
request.
For example, to globally add a new module, mod_logging, add the following entry in the
axis2.xml file.
<module ref="mod_logging"/>
where,
ref
is the attribute that accepts the module name of the module being referenced.
NOTE: To attach a module, the module DLL must be added to the /modules directory in the
NonStop SOAP 4 deployment directory. In the mod_logging example, the DLL object of
mod_logging is located in the <NonStop SOAP 4 Installation
Directory>/sample_services/modules/mod_logging directory.
Attaching Message Receiver User Functions at the Global Level
A Message Receiver User Function can be attached at the global level so that it is invoked every
time a service is called in the NonStop SOAP 4 deployment. For more information about the
Message Receiver User Function, see Chapter 3: “Migrating NonStop SOAP 3 Services to NonStop
SOAP 4 or Higher Versions” (page 52).
For example, to add a new Message Receiver User Function axis2_MRUF_log globally, add the
following entry in the axis2.xml file.
<parameter name="MessageReceiverUserFunctions">axis2_MRUF_log</parameter>
where,
axis2_MRUF_log
is the class name of the Global Message Receiver User Function.
The parameter element in the axis2.xml file is optional and is used to define the custom
parameters in NonStop SOAP 4. The MessageReceiverUserFunctions parameter is used
to define DLLs, which are attached as Message Receiver User Functions. If the parameter is defined
in axis2.xml file, then the Message Receiver User Functions are attached globally and invoked
on every service request.
The axis2.xml File 181