beautypg.com

HP Reliable Transaction Router User Manual

Page 4

background image

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