HP Reliable Transaction Router Getting Started page 58

RTR Interfaces
•
•
The RTR application programming interfaces, where available,
are identical on all hardware and operating system platforms
that support RTR. The object-oriented C++ API is fully described
in the HP Reliable Transaction Router C++ Foundation Classes
manual. The C-programming API is fully described in the
HP Reliable Transaction Router C Application Programmer's
Reference Manual. Both APIs are used in examples in the HP
Reliable Transaction Router Application Design Guide. The
Java J2EE interface is described in the JTA material in the
RTR JRTR kit. The XA interface is described in materials from
X/Open.
The transaction processing environment poses special challenges
Application
for the development of applications, challenges best addressed
Development
by following a defined methodology such as the software
development life cycle or object-oriented design fleshed out with
use cases.
The software development life cycle consists of the following
phases that are to be viewed as iterative:
•
•
•
•
•
•
4–4 RTR Interfaces
An interface that enables use of an X/Open Distributed
Transaction Processing-conformant resource manager
This interface, invoked through the RTR management
interfaces, enables RTR applications to be used with
X/Open-compliant resource managers such as Oracle8.
The OpenVMS API containing OpenVMS calls
This API, supported on OpenVMS only, is obsolete for new
development. To take advantage of new RTR features and
capabilities, such applications can be rewritten with one of
the newer APIs. Older applications will continue to run with
later versions of RTR.
Gathering requirements (what is needed?)
Developing a high-level design (what will the transaction
processing application do?)
Constructing a detailed design (explicitly, what will each part
of the application do and what are its intended results?)
Coding and unit testing
Integration and system testing/deployment
Maintenance