Siebel Remote and Replication Manager Administration Guide > Architecture of Siebel Remote > How Siebel Remote Synchronizes Local Databases >

How Siebel Remote Synchronizes Data That Users Modify

The Siebel Server prepares transactions that other users apply to the server database between synchronizations. Server components on the Siebel Server write these transactions to a separate folder for each user that resides on the server. Siebel Remote downloads these transactions and other items from the file system to the remote client during the next synchronization. Items in the file system include updated, published, or requested marketing literature, correspondence templates, and other types of file attachments. A similar process occurs on the remote client, although without using the server component.

Scenario for Synchronizing Modified Data with Connected Users

This topic describes how Siebel Remote downloads data that users have modified from the server database to the local database. It describes the steps that occur when a connected user creates a new opportunity until Siebel Remote displays this opportunity in the local database. It describes a telesales user who works in a Call Center who talks with a potential customer who is replying to a new advertising campaign.

Figure 6 illustrates a scenario for synchronizing data with a connected user.

Figure 6. Scenario for Synchronizing Data with Connected Users

Explanation of Callouts

Siebel Remote does the following work to synchronize data with a connected user:

1. A telesales user creates a new opportunity. Siebel Remote saves this opportunity as a transaction in the opportunities table on the server database. It saves a copy to the master transaction log.
2. The Transaction Processor copies this transaction and other transactions to the Siebel Server.
3. A Transaction Router task writes each transaction from the txnproc folder to transaction files that reside in separate outbox folders for each remote client. Siebel Remote stores these outbox folders on the remote client on the Siebel Server.
4. The user starts a synchronization from the remote client.

   Siebel Remote does steps Step 5 through Step 11 to download the new opportunity to the local database during the synchronization.

5. The remote client uses an existing modem or LAN connection to dial the modem so that Siebel Remote can connect to the Siebel Server.
6. The remote client connects to the Siebel Server.
7. The Siebel Server starts the synchronization for the remote client.
8. The Synchronization Manager validates the node name that resides on the remote client with the list of valid node names that exist in the server database. The remote client receives transaction files that Siebel Remote routes to and from the Siebel Server. It also gets file attachments.
9. The remote client gets transaction (.dx) files from the user outbox folder that resides on the Siebel Server, and then stores them in the local inbox folder that resides on the remote client. The remote client also gets any requested, published, or broadcasted file attachments that reside on the Siebel File Server.
10. Siebel Remote inserts the new opportunity in the opportunity table in the local database that resides in the client.
11. The remote client closes the connection with the Siebel Server. The user can use the remote client while it applies synchronized data to the local database.

Scenario for Synchronizing Modified Data with Unconnected Users

This scenario describes how Siebel Remote uploads data that a user has modified from the local database to the server database. It describes how a telesales user works in a Call Center and meets with a potential new customer who Siebel Remote represents as an existing opportunity in the local database. Another user created this opportunity at an earlier time, and then uploaded it to the Siebel Server during a synchronization. The telesales user then downloaded it during a subsequent synchronization.

Figure 7 illustrates a scenario for synchronizing data with an unconnected user.

Figure 7. Scenario for Synchronizing Data with Unconnected Users

Explanation of Callouts

Siebel Remote does the following work to synchronize data with an unconnected user:

1. The user modifies an existing opportunity that resides in the local database. The user enters these modifications immediately after meeting with the potential customer while working offline.
2. Siebel Remote saves the modified opportunity in the opportunities table that resides in the local database.
3. Siebel Remote saves a transaction record to the local transaction log.
4. Siebel Remote extracts pending transactions from the local transaction log to transaction dx files. It then places these DX files in the outbox folder that resides on the remote client.
5. The user starts a synchronization from the remote client.

   Siebel Remote does Step 6 through Step 12 to record the modifications that occur to the opportunity during this session.

6. Siebel Remote dials the modem to connect to the Siebel Server. If the user is in the office, then Siebel Remote can use a LAN connection.
7. The remote client connects to the Siebel Server.
8. The Siebel Server starts the synchronization for the user.
9. Synchronization Manager validates the remote client name with the list of valid clients that exist in the server database.
10. Synchronization Manager sends any transaction files that exist in the user outbox folder on the remote client to the user inbox folder that resides on the Siebel Server.
11. Siebel Remote closes the connection with the Siebel Server.
12. Siebel Remote inserts the modified opportunity in the opportunity table on the server database.