Siebel CRM Desktop for IBM Notes Administration Guide > How Siebel CRM Desktop Synchronizes Data > How Siebel CRM Desktop Synchronizes Data Between the Client and the Siebel Server >

How Siebel CRM Desktop Synchronizes Data During the Initial Synchronization

An initial synchronization is a type of synchronization that occurs in the following situations:

• Immediately after the user installs Siebel CRM Desktop.
• If you deploy a metadata change to the user that includes a change to the data schema.
• If the options in the login dialog box change. For example, the user name changes or the URL of the Siebel Server changes.

The purpose of the initial synchronization is to initialize the IBM Notes data storage with the Siebel CRM data that is available to the user. CRM Desktop downloads files in the customization package to IBM Notes the first time the user synchronizes metadata with the Siebel Server. This metadata includes the following information:

• Definition data for CRM Desktop, such as synchronization rules, object definitions, and so on
• Siebel CRM data for CRM Desktop, such as accounts, opportunities, and so on

CRM Desktop does the following work during the initial synchronization:

1. Establishes a synchronization session with the Siebel Server through the Web service interface.
2. Directs the Web Service Connector in IBM Notes to call the DownloadMetadataFiles method of the PIM Client Metadata Service business service that resides on the Siebel Server.

   To broker requests through the EAI Siebel Adapter, CRM Desktop uses the business services that the Web services references. It uses the EAI Siebel Adapter business service to process the SiebelMessage payload in the requests.

3. Directs the PIM Client Metadata Service on the Siebel Server to get the login ID of the user from the session, and then identifies the responsibility that the user uses, the customization package that the responsibility references, and if the package is active. For more information, see Relationships Between Users, Responsibilities, Customization Packages, and Metadata Files.
4. If the customization package is published and valid, then CRM Desktop queries all metadata files of that package and creates a Siebel message. It does the following work:
   • Sets the containsFiles argument to true.
   • Enters the relevant data in the packageId, responsibilityId, and hashValue arguments.
5. Applies the downloaded package for IBM Notes.
6. Downloads Siebel CRM data.

   For more information, see How Siebel CRM Desktop Synchronizes Siebel CRM Data.

7. Logs out of the synchronization session that it established in Step 1.

For more information, see How Siebel CRM Desktop Handles Synchronization Errors.