Siebel Remote and Replication Manager Administration Guide > Siebel Replication Manager Concepts > Siebel Replication Manager Architecture >

Routing Groups and Routing Rules

Each Regional Node contains either a full replica of the parent node's Database Server and File System or a subset of that data. You choose which of these to use by associating a routing group with the regional database. Do this when you register the Regional Node in the Administration - Siebel Remote view. This will determine how much of the data from the parent node will be replicated to the Regional Database. See Registering a Regional Node for more detail about registering a regional node.

Routing group options include:

• Regional Server - Full Copy. When the regional database is assigned this routing group, all user data is replicated. The regional database is considered a full copy, or full replica, of the parent database. However, the full replica should not be used as a backup system for the headquarters node for the following reasons:
  • Some system-related data may not be replicated.
  • A regional node may require re-extraction if the parent node cannot be restored properly.
  • Not every user is replicated.
  • A regional node cannot be converted to an HQ node.

    CAUTION:  If the Headquarters Node crashes, the full replica cannot be used as a new Headquarters Node for the reasons described above.

• Regional Server - Standard. When the regional database is assigned this routing group, the data replicated to the regional database is the union of data visible to connected users assigned to the Regional Node. Siebel Replication Manager applies standard routing rules to determine what data at the parent node is replicated to the Regional Node.

There are trade-offs between these two routing groups. Table 24 describes the pluses and minuses of each group.

Also, consider the following guideline when using the Standard Regional Routing Group: if you will route more than half of the data on the parent node to the regional node, it may be more beneficial to use the Full Copy Routing Group rather than the Standard Regional Routing Group for optimal performance.

Routing rules determine the subset of Dock Object instances that Siebel Remote replicates to each Mobile Web Client. Dock objects are groupings of tables in the database that logically form Siebel business components. Dock objects are similar to business components.

Siebel applications provide pre-configured user routing rules. See Dock Objects and Routing for more information.

Routing groups cannot be modified.

NOTE:  If a dedicated user is assigned to multiple databases (one Regional or Headquarters database, and one Siebel Remote database), the data visible to that user is synchronized to each of those databases. However, a mobile user is assigned to only one database—HQ or Regional.