NonStop SOAP 4.1 User's Manual

E Transaction Management Model in NonStop SOAP 3
and NonStop SOAP 4
The transaction management model followed by NonStop SOAP 4 is different from the transaction
management model of NonStop SOAP 3.
“Transaction Management Models in NonStop SOAP 3 and NonStop SOAP 4” (page 398) highlights
the differences between NonStop SOAP 3 Transaction Management Model and the NonStop
SOAP 4 Transaction Management model.
Table 26 Transaction Management Models in NonStop SOAP 3 and NonStop SOAP 4
NonStop SOAP 4 Transaction Management ModelNonStop SOAP 3 Transaction Management Model
Dummy session ID has no bearing on transactionsPersistent session object encapsulates all transactions
Transaction ID is exposed to the client.Session ID is exposed to the client
Cookie file is not maintained.Cookie file is maintained
Two distinct SOAP header blocks are used for handling
sessions and transactions.
Single SOAP header block is used for handling sessions
and transactions
Transaction management, implemented as a module, can
be detached from the NonStop SOAP 4 server.
Session management is permanently implemented in the
SOAP server object.
The TMFTransactionSupport attribute accepts the
following values:
The TMFTransactionSupport attribute accepts the
following values:
• Required• yes
• •no Supports
• Never
398 Transaction Management Model in NonStop SOAP 3 and NonStop SOAP 4