Projection Rules
Projection rules differ from join rules in that during a join process, the join rules search for an existing metaverse object that matches the connector space object. During the projection process, projection rules determine whether or not a new object is created in the metaverse so that the connector space object can link to it. Management agents apply projection rules to objects where join rules have not found a unique match or where join rules were not configured. Projection rules only configure the object type of the projected object in the metaverse. You have to use attribute flow rules to configure attributes.
You can define only one projection rule for each object type in the connector space. The projection rule can be a declarative rule or a rules extension.
| Rule | Description |
|---|---|
Declarative rule |
Define a basic object type mapping, where the source and target object types are selected from the available connector space object types and metaverse object types in the Management Agent Designer. |
Rules extension |
Enable users to write a rules extension that can examine the source object and determine whether it is projected to the metaverse, and, if so, as what object type. |
Note
You must define either join or projection rules, or both, in the management agent in order for objects to link between the connector space and the metaverse.
For more information about creating rules extensions, see the FIM Developer Reference.
The following flow chart shows the sequence in which management agent rules are applied.
.gif "Management agent rules")