NonStop SOAP 4.1 User's Manual

Example 20 The SOAP Message Body for a Sample DDL file with the @SOAP_OCCURS_DEP_ON
Tag
<complex1>
<ch2>abc</ch2>
<ch3>d</ch3>
<bin2>3</bin2>
<complex2>
<custnum>10</custnum>
<bin3>1</bin3>
<bin3>2</bin3>
<bin3>3</bin3>
</complex2>
</complex1>
In Example 20, the <bin2> element in the <complex1> structure dictates the number of <bin3>
occurrences in the <complex2> structure in accordance with the @SOAP_OCCURS_DEP_ON DDL
comment.
Hot-Deployment of the NonStop SOAP 4 Server
NonStop SOAP 4 server allows you to deploy Web services while it is operational, running, and
serving requests. The process of deploying Web services while the NonStop SOAP 4 server is
actively serving requests is known as Hot-Deployment. This feature enables you to deploy new
Web services in your NonStop SOAP 4 installation without bringing down the NonStop SOAP 4
server.
The NonStop SOAP 4 server scans all the services under the services directory of your NonStop
SOAP 4 deployment and adds the new services in the service repository.
When a client sends a request to the NonStop SOAP 4 server, the NonStop SOAP 4 server checks
the service repository and loads the services listed in the service repository. Because the service is
added to the service repository during Deployment, the DLL loader can locate the requested service
and process the client request.
The Hot-Deployment approach avoids reconfiguration downtime for businesses because the NonStop
SOAP 4 server immediately makes the service available (that is, without restarting the iTP
WebServer).
The Hot-Deployment feature is enabled by default. To disable this feature, set the hotdeployment
attribute to false in the axis2.xml file. For example, the following entry in the axis2.xml file
turns off the Hot-Deployment feature:
<parameter name=”hotdeployment” locked="false”>false< /parameter>
NOTE: The Hot-Deployment feature is applicable only for services and not for modules.
Hot-Update for the Deployed Services
The NonStop SOAP 4 server enables you to update configuration or definition of a Web service
while it is still operating, running, or serving requests. This feature enables you to make changes
to Web services in your NonStop SOAP 4 installation without bringing down the NonStop SOAP
4 server or the service.
When a client sends a request to the NonStop SOAP 4 server, the NonStop SOAP 4 server checks
the modification date of the services.xml file and the WSDL file. If either of these files are
modified, the NonStop SOAP 4 server loads the information into the service repository, which is
then used for current and subsequent requests, unless a change occurs. However, the modification
date check adds overhead to the SOAP message processing, therefore this feature is disabled by
default.
To enable this feature, set the hotupdate attribute to true in axis2.xml file. For example, the
following entry in axis2.xml file enables this feature:
Hot-Deployment of the NonStop SOAP 4 Server 229