NonStop SOAP 4.1 User's Manual

Example 2 A Sample services.xml Configuration File
<service name="EMPDB">
<parameter name="ServiceClass" locked="xsd:false">EMPDB</parameter>
<!--Uncomment to specify static WSDL path-->
<parameter name="wsdl_path">/home/usr1/t0865h01/services/empdb_p
athway/SoapPW_EMPSVR.wsdl</parameter>
<parameter name="pathmon">$AXIS</parameter>
<parameter name="serverclass">EMPDB</parameter>
<description>
Service template file
</description>
<operation name="EmpInfo">
<messageReceiver class="axis2_pway_receiver" />
<parameter name="TMFTransactionSupport">Supports</parameter>
<parameter name="TotalResponse">2</parameter>
<parameter name="Response0">EmpInfoResponse0</parameter>
<parameter name="Response0_Default">yes</parameter>
<parameter name="Response1">EmpInfoResponse1</parameter>
<parameter name="Response1_StartIndex">0</parameter>
<parameter name="Response1_EndIndex">2</parameter>
<parameter name="Response1_BufferValue">00</parameter>
<parameter name="Response1_ComparisonOp">eq</parameter>
<parameter name="Response1_ConversionOp">string</parameter>
<parameter name="Response1_Fault">yes</parameter>
</operation>
</service>
Engaging a Module at the Service Level
A module can be attached at the service level so that its handlers are invoked every time a service
is called. A module can be attached with a service using the module element. This element specifies
the module that is referenced by the service. The sample syntax for the module element is:
<module ref="module class name"/>
where,
ref
is the attribute that accepts the module name of the module being referenced. This is a
mandatory attribute.
Setting the Operation-Specific MEP
The operation-specific MEP information for a service can be specified using the operation
element. The sample syntax for the operation element is:
<operation name="operation-name" mep="mep-uri">
</operation>
where,
name
is the operation name specified in the WSDL file for the service. This is a mandatory attribute.
The services.xml File 189