Administering Siebel Replication Manager

This chapter describes how to administer Siebel Replication Manager. It includes the following topics:

Process of Administering Siebel Replication Manager

This process is a step in Roadmap for Implementing Siebel Remote.

To administer Siebel Replication Manager, you do the following:

The order that you use to do these steps and how often you do them might vary according to your requirements.

Adding a Connected User to a Regional Node

This topic describes how to add a connected user to a regional node.

To add a connected user to a regional node

Make sure the user is a connected user at the headquarters node.
You must add a user to the parent node before you add this user to a regional node. For more information, see Siebel Applications Administration Guide.
Locate the record for the regional database where you must add a remote client.
For more information, see Locating the Record for the Regional Database.
In the Users field, click the select icon.
In the Database Users dialog box, choose a user from the Available list, and then click Add.
Repeat Step 3 through Step 4 for each connected user that you must add to the regional node.
For more information, see Requirements for Adding a User to a Regional Node.
Click OK.
Save the record.
Create a user access account on the regional node.
A user access account is a database account or other external folder service, such as LDAP. For more information, see Siebel Security Guide.
Optional. To add more connected users, repeat Step 1 through Step 8 for each connected user.
Wait to make sure Replication Manager copies the new user data to the regional node.
Depending on your network and hardware configuration, this step might take a few hours to finish.

Locating the Record for the Regional Database

This topic describes how to locate the record for the regional database that you must administer.

To locate the record for the regional database

Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Navigate to the Administration - Siebel Remote screen, and then the Replication Servers view.
In the Parent Server form, query the Server Name field for the parent of the regional node where the regional database resides.
In the Regional Databases list, query the Server Name field for the name of the regional database that you must administer.

Adding a User to a Regional Node

This topic describes how to add a user to a regional node. For more information, see Requirements for a User on a Regional Node.

Caution: If you add a user who is assigned to the Siebel Administrator position to a regional node, then a very large download might occur. The Siebel Administrator position, including SADMIN, allows the user to do a wide variety of administrative work. It includes access to most of the views that a Siebel application displays.

To add a user to a regional node

Add the user as a connected user.
For more information, see Adding a Connected User to a Regional Node.
Add the user as a remote client.
For more information, see Adding a New Remote Client.
Repeat Step 1 and Step 2 for each user that you must add to the regional node.

Requirements for a User on a Regional Node

If a regional node supports users, then the following requirements apply:

You must first add every user on a regional node to the node as a connected user, and then add that user as a remote client.
You can assign a user to only one Siebel Server of the headquarters node or to one regional node.
If you reassign a remote client to a different parent server, then you must synchronize and then reextract that client.

Deleting a Remote Client from a Regional Node

This topic describes how to delete a remote client that resides on the regional node. You delete a remote client from a regional node in the same way that you would delete it from the headquarters node.

For more information, see Deleting a Remote Client.

Managing Synchronization for a Regional Node

During the course of operation after you complete an initial implementation of Replication Manager, it might be necessary for you to adjust how Replication Manager synchronizes a regional node.

To manage synchronization for a regional node

Use parameters of the Replication Agent server component to more closely align synchronization with your environment requirements.

For more information, see Configuring the Replication Agent Server Component.

Modifying the Routing Group for a Regional Node

You can modify the routing group for the Siebel Server of a regional node. For more information, see How Siebel Replication Manager Uses Routing Groups.

To modify the routing group for a regional node

If the regional node contains remote clients, then synchronize these clients with the regional node.
Send updates that exist in the regional node to the headquarters or parent node.
Stop any update activity on the regional node.
Locate the record for the regional database where you must modify the routing group.
The correct node for the parent in the Parent Server form is typically HQ. For more information, see Locating the Record for the Regional Database.
In the Routing Group field, click the select icon.
In the Pick Routing Model dialog box, choose the new Routing Group, and then click OK.

Caution: For important caution information about modifying the routing group from Standard to Full Copy, see Requirements for Extracting the Server Database.
Extract the regional database.
For more information, see Extracting the Regional Database.
Initialize the regional database.
For more information, see Initializing the Regional Database.
Extract the Siebel database for each remote client that exists on the new regional node.
For more information, see Extracting the Server Database.
Resume operations on the regional node.

Deactivating a Regional Node

This topic describes how to deactivate a regional node.

Caution: Make sure you do a full backup of the headquarters node and the regional nodes before you deactivate a regional node.

To deactivate a regional node

Synchronize remaining transactions of the users who are assigned to the regional node.
Make sure all transactions are applied to the regional node.
For example, make sure the Transaction Merger on the regional node has processed the DX files.
Make sure the transactions are synchronized with the headquarters node.
Move sure every user who resides on the deactivated regional node is also assigned to the headquarters node or to another regional node.
Shut down the following server components on the regional node:
- Transaction Processor
- Transaction Router
- Transaction Merger
- Replication Agent
  For more information, see Using the Command Line Interface to Administer Server Components.
