Before you create or modify routes, be sure you have carefully determined where routes are needed in your system. As part of the design process, you must know where each source Replication Server and its destination Replication Servers reside.
Identify which routes are direct and which are indirect. Indirect routes carry messages to destination Replication Servers through one or more intermediate Replication Servers. Using direct versus indirect routes can have a noticeable effect on system performance.
Refer to the Replication Server Design Guide for details on routing and performance issues. Also see “Routing schemes” for a general discussion of direct and indirect routes.
Once you have determined your routing scheme, you can set up the required routes based on these rules:
Replication Servers that manage databases containing primary data require direct or indirect routes to the Replication Servers that manage databases with subscriptions for the data.
Replication Servers that manage replicate databases where request functions originate require direct or indirect routes to the Replication Server managing the primary database. If no replicated functions originate in the replicate database, a route from a replicate to a primary Replication Server is not required.
Each route in an indirect route must be a direct route.
See “Indirect routes” for examples of indirect routes.
You customize function strings for system functions with class scope at the primary Replication Server for the function-string class. In this instance, you must create routes from the primary Replication Server to the Replication Server managing the databases that use the function strings.
See “System functions with function-string-class scope” on page 16 in the Replication Server Administration Guide Volume 2 for more information.
You customize error classes at the primary Replication Server. In this instance, you must create routes from the primary Replication Server to the Replication Server managing the databases that use the error mappings.
A Replication Server that you plan to assign as the new primary site for a function-string class or error class, using the move primary command, has the following requirements:
It must have routes to and from the Replication Server that is the current primary site for the class, and
It must have routes to all the same Replication Servers as the Replication Server that is the current primary site for the class
See “Changing the primary Replication Server for an error class” on page 232 in the Replication Server Administration Guide Volume 2 for more information. See also “Primary site for a function-string class” on page 30 in the Replication Server Administration Guide Volume 2.
