|
Siebel Remote and Replication Manager Administration Guide > Administering Siebel Replication Manager >
Changing the Routing Group for a Regional Server
Each regional server has a routing group associated with it. The group determines the data that will be extracted to and transactions that will be synchronized with the regional server. There may be times when you need to change the routing group for a regional server. The procedure below describes how to do this. CAUTION: Changing the routing group from "Standard" to "Full Copy" requires a reextract of the regional database. Also any Mobile Web Clients associated with the Regional Node require a reextract as well.
To change the routing group for a regional server
- If the Regional Node has Mobile Web Clients, synchronize these with the Regional Node.
- Send updates in the regional node to the HQ or parent node.
- Stop the activities on the regional node.
This means no more updating.
- From the application-level menu, choose Navigate > Site Map > Administration - Siebel Remote > Replication Servers.
- In the Parent Server form, select the appropriate node as the parent.
Usually, this is HQ.
- In the Regional Databases list, select the appropriate Server Name.
- Click the select button in the Routing Group field.
- In the Routing Model Selection dialog box, select the new Routing Group you want and click OK.
Fill in any of the other fields on the form as appropriate.
- Perform a database extract of the regional database, then initialize the regional database.
For extracting the regional database, see Extracting the Regional Database.
For initializing the regional database, see Initializing the Regional Database.
- Perform database extract of Mobile Web Clients on the new regional node, and resume normal operations on the regional node.
For extracting mobile databases, see Creating Mobile Web Client User Accounts and Privileges.
NOTE: All views are supported only on Regional Nodes that have a Routing Group of type REGIONAL SERVER - FULL COPY.
|
