Siebel Server Sync Guide > Administering Siebel Server Sync >
About SSSE Domains
This topic describes the Siebel and PIM domains supported by SSSE. The mapping of a Siebel domain to a PIM domain (such as a Microsoft Exchange Server domain) allows SSSE to synchronize data in these two domains. The supported SSSE domain maps specify how each Siebel and PIM field in a domain is mapped. Table 21 shows the SSSE supported Siebel domains, PIM domains, and domain maps. The Siebel domains synchronize Siebel data with Microsoft Exchange Server data. The PIM domains synchronize Microsoft Exchange data with the Siebel database. The current version of SSSE does not support the creation of new Siebel domains. CAUTION: PIMSI Engine functions correctly using only the PIM and Siebel domains listed in Table 21. Do not change the values of the Name or EAI Integration Object fields for the provided Siebel domains or the Name or Domain Identifier of the provided PIM domains. Additionally, you must not change the name of the domain maps or the default mapping of PIM and Siebel domains.
Table 21. Default Mapping of Siebel and PIM Domains
|
|
|
Siebel-Exchange Business Contact Map |
Siebel Business Contact |
Exchange Contact |
Siebel-Exchange Calendar Map |
Siebel Calendar |
Exchange Calendar |
Siebel-Exchange Employee Map |
Siebel Employee |
Exchange Contact |
Siebel-Exchange Personal Contact Map |
Siebel Personal Contact |
Exchange Contact |
Siebel-Exchange Task Map |
Siebel To Do |
Exchange Task |
About Resolving Synchronization Conflicts
If data in the Siebel application and Microsoft Exchange Server has been modified in such a way that SSSE cannot synchronize the differences, the current version of SSSE always resolves the conflict by using the data from the Siebel application. An example of a synchronization conflict is where the status of a Microsoft Exchange task is set to a value that differs from the value of the corresponding Siebel to do item. If the status is updated at approximately the same time, thereby falling within the same synchronization cycle, SSSE has no way to determine which update has to be applied, and automatically uses the data from the Siebel application.
|