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

Defining the Regional Node

To define each regional node, you register the regional Siebel database and then add users for this database.

To define the regional node

1. Make sure the requirements for the parent node are met.

   For more information, see Requirements for the Parent Node.

2. Make sure the requirements for the organization, territory, and Assignment Manager are met.

   For more information, see Requirements for Organization, Territory and Assignment Manager.

3. Log in to the Siebel Server with administrator privileges.

   For more information, see Logging in to the Siebel Server as an Administrator.

4. Navigate to the Administration - Siebel Remote screen, and then the Replication Servers view.
5. In the Parent Server form, choose a node as the parent.

   The Parent Server form displays the registered databases and indicates whether the Siebel database resides on a headquarters or on a regional node. You typically choose the headquarters node. The Regional Databases list displays regional nodes that are children of a parent database that is currently chosen in the Parent Server form. Only the headquarters database or a regional database can be the parent of another database. A local database cannot be a parent.

6. Right-click in the Regional Databases list, and then choose the Columns Displayed menu item.
7. In the Columns Displayed dialog box, move Description from the Available Columns window to the Selected Columns window, and then click Save.
8. In the Regional Databases list, click New.
9. In the Server Name field, enter a name for the regional database.

   For example, you can enter SIEBEL_EUROPE. For more information, see Requirements for the Siebel Server Name and Local Database Names.

10. In the Description field, type in a description of the regional database.

    For example, you can type in European Regional Database.

11. Specify the Routing Group where the regional database belongs:
    1. In the Routing Group field, click the select icon.
    2. In the Pick Routing Group dialog box, choose one of the following items:
       • Regional Server-Full Copy
       • Regional Server-Standard

         For more information, see How Replication Manager Uses Routing Groups.

    3. Click OK.
12. Save the record.
13. Add the users.

    For more information, see Requirements for Adding a User to a Regional Node.

Requirements for the Parent Node

You must configure the parent node before you can define a child of the parent node:

• If you implement a single tier of regional nodes, then the headquarters node is the parent node.
• If you implement two or more tiers of regional nodes, then the lower tier references a regional node as the parent node. Two or more tiers of regional nodes is a hierarchy of regional nodes.

  If you implement a regional node whose parent node is another regional node, then you must synchronize the parent node with the headquarters node so that the parent node contains current data. This configuration reduces the amount of data that Replication Manager must replicate after you initialize the regional node.

For more information, see Regional Node.

Requirements for Organization, Territory and Assignment Manager

Before you define a regional node, you must make sure your organization setup and territory is finished, and that Assignment Manager runs on the headquarters node. If you modify the organization and territory after you extract and initialize the regional database, then it might be necessary for you to reextract the regional database on the parent node, and then reinitialize it. If you do not reextract and reinitialize in this situation, then Replication Manager might overload the Transaction Routers.

Requirements for the Siebel Server Name and Local Database Names

Note the following requirements for the Siebel Server name and local database names:

• The name must use to a specific format. For more information, see Format That Siebel Remote Uses for the Remote Client Name, Database Name, Login ID, and Windows Password.
• The name must be unique in the headquarters node and the regional nodes.
• You cannot use the following names:
  • TXNPROC
  • OUTBOX
  • INBOX
• The name does not have to match an existing database name.

Requirements for Adding a User to a Regional Node

Note the following requirements for adding a user to a regional node:

• When defining a regional node, you must add users. These users must be connected to the regional database.
• You must specify at least one connected user for the regional node before you extract the regional database.

For more information, see Adding a User to a Regional Node.