NonStop Systems Introduction

Transaction Management
NonStop Systems Introduction—527825-001
5-14
TMF Integration With the Application Server
Environments and SQL/MX
after-image shows a value of 330. The before-image for part B9 shows a value of 70
in the QOH field, while the after-image shows a value of 65.
The archive copy of the warehouse database (the copy restored from the last online
dump) does not reflect the changes made by the three transactions because the
changes occurred after the last online dump. So TMF brings the archive copy of the
database up to date as follows:
•
It changes QOH from 800 to 750 in the record for part A6.
•
It changes QOH from 240 to 330 in the record for part D7.
•
It changes QOH from 70 to 65 in the record for part B9.
Applying the after-images from the audit trail to the three archive records restores the
database to the state it was in just before the failure. File recovery has recovered the
database.
TMF Integration With the Application Server
Environments and SQL/MX
TMF plays an important role in NonStop transactional applications. The use of TMF
significantly reduces the complexity of application logic. Simple statements define
each transaction, and TMF automatically performs all auditing and transaction backout
functions for the application.
In addition, TMF is closely integrated with the transaction processing environments and
the TS/MP and SQL/MX core services. Together these products form a powerful
application environment that can support your most critical applications.
You can choose any of the transaction processing environments supported by HP: the
NonStop Tuxedo environment, the NonStop CORBA environment, or the WebLogic
Server/J2EE environment. Applications based on any of these environments and the
TS/MP (for NonStop Tuxedo and NonStop CORBA), SQL/MX, and TMF core services
meet all the demanding requirements of a ZLE application environment and relieve
programmers of the burden of writing special code for these requirements.
Programmers can concentrate on the business aspects of the application instead.
Do you have to use all these products together in every application? The answer is no.
The NonStop application environment is flexible enough to let you use any one of
these products in an application without using the others. But for maximum
performance, data integrity, and programmer productivity, your applications should take
advantage of these products.