Bookshelf Home | Contents | Index | Search | PDF

Developing and Deploying Siebel eBusiness Applications > Implementing Siebel Remote > Synchronizing a Mobile Web Client >

Process Flow for Changes Made by Mobile Users

---

Mobile Web clients, such as Kate, use a local database to store data for user access. The local database contains Siebel eBusiness Applications tables that store user data. The local database also contains a local transaction log to store transactions created by the mobile user. Siebel Remote forwards these transactions to the Siebel Remote server when the client synchronizes.

This section provides a description of each phase of the process flow, from the time when Kate modifies the new opportunity until the time when the modifications appear in the Server database. For this example, assume that Kate is meeting with the potential new client, represented by the opportunity record entered by the telesales representative in the previous section.

The figure below illustrates this flow and includes the following groups of steps:

As a result of the meeting, Kate makes changes to the Opportunity record in her local database. She enters these changes immediately after the meeting while working offline.
The modified opportunity record is saved to the Opportunities table in Kate's local database.
The transaction record is saved to the Local Transaction log.
Kate synchronizes the laptop. The Siebel Remote client extracts pending transactions from the Local Transaction log into transaction files (.dx). The client then places these DX files in the outbox directory on Kate's laptop. Siebel Remote connects to the server and the DX file is sent to the server and inserted in the database. as shown in Figure 43.

Figure 43. Process Flow for Changes by Mobile Users

For more information about process flow for changes by mobile users, see Siebel Remote and Replication Manager Administration Guide.

Bookshelf Home | Contents | Index | Search | PDF