Shut down the Transaction Processor and Transaction Router server components on the headquarters node.
On the headquarters node, navigate to the Administration - Siebel Remote screen, and then the Replication Servers view.
Set the Effective End Date for the regional node.
Restart the Transaction Processor and Transaction Router server components on the headquarters node.
For more information, see Using the Administrative Interface to Administer Server Components.
To make sure the connected users of the regional node reference the headquarters node, you modify the ODBC sources and the configuration file.
For more information, see Modifying the Siebel Configuration File for Siebel Remote.
Delete the deactivated docking folder for the regional node from the SIEBEL_ROOT\docking folder on the headquarters node.

Reactivating a Regional Node

You can reactivate a regional node.

To reactivate a regional node

Log in to the Siebel Server of the headquarters node with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Shut down the Transaction Processor and Transaction Router server components on the headquarters node.
Navigate to the Administration - Siebel Remote screen, and then the Replication Servers view.
Set the Effective End Date to NULL for the regional node you are reactivating.
Reextract the regional database.
For more information, see Extracting the Regional Database.
Reinitialize the regional database.
For more information, see Initializing the Regional Database.

Upgrading a Regional Node

You must distribute any object definition modifications that you make to the headquarters, regional, and local databases. This is known as a minor upgrade. Some examples of modifications to object definitions include modifications to the behavior of an application or adding extension columns to a table. You can make these Siebel Repository updates in Siebel Tools and then make sure they are part of the Siebel runtime repository in the regional database or local databases. A set of DDL (Data Definition Language) operations represents schema object modifications.

In any one schema hierarchy, each Replication Manager instance and each remote client must contain the same database schema and Siebel runtime repository. If the Siebel Server and the remote client do not contain the same Siebel runtime repository, then transactions can become corrupt. If you modify the schema or Siebel runtime repository, then you must configure Siebel Remote to upgrade each remote client during the next synchronization. This upgrade is necessary even if this modification does not affect the schema. During typical operations there can be a short moment where the Siebel Server and the remote client contain a different Siebel runtime repository.

For more information, see Overview of the Siebel Remote Architecture.

To upgrade a regional node

Thoroughly test the repository modifications and upgrade steps.
It is strongly recommended that you thoroughly test the repository modifications and upgrade steps in a separate test environment before you migrate them to a production environment.
Update and distribute the upgraded Siebel runtime repository.
Make sure each user synchronizes with the regional database.
After synchronizing, each user must not modify the local database until after you finish the upgrade. If you apply these modifications to the Siebel Server on the regional node, then problems might occur.
Wait for Replication Manager to finish applying every transaction to the regional node.
To synchronize the regional node with the parent node, run Replication Agent.
The parent node is typically the headquarters node. Do not modify the regional node until after you finish the upgrade. If you apply these to the parent node, then problems might occur.
Wait for Replication Manager to finish applying the transactions to the Siebel database on the parent node.
If necessary, disconnect all users, and then stop the server components.
All upgrades do not require this step.
Apply the upgraded Siebel runtime repository to the headquarters node.
You can distribute the Siebel runtime repository using Siebel Anywhere. For more information, see Siebel Anywhere Administration Guide.
Finish the upgrade:
- If you use Siebel Anywhere, then see Finishing the Upgrade with Siebel Anywhere.
- If you do not use Siebel Anywhere, then see Finishing the Upgrade without Siebel Anywhere.

Finishing the Upgrade with Siebel Anywhere

If you use Siebel Anywhere, then you can use it to apply schema modifications. For more information, see Siebel Anywhere Administration Guide.

To finish the upgrade with Siebel Anywhere

Restart server components, and then make the Siebel application is available to users.
Build the upgrade kit for the Siebel database schema.
Distribute the upgrade kits, and then finish the upgrade.

Finishing the Upgrade without Siebel Anywhere

If you do not use Siebel Anywhere, then you must reextract and reinitialize the regional and Remote nodes after you apply the Siebel repository modifications and synchronize the physical schema.

To finish the upgrade without Siebel Anywhere

Synchronize the repository with the physical schema.
Allow connected users at the headquarters node to reconnect and continue working using the new Siebel runtime repository.
To create a new database template on the parent node, use Generate New Database.
On the parent node, do a database extract of the regional node.
Initialize the regional node.
Allow connected users on the regional node to reconnect and to resume work using the new Siebel runtime repository.
Generate a new database template on the regional node.
Extract each remote client on the regional node.
Allow users to reinitialize their local databases and to resume work using the new Siebel runtime repository.

Language Requirements

Although the language can vary for each instance in any one hierarchy, you must create the Siebel runtime repository from the same Siebel development repository. For example, the Siebel runtime repository in a replication environment can be in a language that is different from the Siebel runtime repository in the headquarters environment, even if you generate both of these Siebel runtime repositories from the same Siebel development repository. The language that a remote client uses can be different from the language that another remote client in the same hierarchy uses even if both clients use a Siebel runtime repository created from the same Siebel development repository.

