1.4 Key Terms

Driver Shim. A dynamically linked library (Exchange55Shim.dll) loaded directly by Identity Manager or by the Remote Loader. The shim collects the changes to be sent from Exchange to the Identity Vault, communicates changes from the Identity Vault to Exchange, and operates as the link that connects the Identity Vault and Exchange.

Driver. A set of policies, filters, and objects that act as the connector between the Identity Vault and the driver shim. The Identity Manager Driver for Exchange is a bidirectional synchronization connector between Microsoft Exchange and an Identity Vault. This connector uses XML to convert Exchange objects to Identity Vault objects and vice versa.

The driver enables an application to publish events from an application to the directory, enables an application to subscribe to events from the directory, and synchronizes data between the directory and applications.

To establish a connection between the Metadirectory engine and Exchange, you specify the driver’s configuration and connection parameters, policies, and filter values.

Driver Object. A collection of channels, policies, rules, and filters that connect an application to an Identity Vault that is running Identity Manager.

Each driver performs different tasks. Policies, rules, and filters tell the driver how to manipulate the data to perform those tasks.

The Driver object displays information about the driver’s configuration, policies, and filters. This object enables you to manage the driver and provide Identity Vault management of the driver shim parameters.

Identity Vault. A hub, with other applications and directories publishing their changes to it. The Identity Vault then sends changes to the applications and directories that have subscribed for them. This results in two main flows of data:

The Identity Manager Driver for Exchange is a bidirectional synchronization connector between Microsoft Exchange and an Identity Vault. This connector uses XML to convert Exchange objects to Identity Vault objects and vice versa.

Publisher Channel. Reads information from your Exchange Server and submits that information to the Identity Vault via the Metadirectory engine.

By using the poll parameters, the Publisher channel polls the Exchange server for changes to objects. If the Identity Manager Driver for Exchange detects changes in Exchange, the data between Exchange and the Identity Vault is synchronized. If the change was caused by data sent to Exchange from the Subscriber, no synchronization is necessary.

Subscriber Channel. Watches for additions and modifications to Identity Vault objects and creates changes on the Exchange server via the Metadirectory engine.

The Subscriber channel synchronizes changes made in the Identity Vault with data on the Exchange server. If an associated object is changed in the Identity Vault, the Subscriber channel updates the Exchange server with the new information.