You can configure Identity Resolution to load, synchronize, and search against data stored in a Siebel 7.7 CRM application. This chapter provides detailed instructions for integrating Identity Resolution with Siebel.

Siebel application data is held in an Oracle, UDB or Microsoft SQL Server database. At a physical level, the data are held in base tables. However, base tables are not accessed directly. Instead, Siebel provides a higher level of data abstraction with its Object Manager (OM). The joins base tables to provide highlevel Integration Objects (IO) that the user works with.

As Siebel prohibits the creation of triggers on base tables, Identity Resolution treats Siebel as a No Source Access (NSA) style of database. The fundamental unit of data that can be extracted or synchronized is an IO, which is mapped 1:1 to an Identity Resolution IDT.

To extract and synchronize data, the Siebel administrator must first define an IO using Siebel Tools. A matching IDT-Definition is created in an Identity Resolution System.

Identity Resolution provides a Siebel Workflow to extract data using the Object Manager. The workflow will query Siebel to extract the IO data, encode them using XML and write them to a flat-file. This file can then be loaded into Identity Resolution.

Synchronization workflows (activated by Run-Time Events) are provided to pass synchronization messages to Identity Resolution whenever an object is added, deleted, or modified. The messages are encoded as XML and sent over a socket using HTTP to the Identity Resolution XS Server. The XS Server stores transactions in the NSA Transaction Table for processing by the Update Synchronizer.