Availability Guide for Application Design
Availability Guide for Application Design—52563-004
xiii
About This Guide
The Availability Guide for Application Design provides an overview of application
availability options available to designers and developers. The described options
support both the business function of the application and the instrumentation of the
application.
The guide tells you how to design as much availability as you need into your
application. Your HP NonStop™ system already provides you with the most highly
available system services of any commercially available computer system and does so
with minimal overhead. By selecting the availability options you need as described in
this guide, your application can become as available as the system it runs on.
For the most part, the guide assumes that the reader is designing a new application.
Some of the information, however, will also be useful to readers who are redesigning or
adding function to existing applications.
After reading this guide, you should be able to:
•
Understand the concepts of available applications well enough to lead teams of
developers
•
Understand which of the alternative approaches to application design could work
for your specific availability needs
•
Understand the benefits and compromises each approach brings to the availability
needs of your business objectives
•
Understand which approaches to application design support availability
•
Provide application developers with check lists or other instructions on how to go
about developing the design of the application, coding the application, or testing
the application with respect to availability
•
Easily find the additional information needed to develop the application
After helping you select the right approach for your business needs, this guide refers
you to the appropriate programming manual. The guide also provides references to
other manuals that provide complete overviews of products and subsystems that are
introduced in this manual from the viewpoint of availability only.
The guide assumes that you are using either a TNS/R or TNS/E system for
development and will execute the programs on that same series system. If you wish to
develop on one series and execute on the other, remember that the loadfiles and the
supporting run-time libraries and environments are different. The NonStop Application
Environment on page 1-10 provides an overview of the architecture of both series and
some application migration issues.