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.

The following diagram illustrates a scenario for synchronizing data with a connected user.

Explanation of Callouts

As shown in this diagram, 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 docking\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 performs the remaining steps to download the new opportunity to the local database during the synchronization.

5. The remote client uses an existing LAN, WAN, or VPN connection to 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.