Siebel Remote and Replication Manager Administration Guide > Siebel Remote Concepts > Using Siebel Remote >

How Changes Are Propagated to and from a Mobile Web Client

Between synchronization sessions, the Siebel Remote server prepares transactions applied to the database server by other users—mobile and dedicated. Siebel Server components write the transactions to a separate directory for each mobile user. These transactions, combined with items from the File System, are downloaded to the Mobile Web Client during the next synchronization session. Items from the File System include updated, published, or requested marketing literature, correspondence templates, and other types of file attachments.

A similar process occurs on the client as well, although without the server component.

Process Flow for Changes by Connected Users

This section describes the process flow for downloading changes on the server database to local databases. The flow takes place from the time a connected user creates a new opportunity until it appears in a local database.

This specific process flow includes an example of a telesales representative in a Call Center. The telesales person talks to potential customers responding to a new advertising campaign.

The telesales person decides to create a new opportunity record for one of the more promising responses. Figure 7 illustrates this flow. The numbers in the diagram correspond to the list immediately following the diagram.

Figure 7.  Process Flow for Changes by Connected Users

The process flow for the example above includes the following steps:

1. The telesales person creates a new opportunity record—a transaction saved in the opportunities table on the server database. A copy is saved to the master transaction log.
   1. Transaction Processor copies this transaction, and others, to the Apps Server.
   2. A Transaction Router task writes each transaction from the TXNPROC directory to transaction files in separate outbox directories for each Mobile Web Client.

      The Mobile Web Client outbox directories are stored on the Siebel Remote server.

2. A mobile user invokes a synchronization session from the laptop.

   During the synchronization session, the following steps occur to download the new Opportunity record to the mobile user's local database:

   1. The Siebel Remote client on the laptop dials the modem to connect to the Siebel Remote server.

      This can be handled by an existing modem or LAN connection.

   2. The Siebel Remote client connects to the Siebel Remote server.
   3. The Siebel Remote server starts the synchronization session for the Mobile Web Client.
   4. The Synchronization Manager validates the Mobile Web Client's node name against the list of valid mobile users in the server database.

      The Siebel Remote client receives transaction files going to and from the Synchronization server, and retrieves file attachments.

   5. The client retrieves transaction (.dx) files from the user's outbox directory on the Siebel Remote server and stores them in the mobile user's local inbox directory. The client also retrieves the user's requested, published, or broadcasted file attachments from the Siebel File Server.
   6. The new opportunity record is inserted into the Opportunity table in the user's local database.
   7. The Siebel Remote client closes the connection with the Siebel Remote server.

      The mobile user can use the Siebel client while the Siebel Remote client applies the changes to the local database.

CAUTION:  Users should never directly modify the local transaction log. The Siebel Remote synchronization client automatically purges the local transaction log table.

Process Flow for Changes Made by Mobile Users

Mobile Web Clients 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 the mobile user modifies the new opportunity until the time when the modifications appear in the Server database. For this example, assume that a mobile user is meeting with a potential new client, represented by the opportunity record entered by the telesales representative in the previous section.

Figure 8 illustrates this flow. The numbers in the diagram correspond to the list following the diagram.

Figure 8.  Process Flow for Changes by Mobile Users

1. As a result of the meeting, the mobile user makes changes to the Opportunity record in the local database on the laptop. The user enters these changes immediately after the meeting while working offline.
2. The modified opportunity record is saved to the Opportunities table in the local database. A transaction record is saved to the Local Transaction log.
3. 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 the laptop.
4. The mobile user synchronizes the laptop.

   During the synchronization session, the following steps occur to record the changes to the opportunity record:

   1. Siebel Remote dials the modem to connect to the Siebel Remote server.

      If the user is in the office, a LAN connection will also work.

   2. Siebel Remote client connects to the Siebel Remote server.
   3. Siebel Remote server starts the synchronization session for the mobile user.
   4. Synchronization Manager validates the Mobile Web Client's node name against the list of valid Mobile Web Clients in the server database.
   5. Synchronization Manager sends the transaction files in the outbox directory on the laptop to the mobile user's inbox directory on the Siebel Remote server.
   6. Siebel Remote closes the connection with the Siebel Remote server.
   7. The changed Opportunity record is inserted into the Opportunity table on the Server database.

File Attachments and Siebel Remote

This section provides additional information about how Siebel Remote handles file attachments.

When a Siebel Remote client attaches a file to a record in the local Siebel database, the metadata concerning the file is stored in the local Siebel database, and the file is stored in the local Siebel file system. When the client synchronizes with the Siebel Remote Server, normal synchronization procedures result in the file being copied to the server's Siebel file system, and metadata concerning the file being copied to the server's Siebel database.

If the record to which the file is attached is accessible to another Siebel Remote client, such as another member of a sales team, then ordinarily file metadata is transferred to that team member's local Siebel database when that team member next synchronizes. However, the file attachment, itself, usually is not transferred to the local Siebel file system until it is specifically requested. (The exception is that certain types of file attachments, such as Literature items, have a Distribution Method setting. If Distribution Method is set to Publish, the file is automatically sent to Siebel Remote users, without needing to be requested.)

A Remote client requests a file attachment by clicking its link in a Siebel application, or by selecting its Request File check box. When this is done, a request for the file is queued. In order to actually receive the file, the client must synchronize again, which will result in the file being copied to the local Siebel file system. Once the synchronization is complete, the client must click the link again to view the file.