ページ1に含まれる内容の要旨
HP Reliable Transaction Router
Getting Started
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
ページ2に含まれる内容の要旨
© 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
ページ3に含まれる内容の要旨
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
ページ4に含まれる内容の要旨
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
ページ5に含まれる内容の要旨
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 1 RTR Reading Path............................
ページ6に含まれる内容の要旨
4–6 RTR Service Provider............................... 4–17 5–1 RTR System Management Environment ................ 5–4 5–2 RTR Runtime Environment . ......................... 5–7 Tables 1 RTR Documents . . ................................. viii 2–1 Functional and Object-Oriented Programming Compared . . . 2–8 4–1 RTR Development Interfaces and their Use.............. 4–5 vi
ページ7に含まれる内容の要旨
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
ページ8に含まれる内容の要旨
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 Describes new features, 1 Release Notes corrections, restrictions, and known problems for RTR. HP Reliable Transaction Router Provides an overview Getting Started of RTR technology and solutions, and includes the glossary that defines all RTR terms. HP Reliable Transaction Router Describes product features. Software Product Descrip
ページ9に含まれる内容の要旨
Table 1 (Cont.) RTR Documents Document Content HP Reliable Transaction Router Provides an overview 2 JRTR Getting Started of the object-oriented JRTR Toolkit including installation, configuration and Java programming concepts, with links to additional online documentation. HP Reliable Transaction Router Describes the object- C++ Foundation Classes oriented C++ interface that can be used to implement RTR object-oriented applications. HP Reliable Transaction Router Explains how to design C Applicat
ページ10に含まれる内容の要旨
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 book
ページ11に含まれる内容の要旨
Release SPD Figure 1 RTR Reading Path Notes Getting Started = Glossary System Manager Application Programmer If Java Application JRTR Design Installation Getting Guide Guide Started (Online Only) If C If C++ C Application C++ Programmer’s Foundation System Reference Classes Manager’s Manual Manual RTR Help (Online Only) = Tutorial VM-0818A-AI xi
ページ12に含まれる内容の要旨
ページ13に含まれる内容の要旨
1 Introduction This document introduces RTR and describes RTR concepts. It is intended for the system manager or administrator and for the application programmer who is developing an application that works with Reliable Transaction Router (RTR). Reliable Transaction Router Reliable Transaction Router (RTR) is failure-tolerant transactional messaging middleware used to implement large, distributed applications with client/server technologies. RTR helps ensure business continuity across multivendo
ページ14に含まれる内容の要旨
Reliable Transaction Router You use the architecture of RTR to ensure high availability and Interoperability transaction completion. RTR supports applications that run on different hardware and different operating systems. RTR applications can be designed to work with several database products including Oracle, Microsoft Access, Microsoft SQL Server, Sybase, and Informix. For specifics on operating systems, operating system versions, and supported hardware, refer to the HP Reliable Transaction Ro
ページ15に含まれる内容の要旨
Reliable Transaction Router processing system using RTR requires analysis, planning, and considered execution. RTR Continuous Computing Concepts RTR provides a continuous computing environment that is particularly valuable in financial transactions, for example in banking, stock trading, or passenger reservations systems. RTR satisfies many requirements of a continuous computing environment: • Reliability • Failure tolerance • Data and transaction integrity • Scalability • Ease of building and mai
ページ16に含まれる内容の要旨
RTR Continuous Computing Concepts • Durable For more details on transactional ACID properties, see the brief discussion later in this document in the section Transaction Integrity and refer to the HP Reliable Transaction Router Application Design Guide. RTR Terminology In addition to the terms previously defined, the following terms are either unique to RTR or redefined when used in the RTR context. If you have learned any of these terms in other contexts, take the time to assimilate their meaning
ページ17に含まれる内容の要旨
RTR Terminology • Standby server • Transactional shadowing • RTR journal • Partition • Key range •XA RTR Application An RTR application is user-written software that executes within the confines of several distributed processes. The RTR application may perform user interface, business, and server logic tasks and is written in response to some business need. An RTR application can be written in one of the supported languages, C, C++, or Java and includes calls to RTR. RTR applications are composed
ページ18に含まれる内容の要旨
RTR Terminology A server is always a server application, one that reacts to a Server client’s units of work and carries them through to completion. This may involve updating persistent storage such as a database file, toggling a switch on a device, or performing another predefined task. In the context of RTR, a server must run on a node defined to have the backend role. In other contexts, a server can be a physical system, but in RTR and in this document, physical servers are called backends or nod
ページ19に含まれる内容の要旨
RTR Terminology A node that runs client applications is called a frontend Roles (FE), or is said to have the frontend role. A node that runs server applications is called a backend (BE). Additionally, the transaction router (TR) contains no application software but acts as a traffic cop between frontends and backends, routing transactions to the appropriate destinations. The router controls the distributed RTR nodes, and takes care of two-phase commit, failover and failback. The router also elimi
ページ20に含まれる内容の要旨
RTR Terminology Figure 1–4 Facility Symbol VM-0822A-AI A facility name is mapped to specific physical nodes and their roles using the CREATE FACILITY command. Figure 1–5 shows the logical relationship between client application, server application, frontends (FEs), routers (TRs), and backends (BEs) in the RTR environment at a specific location. The database is represented by the cylinder. Two facilities are shown (indicated by the large double-headed arrows), the User Accounts Facility and the Gen
