Guidelines For Direct Synchronization#

Direct synchronization typically uses views to synchronize data between Identity Manager and a database. You can use tables if they conform to the structure that the JDBC driver requires.

Direct model is usually associated with views Views provide the abstraction mechanism that best facilitates integration with existing customer tables.

• 1 view for each object class.
• View exposes all attributes included in the driver filter.
• Primary/foreign key hints (pk_ prefixes, etc.)

The following diagrams illustrate how direct synchronization works on the Subscriber and Publisher channels. In the following scenarios, you can have one or more customer views or tables.

Subscriber channel:#

• The View(s) or Table(s) must be update-able by the JDBC Driver User.

Direct Subscriber image

The Subscriber channel updates existing customer tables through a view in the synchronization schema.

Direct synchronization without a view is possible only if customer tables match the structure that the JDBC driver requires.

Publisher channel:#

• Event log (JDBC 1.x, 2.x)
• Triggerless (JDBC 2.x only)

Direct Publisher image

When a customer table is updated, publication triggers insert rows into the event log table. The Publisher channel then reads the inserted rows and updates the Identity Vault.

The DBA is responsible to place the data within the Publisher Event Log. Typically done by triggers, but how it is done is determined by the DBA.

Depending on the contents of the rows read from the event log table, the Publisher channel might need to retrieve additional information from the view before updating the Identity Vault. After updating the Identity Vault, the Publisher channel then deletes or marks the rows as processed.