|
Siebel Server Sync Guide > Siebel Server Sync for Microsoft Exchange Server Architecture Overview >
About Synchronizing Records during Initial Extract
During the initial extract process for a particular user, for each domain that the user can synchronize, the initial extract process compares that user's Microsoft Exchange records in that domain with that user's Siebel records in the corresponding Siebel domain. The actions that follow this comparison depend on the following factors:
- Synchronization level for the current domain and user. The synchronization level determines whether SSSE synchronizes a domain. For a domain that SSSE can synchronize, the synchronization level determines whether information can flow in both directions between the Microsoft Exchange Server and the Siebel database, or whether information must always flow in one direction.
- Extract Start Date. The administrator can specify extract start dates for individual users, and a system-wide extract start date that applies to all users for whom individual extract start dates are not specified. The Extract Start Date determines the date of the oldest appointments and tasks that SSSE is to synchronize.
- Existence or absence of a matching record. SSSE compares Microsoft Exchange records and Siebel records to determine if corresponding records have to be modified or if new records have to be created.
When SSSE compares calendar, employee, and task records in Microsoft Exchange and Siebel Business Applications, SSSE only checks the values in certain key fields to determine whether or not the records match. For additional information about key fields, see Setting Key Fields. For information about how SSSE matches contact records, see About SSSE Contact Record Matching.
- PIM Category Value. Depending on how your SSSE implementation is configured, whether or not SSSE synchronizes Microsoft Exchange contact records depends on whether or not the Category field in the Microsoft Exchange record has a value that matches the PIM Category value setting in your Siebel implementation, as described in Initial Extract of Microsoft Exchange Contact Records.
If you have enabled the Opt-in feature for calendar and task records, the value of the Category field in the Microsoft Exchange record must also match the PIM Category value setting if the record is to be synchronized. For additional information, see Implementing Opt-In Synchronization for Calendar and Task Records.
- Private check box status. If you have set the Ignore option for the Private Item Behavior parameter for calendar and task records, SSSE does not synchronize records that have the Private check box selected. For additional information, see Skipping Private Calendar or Task Records During Synchronization.
- Sync List Status. Whether or not SSSE synchronizes Siebel contact records depends on whether the Sync List flag is set for the record and user in question.
- Status of case sensitivity settings for your Siebel implementation. Siebel implementations can be set for case-sensitivity or case insensitivity at the application level, at the AOM (application object manager) level, or at the field level. The status of these settings affects whether or not SSSE detects differences between two field values that differ only in capitalization.
By default, Siebel Business Applications are set to be case-sensitive. For example, the default settings cause SSSE to detect no match between a value of ABC Corp on the PIM and a value of ABC CORP in the Siebel database. In such a case, SSSE synchronizes the records separately, resulting in both forms of the record being present on the PIM and in the Siebel database. However, if your Siebel application is case-insensitive in the context where SSSE checks for matching records, then SSSE would treat these two values as a match. For information about setting applications, AOMs, and fields to be case-insensitive, see Siebel Applications Administration Guide.
For additional information on initial and ongoing extractions, see:
|
