The sample replication system replicates the changes made to two tables
in the pubs2 database from one Adaptive Server to another Adaptive
Server.
You can set up this example as an introduction to using Replication Server
or to test your replication system installation.
Note: The application architecture for this example is similar to the
decision-support model described in the Replication Server Design Guide.
The goal of this replication system is to replicate all changes made to the
authors and titles tables in the pubs2 database in one Adaptive Server to
the same tables in the pubs2 database in another Adaptive Server.
The replication system has two Adaptive Servers:
- A primary Adaptive Server, named TOKYO_DS, holds the RSSD for
the primary Replication Server and the primary pubs2 database.
- The replicate Adaptive Server, named SYDNEY_DS, holds the
RSSD for the replicate Replication Server and the replicate pubs2
database.
The replication system has two Replication Servers:
- A primary Replication Server named TOKYO_RS manages the primary
pubs2 database.
- A replicate Replication Server named SYDNEY_RS manages the
replicate pubs2 database.
The replication system has two RepAgents, which are the Replication Agents
for Adaptive Server:
- A RepAgent for the primary RSSD runs in the ASE TOKYO_RSSD and
transfers the RSSD log to the primary Replication Server.
- A RepAgent for the primary pubs2 database runs in the ASE
TOKYO_PUBS2 and transfers the pubs2 log to the primary Replication
Server.