Reliable Transaction Router
Application Design Guide

Contents

Preface
Preface	Preface
Chapter 1
1	Introduction
Chapter 2
2	Configuration and Design
Chapter 3
3	Implementing an Application
Chapter 4
4	Design with the C++ API
Chapter 5
5	Design with the C API
Appendix A
Appendix A	RTR Design Examples
Appendix B
Appendix B	RTR Cluster Configurations
Appendix C
Appendix C	Server States
Appendix D
Appendix D	RTR C++ API Samples
Appendix E
Appendix E	RTR C API Samples
Appendix F
Appendix F	Evaluating Application Resource Requirements
Appendix G
Appendix G	Dual-Rail Setup
Index
Index
Figures
1	Reading Path
1-1	RTR Layers
2-1	Transaction Flow with Concurrent Servers and Multiple Partitions
2-2	Transaction Flow on Standby Servers
2-3	RTR Standby Servers
2-4	Transaction Flow on Shadow Servers
2-5	Two Sites with Shadowing and Standby Servers
2-6	Configuration with Quorum Node
2-7	Commit Sequence Number
2-8	CSN Vote Window for the C++ API
2-9	CSN Vote Window for the C API
2-10	Recovery after a Failure
2-11	Single-Node TPS and CPU Load by Number of Channels
2-12	Single-Node TPS and CPU Load by Message Size
2-13	Two-Node TPS and CPU Load by Number of Channels
2-14	Two-Site Configuration
2-15	Message Fan-Out
3-1	Transactional Shadow Servers
3-2	Shadow Servers and Third Common Database (not recommended)
3-3	Uncertain Interval for Transactions
3-4	Concurrent Server Commit Grouping
3-5	Transactional Messaging
3-6	Transactional Messaging Interaction
3-7	Deadly Embrace
3-8	Scenario for Distributed Deadlock
4-1	Transactional Messaging with the C++ API
4-2	C++ API Calls for Transactional Messaging
4-3	Flow of a Transaction
4-4	Accept Processing
5-1	RTR C API Calls for Transactional Messaging
5-2	MS DTC and RTR
A-1	Transportation Example Configuration
A-2	Stock Exchange Example
A-3	Banking Example Configuration
B-1	OpenVMS CI-based Cluster
B-2	Tru64 UNIX TruCluster Configuration
B-3	Windows NT Cluster
C-1	Server Events and States with Active Transaction Message Types
C-2	Server States after Standby Events
G-1	Dual-Rail Configuration with Network Cards on a Router
G-2	Dual-Rail Configuration with Network Cards on a Frontend
Tables
3-1	Backend Transaction States
3-2	Frontend Transaction States
3-3	RTR Error Codes
3-4	LOCK TABLE Statements
3-5	Summary of Locking Options
3-6	Non-Default Locking Behavior
4-1	RTR Message Types
4-2	RTRServerTransactionControllerMethods
4-3	RTRClientTransactionController Methods
4-4	Prepare Phase Server States
4-5	Commit Phase Server States
4-6	Prepare Phase Router States
4-7	Typical Server Application Transaction Sequences
5-1	RTR C API Calls by Category
5-2	RTR C API Calls
5-3	How RTR Reports Aborted Transactions
5-4	RTR Message Types
5-5	Client Action Based on Journal State
5-6	Server Participation