Availability Guide for Application Design

Availability Guide for Application Design—525637-004
6-1
6
Availability in the Pathway
Transaction-Processing
Environment
This section provides an overview of the availability features in the Pathway
transaction processing environment. Described here are the traditional HP products
and interfaces that support client/server or requester/server applications.
Like any transaction processing environment, the purpose of the Pathway transaction-
processing environment is to manage resources, including ensuring that resources are
available. It collects requests from a wide range of sources (client processes and
requester processes) and distributes those requests among resources.
Figure 6-1 on page 6-2 shows the relationships among the products and interfaces that
support the Pathway environment.
The NonStop Transaction Services/MP (NonStop TS/MP) product is central to the
Pathway environment. It provides support for the server part of the application; refer to
NonStop TS/MP and Highly Available Server Processes on page 6-4 for an overview.
The following products and interfaces provide services to the client or requester:
•
The Pathway/XM product provides support for automation and management of
very large NonStop TS/MP client/server environments. Refer to Pathway/XM and
Highly Available Server Classes on page 6-8.
•
The RSC/MP products provide support for client processes that run on a PC,
Macintosh, or other workstation. Refer to Availability Through RSC/MP on
page 6-11.
•
The Pathsend interface enables you to develop and run requester processes in
any supported language, often to provide message processing for remote client
processes. Refer to Availability Through Pathsend on page 6-18.
•
The Pathway (Pathway/iTS) product allows you to develop and execute terminal-
based requester programs in COBOL. This product also allows you to convert a
SCREEN COBOL application to a web client and then build and deploy the
resulting client in a Pathway environment. Refer to Availability Through
Pathway/iTS on page 6-24.
Note. This manual uses the term “client process” to refer to the part of an application that runs
on some other vendor’s hardware such as a PC, Macintosh, UNIX workstation, or mainframe
computer system and makes requests of a server process. The term “requester
” is used to
refer to that part of an application that runs on an HP NonStop system and makes requests of
a server process. While a requester process is conceptually the same as a client process, the
term “requester” is retained for historical reasons.