NonStop SOAP 4.1 User's Manual

Request Processing in NonStop SOAP 4
Request processing in NonStop SOAP 4 takes place through the interaction of the following
components:
• “Flows” (page 127)
• “Phases” (page 128)
• “Handlers” (page 130)
• “Modules” (page 130)
The default message process in NonStop SOAP 4 uses only flows and phases; it does not use
handlers and modules. You can customize the default message process using handlers and modules
to meet your business requirements.
Flows
A Flow is a sequence of activities where messages flow in and out of NonStop SOAP 4.
NonStop SOAP 4 invokes the following flows based on the configured message exchange pattern
(MEP):
• inflow: invoked when a client sends a request to the service.
• infaultflow: invoked during request processing.
• outflow: invoked when a service sends a response to a client.
• outfaultflow: invoked during response processing.
Figure 13 illustrates the message process in NonStop SOAP 4.
Figure 13 Message Process in NonStop SOAP 4
Service Consumer
iTP Webserver
Message Receiver
Service Provider
Transport Phase
PreDispatch Phase
Dispatch Phase
PostDispatch Phase
Transport Phase
MessageOut Phase
Outflow
inflow
Customizing the NonStop SOAP 4 Message Process Using Handlers 127