NonStop SOAP 4.1 User's Manual

Message Receiver User Functions

In the NonStop SOAP 4 architecture, a message receiver converts the incoming SOAP request

from the NonStop SOAP 4 internal format (AXIOM node) to a format that is compatible with the

deployed service.

NonStop SOAP 4 supports the following message receivers:

• Pathway message receiver: used to invoke services running as Pathway applications or NonStop

processes.

• Raw XML message receiver: used when the service is developed using NonStop SOAP 4

service APIs and is implemented as a DLL.

NOTE: MRUF can be attached only to the pathway message receiver.

The message receiver is attached by NonStop SOAP 4 during service invocation and is configured

using the messageReceiver element in the axis2.xml or services.xml configuration file.

For example:

NonStop SOAP 4 allows you to customize or extend the default behavior of the Pathway message

receiver using Message Receiver User Functions (MRUF). MRUFs enable you to modify the message

buffer, Pathway, or NonStop process service invocation attributes, and customize the message

flow in the Pathway message receiver phase. MRUFs can be attached at the global level, which

means that the MRUF is called for every service invocation in a NonStop SOAP 4 deployment, or

at the service level, which means that the MRUF is called only when a particular service in invoked.

For more information about customizing the Pathway message receiver, see “Customizing the

NonStop SOAP 4 Message Process Using Message Receiver User Functions” (page 137).

NonStop SOAP 4 Message Processing Customization

NonStop SOAP 4 allows you to customize the default message process using user-defined phases,

modules, handlers, and MRUFs attached to the Pathway message receiver.

Figure 12 shows the execution points where handlers can be attached to the default NonStop

SOAP 4 message process to customize its behavior.

Overview 125