Compaq Reliable Transaction Router manual Standby Server Configurations Anonymous clients Tunnel

Page 32

RTR Server Types

Standby Server Configurations

Anonymous clients

Tunnel

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.

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.

RTR supports anonymous clients, that is, clients can be set up in a configuration using wildcarded node names.

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–22Introduction

Image 32
Contents Reliable Transaction Router Getting Started Page Contents Reliability Features Figures Page Document Structure PrefacePurpose of this Document Related Documentation For all usersReading Path Readers Comments= Tutorial System Manager Application ProgrammerIf V2 to Introduction Reliable Transaction RouterRTR Continuous Computing Concepts RTR Continuous Computing ConceptsRTR Terminology RTR TerminologyClient Symbol Server Symbol Roles Symbols Components in the RTR Environment Nontransactional messaging Transaction ID Controller Business Logic Odbc Model Database ServerApplication Presentation PC Browser RTR FrontendBrowser Journal11 RTR Deployed on Three Nodes 12 Standby Server Configuration 13 Transactional Shadowing Configuration RTR Server Types RTR Server TypesStandby server Standby in a cluster 15 Standby Servers 16 Shadow Servers 17 Concurrent Servers Server1 Server2 Server3 Server4Transaction Partition a19 Bank Partitioning Example Standby Server Configurations Anonymous clients Tunnel RTR Networking Capabilities RTR Networking CapabilitiesPage Architectural Concepts Three-Layer ModelThree-Layer Model Three Layer ModelRTR Facilities Bridge the Gap BroadcastsFlexibility and Growth RTR Facilities Bridge the GapTransaction Integrity Flexibility and GrowthPartitioned Data Model Partitioned Data ModelObject-Oriented Programming Object-Oriented Programming Partitioned Data ModelObjects Functional and Object-Oriented Programming ComparedMessages Class Relationships Example 2-1 Objects-Defined SamplePolymorphism Object Implementation Benefits XA Support XA SupportReliability Features ServersFailover and Recovery Failover and RecoveryRecovery Scenarios Backend Recovery Router Recovery Frontend Recovery Recovery ScenariosPage RTR Interfaces RTR Management Station RTR Management Station RTR Create Facility DESIGN/ALLROLES=NODEA RTR RTRRECEIVEMESSAGE/TIME=0 RTR RTRSTARTTX/CHAN=C Application Programming Interfaces InterfaceApplication Programming Interfaces RTR Browser InterfaceRTR C Example of an open channel call in an RTR client program RTR Environment RTR System Management EnvironmentRTR System Management Environment RtrcomservRTR System Management Environment Management Station Running Browser SoftwareMonitoring RTR RTR Runtime Environment Optional External Applet Not Running RTR Runtime EnvironmentClient Application Whats Next? Whats Next?Page Glossary Branch BroadcastCallout server ChannelCommon classes Concurrent serverData marshalling Data objectFault tolerant EndianEvent Event drivenFrontend InquorateJournal Key rangeMessage Message handlerMultichannel MultithreadedPrimary ProcessProperties Property classesRollback RouterRTR configuration RTR environmentShadow StandbyTransaction Transaction controllerTransactional shadowing Two-phase commitTransactional message Index Index-1Index-2