Siebel Remote and Replication Manager Administration Guide > Implementing Siebel Replication Manager >

Defining the Regional Node


Each Regional Node must be defined by registering the Regional Database and adding any mobile users for the database. After the Regional Node has been defined, you can extract the Regional Database on its parent node and initialize it.

NOTE:  After the Regional Node is extracted, you can still continue to add Mobile Web Clients to it.

  • If you are implementing a single tier of Regional Nodes, the Headquarters Node is always the parent node.
  • If you are implementing two or more tiers of Regional Nodes (called a hierarchy of Regional Nodes), the lower tiers will have Regional Nodes as their parent nodes.

NOTE:  Setup of parent nodes must be completed before you can define children for them.

Before you continue with the process of defining a Regional Node, you must finish the setup of your organization and territory structures and run the Assignment Manager on the Headquarters Node. If you make changes to the organization and territory structures after extracting and initializing the Regional Database, you may have to reextract the Regional Database on its parent node and reinitialize it. Otherwise, the transaction routers may be overloaded.

If you are implementing a Regional Node whose parent node is another Regional Node, you should synchronize the parent node with the Headquarters Node so that the parent node has up-to-date data. This reduces the amount of data to replicate after you initialize the Regional Node.

Siebel Remote and Replication Manager Administration Guide