How Siebel Replication Manager Uses Routing Groups

A routing group is associated with each Siebel Server of a regional node. It does the following:

• Determines the data that Replication Manager extracts and the transactions that it synchronizes with the Siebel Server of a regional node.

• Determines how much of the data from the parent node Replication Manager copies to the regional database.

You cannot modify a routing group.

Each regional node contains a full copy of the Siebel database in the parent node and file system, or a subset of that data. To specify the routing group that the Replication Manager uses, you can associate one of the following routing groups with the regional database:

• About the Regional Server - Full Copy Routing Group

• About the Regional Server - Standard Routing Group

To specify a routing group, you use the Administration - Siebel Remote screen when you register the regional node.

For more information about the following items:

• Registering a regional node, see Defining the Regional Node.

• Routing, see Controlling the Data That Siebel Remote Routes to Clients.

• Predefined user routing rules, see Transaction Router Server Component.