NonStop SOAP 4.1 User's Manual

Specifying the Order of Phase Invocation in NonStop SOAP 4 Message Processing
NonStop SOAP 4 enables you to specify the order in which the pre-defined and user-defined
phases can be invoked during a message processing cycle. To specify the invocation order of the
phases, modify the phaseorder attribute to reflect the desired order of invocation. You can also
customize user–defined phases using the phaseOrder attribute.
NOTE: For more information about the phaseOrder element attribute, see Chapter 7:
“Customizing NonStop SOAP 4 Message Processing” (page 124).
For example, to add a phase named UserPhase to the inflow after the pre-defined phases,
add the highlighted entry in the axis2c.xml file:
<phaseOrder type = “inflow”>
<!-- System pre defined phases -->
<phase name="Transport"/>
<phase name="PreDispatch"/>
<phase name="Dispatch"/>
<phase name="PostDispatch"/>
<!-- End system pre defined phases -->
<!-- User defined phases could be added here -->
<phase name="UserPhase”/>
</phaseOrder>
The services.xml File
The services.xml file describes a particular service deployed in a NonStop SOAP 4 deployment
and enables you to configure the service.
The services.xml file is located in the service directory of a particular NonStop SOAP
deployment. For example, if the deployment directory for NonStop SOAP 4 is/home/usr1/
t0865h01, and a service named test is deployed in it, the services.xml file for the test
service will be located in the /home/usr1/t0865h01/services/test directory.
OSS> cd /home/usr1/t0865h01/services/test
OSS> ls
services.xml test.wsdl
To be a valid service, each service must have a services.xml file in the service directory.
NonStop SOAP 4 provides service-level customization by allowing the services.xml file to
override the values defined globally using the axis2.xml file. Sample services.xml files are
available with the sample services distributed with NonStop SOAP 4.
The services.xml file can be generated for Pathway services using the SoapAdminCL tool.
For more information about the SoapAdminCL tool, see Chapter 10: “NonStop SOAP Tools”
(page 194).
The services.xml file is used to perform the following tasks:
• “Updating the Service Parameters” (page 183)
• “Defining Multiple SOAP Response Selection Criteria” (page 186)
• “Controlling TMF Transaction Support” (page 188)
• “Engaging a Module at the Service Level” (page 189)
• “Setting the Operation-Specific MEP” (page 189)
• “Setting the Operation-Specific Message Receiver” (page 190)
NOTE: The services.xml file is an output file produced by the SoapAdminCL tool in response
to a particular SDL file. Modifications to services.xml should be undertaken carefully, as they
will be overwritten when SoapAdminCL is subsequently run on the input SDL file.
182 NonStop SOAP 4 Configuration Files