HP Reliable Transaction Router User manual

HPReliableTransactionRouter
GettingStarted
Order Number: AA-RLE1C-TE
June 2005
This document introduces HP Reliable Transaction Router and describes its
concepts for the system manager, system administrator, and applications
programmer.
Revision/Update Information: This manual supersedes Reliable
Transaction Router Getting Started,
Version 4.2.
Software Version: HP Reliable Transaction Router Version
5.0
Hewlett-Packard Company
Palo Alto, California

© Copyright 2003, 2005 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession,
use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data
for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
The information contained herein is subject to change without notice. The only
warranties for HP products and services are set forth in the express warranty
statements accompanying such products and services. Nothing herein should
be construed as constituting an additional warranty. HP shall not be liable for
technical or editorial errors or omissions contained herein.
Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.
Intel and Itanium are trademarks or registered trademarks of Intel Corporation
or its subsidiaries in the United States and other countries.
UNIX is a registered trademark of The Open Group. Java is a US trademark
of Sun Microsystems, Inc.
This document was prepared using DECdocument, Version 3.3-1B.

Contents
Preface ..................................................... vii
1 Introduction
Reliable Transaction Router . . ........................... 1–1
RTR Continuous Computing Concepts . . ................... 1–3
RTR Terminology . . ................................... 1–4
RTR Server Types . ................................... 1–17
RTR Networking Capabilities ........................... 1–26
2 Architectural Concepts
The Three-Tier Architecture . ........................... 2–1
RTR Facilities Bridge the Gap ........................... 2–3
Broadcasts .......................................... 2–4
Flexibility and Growth ................................. 2–4
Transaction Integrity .................................. 2–5
The Partitioned Data Model . . ........................... 2–6
Object-Oriented Programming ........................... 2–6
Objects .......................................... 2–8
Messages ........................................ 2–9
Class Relationships ................................ 2–9
Polymorphism . ................................... 2–10
Object Implementation Benefits....................... 2–10
Java Support ........................................ 2–11
XA Support ......................................... 2–11
iii

3 Reliability Features
RTR Server Types .................................... 3–1
Failover and Recovery . ................................ 3–2
Router Failover . . . ................................ 3–2
Recovery Scenarios .................................... 3–3
Backend Recovery . ................................ 3–3
Router Recovery . . ................................ 3–3
Frontend Recovery ................................ 3–4
4 RTR Interfaces
RTR Management .................................... 4–6
RTR Administrator ................................ 4–6
RTR Command Line Interface ........................ 4–10
Application Programming Interfaces ...................... 4–16
RTR Java Object-Oriented Interface . . . ................ 4–16
RTR C++ Object-Oriented Programming Interface . . ....... 4–18
RTR C Programming Interface ....................... 4–21
5 The RTR Environment
The RTR System Management Environment ................ 5–1
Monitoring RTR . . . ................................ 5–3
Transaction Management ............................ 5–4
Partition Management .............................. 5–5
RTR Runtime Environment ............................. 5–6
What’s Next? ........................................ 5–7
Glossary
Index
Examples
2–1 Objects-Defined Sample ............................. 2–9
4–1 The user issues the following commands on the server
application where RTR is running on the backend. . ....... 4–12
4–2 When the next command is issued, RTR waits for the
message from the client, which does not appear until after
the client sends it (Example 4-3). ...................... 4–13
iv

4–3 Commands and system response at client. ............... 4–14
4–4 The following lines arrive at the client from RTR after the
user enters commands at the server. ................... 4–15
4–5 Creating a Facility with the C++ API .................. 4–20
4–6 Starting RTR with the C++ API ....................... 4–21
4–7 Creating a Facility with the C++ API .................. 4–21
4–8 Creating a Partition with the C++ API ................. 4–21
Figures
1RTR Reading Path ................................. xi
1–1 Client Symbol . ................................... 1–5
1–2 Server Symbol . ................................... 1–6
1–3 Roles Symbols . ................................... 1–7
1–4 Facility Symbol ................................... 1–8
1–5 Components in the RTR Environment .................. 1–8
1–6 Two-Tier Client/Server Environment ................... 1–11
1–7 Three-Tier Client/Server Environment .................. 1–11
1–8 Browser Applet Configuration ........................ 1–12
1–9 RTR with Browser, Single Node, and Database . .......... 1–13
1–10 RTR Deployed on Two Nodes ......................... 1–13
1–11 RTR Deployed on Three Nodes ....................... 1–14
1–12 Standby Server Configuration ........................ 1–15
1–13 Transactional Shadowing Configuration ................. 1–16
1–14 Standby Servers ................................... 1–19
1–15 Shadow Servers ................................... 1–20
1–16 Concurrent Servers ................................ 1–21
1–17 A Callout Server .................................. 1–22
1–18 Bank Partitioning Example .......................... 1–24
1–19 Standby with Partitioning ........................... 1–25
2–1 The Multitier Model ................................ 2–2
2–2 Partitioned Data Model . . ........................... 2–7
4–1 RTR Administrator ................................ 4–2
4–2 RTR Command Line Interface ........................ 4–3
4–3 RTR Manager . . ................................... 4–7
4–4 RTR Explorer: View of All Facilities ................... 4–8
4–5 RTR Explorer: View of One Facility ................... 4–9
v

