Siebel Remote and Replication Manager Administration Guide > Architecture of Siebel Remote > Overview of the Siebel Remote Architecture >

How Siebel Remote Flows Data Through the Architecture

Figure 3 illustrates the flow of data through the architecture for Siebel Remote. For more information about the server components and files that this architecture uses, see How Siebel Remote Uses Siebel Servers.

Figure 3. Flow Siebel Remote Flows Data Through the Architecture

Explanation of Callouts

Data flows through the Siebel Remote architecture in the following sequence:

1. Siebel Remote considers every action in the server database as a transaction. These actions include adding and deleting rows, updating rows, and merging rows. It stores a copy of each transaction in the Master Transaction Log table (S_DOCK_TXN_LOG), provided that Siebel CRM does the transaction.

   To minimize the size of the S_DOCK_TXN_LOG table, Siebel Remote stores transactions at the field level. If Transaction Logging is turned on, and if an action occurs, then Siebel Remote stores only the modifications that occurred to fields as transactions. This configuration helps to optimize the synchronization process.

   For more information, see Modifying the S_DOCK_TXN_LOG Table.

2. The Transaction Processor server component does the following work:
   • Copies the transactions that exist in the S_DOCK_TXN_LOG table to the docking\txnproc folder.
   • Copies the file system transactions that are of type External File from the file system to the docking\txnproc folder.
   • Clears the S_DOCK_TXN_LOG table of the transactions.
3. The Transaction Router server component determines the users who must receive the transactions that the docking\txnproc folder contains.
4. Siebel Remote creates a docking folder on the Siebel Server for the user the first time that it extracts a database for this user. It does the following work:
   1. Creates an inbox and an outbox. The outbox stores any future extracts and DX files that Siebel Remote receives from the Transaction Router.
   2. Sends these DX files to the outbox for each remote client that resides in the docking folder on the Siebel Server, according to visibility rules and routing rules.
   3. The Transaction Router finishes the task it is processing, and then configures the Transaction Processor server component to remove any DX files that exist in the docking\txnproc folder, according to the following Transaction Processor parameter:

   Clean .dx files iterations

5. When you install a Siebel application you specify at least one Siebel Server as a remote server. This Siebel Server hosts all or some of the users and it contains the docking folders for these users. It uses these folders to transfer the files that are involved with the synchronization process. These files include the following items:
   • New database templates that the Generate New Database task creates
   • Database extracts that Siebel Remote uses with the templates to initialize the local database
   • DX files (.dx)
   • TOC files (.toc)
   • Visibility data for the remote client. This data resides in the visdata.dbf file and the dobjinst.dbf visibility database file.
6. The remote client processes any transactions that exist in the local database while disconnected.

   Siebel Remote stores a copy of each transaction in the Local Transaction Log, which is similar to the Master Transaction Log on the Siebel Server. It does not create any audit trail records on the disconnected client. If a Siebel application uses Siebel Audit Trail, then it eventually uses the information that it stores about disconnected transactions to create audit trail records on the Siebel Server.

7. If the user starts the synchronization process, then the remote client creates DX files from the log, and then moves these DX files to the remote client outbox.
8. The synchronization process begins when the remote client starts a synchronization.

   The Synchronization Manager server component must be running. It authenticates the remote client according to the type of authentication that the parameters for the Synchronization Manager specify.

   The synchronization process includes handling communication between the remote client and the file system. It moves the DX files from the outbox of the docking folder to the inbox on the remote client. It also moves files from the outbox on the remote client to the inbox of the docking folder. It copies any attachments, correspondence, or templates that the remote client creates to the Siebel File System.

9. The remote client applies the DX files to the local database as soon as it receives the first transaction file or after it completes the file exchange with the Siebel Server, depending on the user synchronization options or command line options that you choose. Siebel Remote does not modify the server database until the file exchange finishes and the remote client disconnects.
10. The Transaction Merger server component on the Siebel Server pulls the DX files from the inbox in the docking folder.
11. The Transaction Merger applies the modifications to the server database.

    If your Siebel application uses Siebel Audit Trail, then the Transaction Merger places information about disconnected transactions that synchronize successfully to the server database tables that Siebel Audit Trail uses.

    The Transaction Merger also identifies synchronization conflicts. The System Conflict Resolution system preference uses one of the following values to determine if the Siebel Server or the remote client wins during conflict resolution:

    • Server Wins
    • Client Wins

      Siebel Remote communicates any conflicts that exist to the user during the next synchronization.

      The Transaction Merger deletes any DX files that reside in the inbox in the docking folder.

      The Transaction Merger does not create audit records for a disconnected transaction that does not synchronize. If the user approves a disconnected transaction that Siebel Remote detects as a conflict, then the Transaction Merger creates audit information on the Siebel Server when the user approves the transaction.