Generating Reporting Relationships

If you upgrade to a new version of the Siebel CRM software, or if the denormalized hierarchy structure becomes out of synchronization with the data in the normalized tables, then it might be necessary for you to do the Generate Reporting Relationships process. This process creates a large number of transactions for Siebel users and regional nodes. It requires significant resources of time, CPU, and memory. For more information, see Siebel Database Upgrade Guide.

Modifying Authentication for Siebel Replication Manager

To log on to the parent node, Replication Manager uses the user name and password of the administrator. When logging on, it authenticates with the parent node according to the Authentication Method that you set in the Synchronization Manager server component of the parent node. The parent node is typically the headquarters node.

The regional application servers and srvrinit use the administrator login. It is recommended that you use the same administrator user name and password on the headquarters database and on the regional databases.

To modify authentication for Replication Manager

Modify the password according to the Authentication Method.
For example, if you set the Authentication Method to Database, and if you modify the password in the Siebel database of the parent node, then you must modify the same password on the regional node. For more information, see Parameters of the Synchronization Manager Server Component, and see Siebel Security Guide.
To modify the password, use the Siebel Server on the regional node:
1. Navigate to the Administration - Server Configuration screen, Enterprises, and then the Parameters view.
2. In the Enterprise Parameters list, query the Parameter field for Password.
3. Enter a value in the Value field.
4. Stop the Siebel application services.
  For more information, see Siebel System Administration Guide.
5. Restart the Siebel application services.
The Siebel Server applies the modifications you make after the services restart. For more information, see About the Siebel Enterprise and the Siebel Enterprise Server.

Maintaining Siebel Replication Manager

This topic describes some of the management activities not addressed elsewhere in this chapter that you can do periodically to keep your Replication Manager implementation running efficiently.

Backing Up and Recovering a Database on the Headquarters Node or Regional Node

This topic describes how to backup and recover a database of the headquarters or regional node.

To back up and recover a database on the headquarters node or regional node

Make sure you do regular backups and maintenance tasks on the headquarters database and on the regional databases.
It is strongly recommended that you regularly do this work.
If a failure occurs, then do the following work:
- If a failure occurs on a regional database, and if you cannot recover it to the exact point of failure, then you must reextract the regional database on the Siebel Server at the parent node.
- If transactions are lost on the headquarters node, then you must do the following:
  - Reextract all child nodes.
  - Reextract the users who synchronize with the regional server whose regional database failed.

If you can recover the regional node to the exact point of failure, then the S_DOCK_STATUS values of the headquarters and regional nodes are synchronized. Replication Manager synchronizes the following transactions after recovery to the point of failure:

Transactions that Replication Manager had not synchronized at the time of failure
Transactions that Replication Manager created on the headquarters node and the regional nodes after the point of failure

Backing Up and Recovering the Siebel Enterprise Server

To back up the entire Siebel database or user schema, you can use an RDBMS tool that a third-party vendor provides. You must take some precautions, such as not backing up the docking folders. For more information, see 475580.1 (Article ID) on My Oracle Support, also known as Technical Note 0026.

Administering Monitoring and Logging

This topic describes how to monitor Siebel Servers and how to manage data that Replication Manager logs in the transaction log table.

Monitoring the Regional Siebel Servers

This topic describes how to monitor the regional Siebel Servers.

To monitor the regional Siebel Servers

To monitor server components and the movement of data between regional nodes and the parent node, use the following screens in the administrative interface:
- Administration - Siebel Remote
- Administration - Server Management

It is also recommended that you monitor disk space availability.

Reducing the Transaction Log Table by Expiring Obsolete Transaction Processor Tasks

It is strongly recommended that you periodically expire each obsolete Transaction Processor task. A Transaction Processor task can become obsolete in the following situations:

Replication Manager starts a Transaction Processor task on the Siebel Server but then does not use it
Replication Manager starts a Transaction Processor task and then you uninstall the Siebel Server
After an upgrade

For more information, see Troubleshooting a Large Transaction Backlog Problem.

To reduce the transaction log table by expiring obsolete transaction processors

Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Navigate to the Administration - Siebel Remote screen, and then the Processor Status view.
In the Transaction Processors list, choose the obsolete Transaction Processor.
In the End Date field, enter an end date that has already occurred.

Guidelines for Doing Administrative Work

This topic describes guidelines you can follow when doing administrative work.

Do Administrative Work on the Headquarters Node

It is recommended that you do administrative work only if you are connected to the Siebel Server of the headquarters node. Example administrative work includes configuring and deactivating remote clients when using the Administration - Replication Server view. Although you can do some administrative work on the Siebel Server of a regional node, doing so causes a delay before Replication Manager copies the data to the headquarters database and then copies it to the regional database. In this situation, a data conflict can occur.