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

PIMSI Engine Task Flow

This topic outlines the sequence of steps that are performed when data is synchronized between Siebel CRM and Microsoft Exchange Server. The process is as follows:

  1. An administrator enables a user for synchronization.
  2. At preconfigured intervals, PIMSI Dispatcher determines which users have synchronization enabled.

    For each synchronization-enabled user, the Dispatcher sends a Task Request to PIMSI Engine, requesting synchronization of Microsoft Exchange data for that user.

    If the user's Siebel data has changed since the user's last successful synchronization, or if the user has not yet synchronized successfully, then the Task Request also asks for synchronization of the applicable Siebel data.

  3. PIMSI Engine determines which data must be synchronized for the user, for both Siebel data and Microsoft Exchange data. The PIMSI engine:
    • Computes the incremental data change since the user's last successful synchronization
    • Communicates with Exchange Connector to request data from Microsoft Exchange Server
    • Reads data from the Siebel database
    • Performs data conflict detection and resolution
  4. PIMSI Engine sends data from the Siebel database to the Exchange Connector, which identifies the user's mailbox on the Microsoft Exchange Server and writes to it.
  5. PIMSI Engine uses Enterprise Application Integration (EAI) methods to write data from the Microsoft Exchange Server to the Siebel database. EAI includes Siebel Adapter, Data Mapper, and XML Converter.

NOTE:  For specific operations, such as Delete or Visibility Change operations, the PIMSI Engine data flow relies upon database triggers recording information in the S_SD_SYNC_INFO table about changes to Siebel data.

Siebel Server Sync Guide Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.