Availability Guide for Application Design

Contents
Availability Guide for Application Design—525637-004
iv
5. Increasing the Availability of Tuxedo Applications
4. Data Protection and Recovery (continued)
The Problem 4-24
Possible Solutions 4-24
Solution Using NonStop Operating System in Support of NetBatch-Plus
Software 4-25
Solution Using Low-Priority Transaction Processing to Perform the Batch
Function 4-26
Solution Using a Database Snapshot 4-29
5. Increasing the Availability of Tuxedo Applications
Overview of Open Transaction Processing 5-1
Availability Concepts Used in Open Applications 5-2
High-Availability NonStop Tuxedo Applications 5-3
How Does NonStop Tuxedo Work? 5-4
Availability of NonStop Tuxedo Applications 5-6
Design Implications for NonStop Tuxedo Applications 5-12
6. Availability in the Pathway Transaction-Processing
Environment
Availability Concepts Used in Pathway Applications 6-2
NonStop TS/MP and Highly Available Server Processes 6-4
What Is NonStop TS/MP? 6-4
Availability of NonStop TS/MP Server Processes 6-4
Design Implications for Server Processes 6-7
Pathway/XM and Highly Available Server Classes 6-8
What Is Pathway/XM? 6-8
Availability of Pathway/XM Server Classes
6-10
Design Implications for Server Processes
6-11
Availability Through RSC/MP 6-11
How Does RSC/MP Work? 6-12
Design Implications for RSC/MP Applications 6-16
Availability Through Pathsend 6-18
How Does the Pathsend Facility Work? 6-18
Availability of Pathsend Applications 6-20
Design Implications for Pathsend Requesters 6-23
Availability Through Pathway/iTS 6-24
How Pathway/iTS Works 6-24
Availability of TCP Applications 6-26
Design Implications for TCP Requesters 6-27