This section assumes a typical scenario where a Replication Server exists at both primary and replicate sites, as shown in Figure B-1. Each time a client requests a transaction that changes database content, the following actions occur:
The LTM reads the log of the primary database for transactions that are marked for replication.
The LTM forwards the transactions, through the Log Transfer Language (LTL), to the primary Replication Server (PRS in the figure), where they are stored in a stable queue.
The primary Replication Server determines, for each transaction, which of the following actions to take:
Discard the transaction if no subscriptions exist for the data.
Forward the transaction to each replicate Replication Server (RRS in the figure), where it is stored in a stable queue.
The replicate Replication Server determines, for each transaction, which of the following actions to take:
Route the transaction to another Replication Server.
Applies the transaction to replicate databases that it manages.
Figure B-1: Replication Server overview
