Bookshelf Home | Contents | Index | PDF |
Siebel Server Sync Guide > Administering Siebel Server Sync for Microsoft Exchange Server > Process of Configuring Siebel and PIM Domain Characteristics > Setting Siebel Domain-Level SynchronizationDomain-level synchronization establishes the highest allowable synchronization setting for all users and groups on the domain. You must set user-level and group-level synchronization to values that are equal to or lower than the domain-level synchronization. This task is a step in Process of Configuring Siebel and PIM Domain Characteristics. The following procedure describes how to set domain synchronization.
About the Limitation Against Import Only Synchronization LevelYou can configure SSSE to allow one-way synchronization of calendar records, from Microsoft Exchange to Siebel Business Applications. For information on configuring import-only synchronization for calendar items, see Implementing Import-Only Synchronization of Calendar Records. The Import Only synchronization level is not supported for any of the other Siebel domains. The reason for this limitation is that there are potential data integrity problems if data is imported only from Microsoft Exchange to your Siebel application. This hazard to data integrity arises from the different methods the two systems use to store data. Siebel Business Applications use a relational database, but Exchange Servers maintain data using an individual data store for each Microsoft Exchange user. As an example of the kind of issue that could arise, a business contact record in a Siebel application can be shared between multiple people in a team. Any update that one user makes to the business contact record in Siebel Business Applications is immediately visible to other users, because all users are accessing a single record in the relational database. However, in Microsoft Exchange, each user has his or her own set of contact records. An update made to one user's contact record is not reflected in other users' contact information. If data was only imported from Microsoft Exchange into your Siebel application, an update made by one user could be lost when another user makes a conflicting update. The following paragraphs describe in more detail how an example business contact record would be handled for different synchronization levels:
|
Siebel Server Sync Guide | Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |