Siebel Server Sync Guide > Siebel Server Sync for Microsoft Exchange Server Architecture Overview >

About PIMSI Engine

PIMSI Engine is a Siebel Server component that enables synchronization of data between Siebel Enterprise Server and Microsoft Exchange Server. This component allows the synchronization of calendar appointments, tasks (called to do items in Siebel Business Applications), and business contacts between the Siebel database and the Microsoft Exchange Server (or servers).

PIMSI Engine administration and configuration is conducted using centralized administration and configuration screens in Siebel Business Applications. No end-user installation is required for synchronization of calendar appointment, task, or contact records. End users designate the contact records to be synchronized, but no other end user action is required. Synchronization can be selectively enabled for individual users or groups of users. After synchronization is initiated between Microsoft Exchange and Siebel Business Applications for a specific user, synchronization is performed automatically for that user. The time that elapses between when a data change takes place and when the change is synchronized depends on a system-wide configuration parameter that the administrator can adjust.

NOTE:  Because PIMSI Engine is server based, users must use Offline Store (OST) files to replicate data between Microsoft Exchange Servers and their local Microsoft Outlook client, or they must store their Microsoft Outlook data exclusively on the Microsoft Exchange Server. PIMSI Engine cannot synchronize data stored in Personal Folders (PST) files.

You can run PIMSI Engine components on multiple Siebel Servers in your Enterprise. If you set the MaxTasks and MaxMTServers parameters for the PIMSI Engine component appropriately, then you can also have multiple PIMSI Engine processes running simultaneously on a Siebel Server host.

If a PIMSI Engine goes offline in a Siebel implementation that has multiple PIMSI Engines, then the remaining PIMSI Engines pick up the workload of the PIMSI Engine that is not functioning. When that PIMSI Engine comes back online, workloads for all PIMSI Engines rebalance automatically.