4–6 RTR Service Provider ............................... 4–17
5–1 RTR System Management Environment ................ 5–4
5–2 RTR Runtime Environment . . ........................ 5–7
Tables
1RTR Documents . . . ................................ viii
2–1 Functional and Object-Oriented Programming Compared . . . 2–8
4–1 RTR Development Interfaces and their Use .............. 4–5
vi

Preface
Purpose of this Document
The goal of this document is to assist an experienced system
manager, system administrator, or application programmer to
understand the Reliable Transaction Router (RTR) product.
Document Structure
This document contains the following chapters:
• Chapter 1, Introduction, provides information on RTR
technology, basic RTR concepts, and RTR terminology.
• Chapter 2, Architectural Concepts, introduces the RTR
three-tier model and explains the use of RTR functions and
programming capabilities.
• Chapter 3, Reliability Features, highlights RTR server types
and failover and recovery scenarios.
• Chapter 4, RTR Interfaces, introduces the management and
programming interfaces of RTR.
• Chapter 5, The RTR Environment, describes the RTR
system management and runtime environments, and
provides explicit pointers to further reading in the RTR
documentation set.
vii

Related Documentation
Table 1 describes RTR documents and groups them by
audience.
Table 1 RTR Documents
Document Content
For all users:
HP Reliable Transaction Router
Release Notes1Describes new features, corrections, restrictions, and
known problems for RTR.
HP Reliable Transaction Router
Getting Started
Provides an overview
of RTR technology and
solutions, and includes the
glossary that defines all
RTR terms.
HP Reliable Transaction Router
Software Product Description
Describes product features.
For the system manager:
HP Reliable Transaction Router
Installation Guide
Describes how to install
RTR on all supported
platforms.
HP Reliable Transaction Router
System Manager’s Manual
Describes how to configure,
manage, and monitor RTR.
For the application
programmer:
HP Reliable Transaction Router
Application Design Guide
Describes how to design
application programs for
use with RTR, with both
C++ and C interfaces.
1Distributed on software kit.
(continued on next page)
viii

Table 1 (Cont.) RTR Documents
Document Content
HP Reliable Transaction Router
JRTR Getting Started 2Provides an overview of the object-oriented
JRTR Toolkit including
installation, configuration
and Java programming
concepts, with links
to additional online
documentation.
HP Reliable Transaction Router
C++ Foundation Classes
Describes the object-
oriented C++ interface that
can be used to implement
RTR object-oriented
applications.
HP Reliable Transaction Router
C Application Programmer’s
Reference Manual
Explains how to design
and code RTR applications
using the C programming
language and the RTR
C API. Contains full
descriptions of the basic
RTR API calls.
2In downloadable kit.
You can find additional information about RTR, including the
Software Product Descriptions, on the RTR website found
through http://www.hp.com links to middleware products or at
http://www.hp.com/go/rtr .
Reader’s Comments
HP welcomes your comments on this manual. Please send
comments to either of the following addresses:
Internet [email protected]
Postal Mail Hewlett-Packard Company
RTR Documentation Group, ZKO3-4/Y17
110 Spit Brook Rd.
Nashua, NH 03062-2698
ix

Conventions
This manual adopts the following conventions:
Convention Description
New term New terms are shown in bold when
introduced and defined. All RTR terms
are defined in the glossary at the end of
this document.
User input User input and programming examples
are shown in a monospaced font.
Boldface monospaced font indicates
user input.
Terms and titles Terms defined only in the glossary are
shown in italics when presented for
the first time. Italics are also used for
titles of manuals and books, and for
emphasis.
FE RTR frontend
TR RTR transaction router or router
BE RTR backend
Refer to . . . References another manual.
See . . . References another part of this manual.
Reading Path
The reading path to follow when using the Reliable Transaction
Router information set is shown in Figure 1.
x