Compaq Reliable Transaction Router Network Router User Manual


 
RTR Server Types
but strictly speaking, the key range defines the partition. A
partition has both a name, its partition name, and an identifier
generated by RTR the partition ID. The properties of a
partition (callout, standby, shadow, concurrent, key segment
range) can be defined by the system manager with a CREATE
PARTITION command. For details of the command syntax, see
the RTR System Manager’s Manual.
A significant advantage of the partitioning shown in the bank
example is that you can add more account numbers without
making changes to your application; you need only add another
server and disk drive for the new account numbers. For example,
say you need to add account numbers from 90,000 to 99,999 to
the basic configuration of Figure 1–19, Bank Partitioning
Example. You can add these accounts and bring them on line
easily. The system manager can change the key range with a
command, for example, in an overnight operation, or you can
plan to do this during scheduled maintenance.
A partition can also have multiple standby servers.
Standby Server
Configurations
A node can be configured as a primary server for one key range
and as a standby server for another key range. This helps
to distribute the work of the standby servers. Figure 1–20
illustrates this use of standbys with distributed partitioning.
As shown in Figure 1–20, Application Server A is the primary
server for accounts 1 to 19,999 and Application Server B is the
standby for these same accounts. Application Server B is the
primary for accounts 20,000 to 39,999 and Application Server A
can be the standby for these same accounts (not shown in the
figure). For clarity, account numbers are shown only for primary
servers and one standby server.
Anonymous clients
RTR supports anonymous clients, that is, clients can be set up in
a configuration using wildcarded node names.
Tunnel
RTR can also be used with firewall tunneling software, which
supports secure internet communication for an RTR connection,
either client-to-router, or router-to-backend.
1–22 Introduction