DirXML PolicySets


We need some clear definitions as between the technical and marketing teams of Novell, everyone has to be confused.

DirXML Driver or connector#

These are the same thing and technically they are a DirXML-DirXML Driver. A DirXML-DirXML Driver must be contained within one and only one DirXML-DirXML DriverSet.

DirXML Rule#

A DirXML Rule (in 3.5 and later) contains none or more conditions and actions. Must be contained within one of the following: The order of execution of the DirXML-Rule is determined by the Policy Interval and Policy Levels defined within the DirXML-Policies attribute of the DirXML-Driver.

A DirXML Rule can be linked or included in any of the permitted containers.

Policy Set Types#

There are several different types of policies you can define on both the Subscriber and Publisher channels. Each policy is applied at a different step in the data transformation, and some policies are only applied when a certain action occurs. For example, a Creation policy is applied only when a new object is created.

The different policy types and their order of execution on the channel are:


Policy Interval and Policy Levels#

The architecture introduced in Identity Manager 3.5 and later uses a single attribute on the driver object call DirXML-Policies.

Prior to 3.5, the DirXML-NextTransformation attribute, was used to determine the order execution which made reusing a policy object difficult.

Policy Flow#

The policy flow image also displays the flow of documents through the system. For example, an input document generated by the application follows the Publisher path identified by the green arrow beginning with the Input Policy Set and moving toward the Identity Vault. Result documents generated by the Metadirectory engine for the input document continue to follow the green arrow flowing back to the connected system through the Schema Mapping and Output Policy sets.

Input documents generated on the Subscriber channel behave similarly by following the orange arrow beginning at the Identity Vault and flowing to the connected application. Result documents generated by the application and Identity Manager driver continue to follow the orange arrow back through the Input and Schema Mapping policy sets to the Identity Vault.

Only Add operations flow through the Matching, Creation, and Placement policy sets on both the Subscriber and Publisher channels. All other operations follow the dotted line, bypassing these policy sets to the Command policy set.

Subscriber Flow Chart#


Publisher Flow Chart#


More Information#

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