jspωiki
DirXML Engine

Overview#

DirXML Engine (Identity Manager) can be thought of as two separate black boxes called channels.

Each channel takes an event on its input and issues a (possibly empty) set of commands on its output. The goal of the transformation from events to commands is to propagate the changes made by the Connected Application to the channel input into the Connected Application] to the channel output.

The transformation involves fixed logic in the DirXML Engine together with a set of configurable policies that guide the transformation of events to commands.

DirXML Engine uses a Publish-Subscribe Messaging pattern which consists of several components.

IDM Engine Flow

Subscriber Channel#

The Subscriber Channel defines and controls the Subscriber Flow of information to the Connected Application.

Publisher Channel#

The Publisher Channel defines and controls the Publisher Flow of information to EDirectory.

Translation Processor#

The Translation Processor is a part of the IDM engine that is responsible for converting information from the eDirectory domain (data format and schema structure/name) to the application domain, and vice versa.

Schema Mapping Policy#

The purpose of the Schema Mapping Policy is to map schema names (particularly attribute names and class names) between the Identity Vault namespace and the Application namespace.

Event Cache#

Data from EDirectory is evaluated against the Notify and Reset Subscriber Filter and then added to the event cache prior to continuation within the Subscriber Flow.

Novell IDM Driver Filters#

DirXML Events and Commands#

The distinction between DirXML Events and Commands is subtle but important.

More Information#

There might be more information for this subject on one of the following: