Bookshelf Home | Contents | Index | PDF |
Siebel Remote and Replication Manager Administration Guide > About Replication Manager > Overview of Replication Manager > Hierarchy of a Replication Manager ImplementationReplication Manager is a data replication technology that copies data throughout a network of Siebel nodes. It copies data that originates in the headquarters node (HQ) to multiple regional nodes. These regional nodes are subordinate to the headquarters node. It uses a hierarchical model. A Replication Manager implementation includes a single headquarters node and one or more regional nodes. The headquarters node contains the master set of data that the regional nodes use. A regional node can possess one of the following types of relationships:
Each subordinate node is a Siebel Enterprise Server that contains a subset of users from the Siebel Enterprise Server that resides on the parent node. Figure 8 illustrates an example configuration for Siebel Replication Manager. It includes the following items:
Headquarters NodeA headquarters node is a separate Siebel Enterprise Server that includes the Siebel database, the Siebel File System, and one or more Siebel Servers. The Siebel database and file system contain the entire set of database records and file attachments that the nodes use. Siebel Servers that reside in the headquarters node manage replication to the following items:
A regional node can support connected users and remote clients that synchronize with the Siebel Server of a regional node. For more information, see About the Siebel Enterprise and the Siebel Enterprise Server. Regional NodeA regional node is a separate Siebel Enterprise Server that includes a Siebel database, Siebel Servers, and Siebel File System that support a set of connected users. The set of registered users at the regional node determines the set of connected users. Each regional node is a child of a parent node. A parent node is another Siebel Enterprise Server that is the headquarters node or another regional node. A regional node contains a full copy of data or a subset of data from the parent node. This copy includes database records and file attachments. A regional node is typically geographically separated from the headquarters node, but this configuration is not required. Replication AgentThe Replication Agent server component runs on the Siebel Server on the regional node. To keep data current at these locations, it periodically synchronizes the regional database with the parent database. Replication Agent runs as a service mode task, which is a type of task that runs continuously after it starts. Benefits of Siebel Replication ManagerReplication Manager can help solve the performance degradation that occurs if bandwidth is limited or if network latency is a problem. Placing data closer to a cluster of connected users instead of requiring data transfer from a single headquarters node can improve response time. This configuration also provides the user with continuous access to the Siebel application even if the network link to the headquarters node is not reliable or is only available intermittently. The user can synchronize with a local regional node to decrease network costs and to improve the performance and reliability of the synchronization process. Comparison Between Siebel Remote and Siebel Replication ManagerTable 23 provides a comparison between Siebel Remote and Replication Manager. |
Siebel Remote and Replication Manager Administration Guide | Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |