1. Remote and Replication Manager Administration Guide
  2. Scenario for Synchronizing Modified Data with Disconnected Users

Scenario for Synchronizing Modified Data with Disconnected 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.

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

Scenario for Synchronizing Data with an Unconnected User: This image is described in the surrounding text.

Explanation of Callouts

As shown in this diagram, 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. The remote client uses an existing LAN, WAN, or VPN connection to connect to the Siebel Server.

  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.