Routes and connections allow Replication Servers to send messages to each other and to send commands to databases. A route is a one-way message stream that sends requests from one Replication Server to another Replication Server. A connection is a message stream from a Replication Server to a database. Replication Server uses a logical connection to represent the active and standby databases in a warm standby application.
To replicate data from one database into another, you must first establish the routes and connections that allow Replication Server to move the data from its source to its destination.
When you add a database to your replication system, Sybase Central or rs_init creates the connection for you. You never have to create a connection directly unless you are replicating data into a database that is not an Adaptive Server.
If you have more than one Replication Server in your replication system, you must create routes between them. If you have only one Replication Server, you do not need to create routes.
Figure 1-2 illustrates connections and routes between three Replication Servers, one database storing primary data, and four databases storing replicated data.
Figure 1-2: Routes and connections
When you create a route from a primary Replication Server to a replicate Replication Server, transactions flow from the primary server to the replicate server.
If you plan to execute replicated stored procedures in a replicate database to update a primary database, you must also create a route from the replicate Replication Server to the primary Replication Server.
