Siebel Remote and Replication Manager Administration Guide > Siebel Remote Concepts > Conflict Detection and Resolution >

Update Conflicts

An update conflict occurs if, for example, one user changes a contact's area code to 415 and another user changes it to 408. Siebel Remote detects and consistently resolves conflicts by using one of two rules: Client Wins or Server Wins. The Client Wins rule states that the Mobile Web Client database value overrides the server database value. The Server Wins rule states that the server database value overrides the Mobile Web Client database value. The default setting, Server Wins, is strongly recommended to resolve such conflicts because data changes will converge more quickly. The Client Wins rule will work as well but will take longer for data to converge.

CAUTION:  To maintain integrity across databases, the same conflict resolution rule must be in effect for client and server databases. You should specify the rule as part of the initial Siebel Remote implementation on your database server, and before running a database extract for any client so that the rule is replicated consistently to the clients.

Siebel Remote applies the same logic to databases to make sure that they remain synchronized. During the initial Siebel Remote implementation, the Siebel administrator sets a system preference to reflect which rule is to be in effect.

NOTE:  Mobile Web Client transactions are processed in the order in which the users synchronized. Any successful database update sent from a Mobile Web Client to the server becomes a server transaction for the purpose of conflict resolution.

If Siebel Remote rejects an update from a Mobile Web Client, the mobile user can determine whether an update conflict has occurred. If the result of Siebel's conflict resolution is inappropriate, the user can manually reapply the change to the local database. It will be sent to the server again during the next synchronization session when the Mobile Web Client sends database changes to the server. If other changes have not been made to the data value since the last synchronization session, the change will not conflict and will succeed on the server.


 Siebel Remote and Replication Manager Administration Guide 
 Published: 19 November 2003