Create Routes

Create routes at the source Replication Server.

As soon as you create a direct route between a source and destination Replication Server, the source Replication Server:
  • Creates an RSI outbound stable queue to hold messages for the destination site, and

  • Starts an RSI thread that logs in to the destination or next Replication Server in the route.

Note: You can create a route from a version 15.0 Replication Server to an older Replication Server (version 11.03 or later).

When you create either direct or indirect routes, the destination Replication Server creates and materializes subscriptions at the destination site for the replicated RSSD system tables. This process lets the destination Replication Server receive available replication definitions and function classes.

When you create an indirect route, Replication Server does not create an RSI queue. The indirect route uses the RSI outbound queues of the direct route segments that compose the indirect route.

For Replication Server to be able to begin transferring system information to the destination Replication Server, you must create direct routes before you create an indirect route.

For example, you cannot create an indirect route (1 to 3) unless you have already created two direct routes (1 to 2 and 2 to 3). You also must set up the routes in the correct order.

Order for Creating Direct and Indirect Routes
Figure 6-5 illustrates order for creating direct and indirect routes with three Replication Servers, N Y underscore R S, L O N underscore R S, and R O M underscore R S. A direct route from N Y underscore R S to L O N underscore R S and L O N underscore R S to R O M underscore R S should be created first before creating the indirect route N Y underscore R S to R O M underscore R S.
Related concepts
Replication Server Technical Overview