NonStop SOAP 4.1 User's Manual

management to work for the migrated service. The transaction management module can be
engaged at the following levels:
• Global Level
If you engage the transaction module at this level, all the services deployed in the NonStop
SOAP 4 server deployment can avail themselves of the transaction management feature.
To engage the transaction module at the global level, add the following line in the
axis2.xml file located in <NonStop SOAP 4 Deployment Directory> :
<module ref=”transaction” />
• Service Level
If you engage the transaction module at this level, the specific service will avail the
transaction management feature. To engage the transaction module at the service level,
add the line in the services.xml file located in <NonStop SOAP 4 Deployment
Directory>/services/<service_name>:
<module ref=”transaction” />
4. Generate the clients.
Generate the NonStop SOAP clients using the WSDL file generated by the SoapAdminCL
tool, as shown in Step 2. There is no change to the way clients used to access the session
management functionality using the session header block.
For more information on how to utilize the session and transaction management features in
NonStop SOAP using the session header block, see “Transaction Management” (page 236).
Because the transaction management module of NonStop SOAP completely deprecates the Cookie
file, the following NonStop SOAP 3 specific configuration parameters have also either been
deprecated or overridden.
Table 1 lists the NonStop SOAP 3 transaction management parameters and its corresponding
parameters in NonStop SOAP 4.1.
Table 1 Transaction Management Parameters in NonStop SOAP 3 and NonStop SOAP 4.1.
DescriptionNonStop SOAP 4.1
Parameter
NonStop SOAP 3 Parameter
The timeout is now restricted to individual
transactions. There is no separate timeout
for sessions.
TMFTimeoutSOAP_SESSION_TIMEOUT
This parameter is deprecated because there
is no cookie file.
NoneSOAP_COOKIE_DELETION_INTERVAL
Migrating NonStop SOAP 3 User-exits
User-exits in NonStop SOAP 3 enable you to customize the default NonStop SOAP 3 behavior.
NonStop SOAP 4 does not support user-exits but provides modules, handlers, and Message Receiver
User Functions that enable you to customize NonStop SOAP 4 message processing. Modules,
handlers, and Message Receiver User Functions are functionally equivalent to user-exits in NonStop
SOAP 3.
This section describes the migration of user-exits from NonStop SOAP 3 to NonStop SOAP 4.1.
NOTE: You must have a good understanding of modules and handlers to migrate user-exits from
NonStop SOAP 3 to NonStop SOAP 4.1. For information on Modules and Handlers, see
“Customizing NonStop SOAP 4 Message Processing” (page 124).
Modules, handlers, and Message Receiver User Functions in NonStop SOAP 4 can be engaged
at the service level and at the global level. When engaged at the service level, they enable you
Migrating NonStop SOAP 3 User-exits 61