Siebel Remote and Replication Manager Administration Guide > Administering Siebel Remote > Data Synchronization >

Managing Synchronization Frequency

You are responsible for developing guidelines for synchronization frequency, the frequency at which your mobile users synchronize. You should recommend an appropriate interval between synchronization sessions, taking into consideration your organization and its activities. The frequency and schedule you define for the Transaction Router should also be considered.

Initially, you may recommend that mobile users synchronize once a day. You can then use the following factors to evaluate your synchronization traffic and determine if your synchronization schedule needs refinement.

Connection time. Frequent synchronization reduces the volume of transactions to be transmitted during a synchronization session, thereby reducing connection time for that session. You should evaluate the difference in connection time and cost between less frequent but longer synchronization sessions, and more frequent but shorter sessions.

Disk space requirements. Frequent synchronization reduces the number of transactions accumulated between sessions, thereby reducing the demand for disk space on both the Siebel Remote server and the client. You should evaluate the availability of disk space and determine the trade-off between increasing disk space and increasing synchronization frequency.

Database volatility. Your synchronization schedule determines when changes to the server database are reflected in client databases. In industries with high sales volatility, frequent synchronization can be a significant advantage. You should investigate the value of frequent synchronization to your organization in such a case.

Remember that the Transaction Router detects and routes database changes to client outboxes for subsequent transmission during synchronization. Therefore, the operating status of the Transaction Router on each application server will affect data availability for mobile users. In a highly volatile environment, you may want to run multiple Transaction Routers for each application server. Additionally, close monitoring of this component is highly recommended.

Mobile users' productivity. Frequent synchronization affects your mobile users' time, and potentially affects their productivity. You should consider your users' environments and their convenience in completing a synchronization session.

Server modem connections. The ratio of Mobile Web Clients to server modem connections influences your synchronization schedule. If your ratio is high, you may need to assign specific synchronization times to your users.