NonStop SOAP User's Manual

NonStop SOAP User-Exits

NonStop SOAP User’s Manual—520501-012

C-6

Nonstop Soap Server User-Exit Processing Flow

Figure C-2 shows how the normal processing flow within the NonStop SOAP server is

modified when user-exits are utilized. The specific purpose of each of the user-exits is

as follows:

Pre_Process() User-Exit

Input: SOAP Request XML document

Output: SOAP Request XML document

The following actions are associated with Pre_Process() user-exit:

Invoked before parsing the input SOAP Request XML document

Allows the input SOAP Request XML document to be modified

Allows to skip default parsing of the XML document using the skipParse()

method

Allows to skip the default service invocation using the skipService()

method

The Pre_Process() user-exit is invoked when the SOAP Request XML document is

received. The Pre_Process() user-exit generally implements the skipService()

or skipParse() methods.

If the skipService() method is called, the default NonStop SOAP Service()

function will be bypassed. It is mandatory to implement the Pre_Service() user-exit

in this case.

To skip the default parsing of the SOAP Request XML document, the skipParse()

function may be used. The skipParse() function is used to avoid the processing

involved in parsing the XML document for correctness when the user is confident about

the correct format of the XML document.

Pre_Service() User-Exit

Input: SOAP Request structure

Output: if not skipService()—SOAP Request structure

if skipService()—SOAP Response structure

The following actions are associated with the Pre-Service user-exit:

Invoked before the NonStop SOAP server sends the request to the service

provider

Allows the SOAP Request structure to be modified

Allows an alternate service provider to be invoked