Siebel Remote and Replication Manager Administration Guide > About Siebel Remote > Siebel Remote Architecture >

Siebel Server Usage

This topic describes how Siebel Remote uses the Siebel Server. For a visual representation of where some of these components reside on the Siebel Server, see Flow of Data Through the Architecture.

About Redundant Disks on the Siebel Server

Each Siebel Server manages a distinct group of users who Siebel Remote assigns to that specific server. Other applications, such as Oracle's Siebel Enterprise Integration Manager (EIM), might run on the same Siebel Server.

To maintain a high level of integrity and availability, the Siebel Server provides an interim storage area for the data that Siebel Remote requires to synchronize a local database with the Database Configuration Utilities. It is recommended that you use a redundant disk configuration for the Siebel Server. Using redundant disk configuration reduces the likelihood that malfunctioning hardware will result in a loss of data on the Siebel Server. If a malfunction does occur, then you can reextract all remote clients that are registered on the affected Siebel Server.

Server Directories for the Remote Client

Each registered remote client requires a separate directory on the Siebel Server. The Database Extract server component creates the appropriate directory and subdirectories for each client.

CAUTION:  The installation program creates a directory named txnproc in the SIEBEL_ROOT\docking directory. You must not modify the contents of this directory under any circumstances.

The following example includes a portion of the tree of the Siebel Server directory after Siebel Remote extracts databases for remote clients named Adams and Scott:

siebel
   docking
      adams
         inbox
         outbox
      scott
         inbox
         outbox
      txnproc

Server Components That Siebel Remote Uses

Table 4 lists the main server components that Siebel Remote uses. For more information, see Server Component Parameters.

Generate New Database Server Component

The Generate New Database server component creates the local database template for a given schema version of the server database. It reads the schema definition from the SRF and then creates Siebel tables and indexes in a database template file that Siebel Remote stores in the SIEBEL_ROOT\dbtempl directory. The Local Database Initialization program uses the local database template when it initializes a new database on the remote client. For more information, see Running the Generate New Database Server Component.

Dictionary Data That Supports Multiple Languages

The Dicdata.dat file and the diccache.dat file are the same dictionary file. Siebel Remote names the Dicdata.dat file differently for the remote client. These files store metadata about schema definitions, visibility rules, and other items. The Generate New Database server component copies the diccache.dat file to the dicdata.dat file in the dbtempl directory. Siebel Remote downloads the dicdata.dat file to the remote client and uses it during synchronization when it applies transactions to the local database. For help with interchanging the dicdata.dat file between remote clients to support different languages, see Getting Help from Oracle.

Database Extract Server Component

The Database Extract server component creates a snapshot file of the server database for a given user. This file contains the data that Siebel Remote requires to initialize the local database. Database Extract retrieves data according to routing rules that define the level of access to information for each remote client. For more information, see Extracting the Server Database, and Extracting Regional Databases in Parallel.

Synchronization Manager Server Component

The Siebel Server starts a Synchronization Manager task for each incoming synchronization request it receives from a remote client. This task does the following work for each request:

• Verifies the status and credentials of the remote client, provided that authentication for Siebel Remote is enabled. Credentials include user ID and password.
• Transfers the local database template and local database extract, if applicable.
• Exchanges transaction files.
• Transfers file attachments to and from the Siebel File Server.

Each Synchronization Manager task services only one remote client at any one time. The Siebel Server can run multiple synchronization tasks concurrently. To configure this behavior, you can use the Max Task parameter of the Synchronization Manager server component. To allow the remote client to connect to the Siebel Server, you must configure the Synchronization Manager for this user. Tasks for Synchronization Manager start automatically. It is not necessary for you to manually start these tasks.

The Siebel File System parameter of the Synchronization Manager server component determines the location of the file system for the remote client.

Transaction Processor Server Component

The Transaction Processor server component scans the master transaction log of the Database Configuration Utilities and then prepares transactions for the Transaction Router server component. To avoid a deadlock problem, the Transaction Processor uses one of the following values according to the type of database that your Siebel application uses:

• DB2. The last log entry.
• MS SQL. The value 1000.

For more information, see Using Time Filters to Prevent Sending Old Data.

Transaction Router Server Component

The Transaction Router server component examines the transactions that the Transaction Processor creates in DX files in the txnproc directory. It determines visibility and routing for each transaction. Routing rules determine the dock object instances that Siebel Remote copies to each remote client. For more information, see Optimizing the Transaction Router Server Component.

Transaction Merger Server Component

The Transaction Merger server component applies transactions to the Database Configuration Utilities that the user uploads to the Siebel Server inbox. It applies these transactions to the server database after the synchronization session finishes and the remote client disconnects. For more information, see Optimizing the Transaction Merger Server Component.