Configure Join and Projection Rules

  • Article

For this procedure, in Management Agent Designer, on the Configure Join and Projection Rules page, you can configure the association of a connector object with a metaverse object. When you run a management agent, a join search is applied to each object in the connector space configured for join rules, which attempts to find a corresponding object in the metaverse. Management agents apply projection rules to objects where a join has failed or was not configured. You can also specify that a rules extension resolve join rules. To complete this procedure, you must be logged on as a member of the FIMSyncAdmins security group.

To configure join and projection rules

  1. In Management Agent Designer, on the Configure Join and Projection Rules page, in the Data source Object Type column, click the data source object type that you want to include in the join or the projection.

  2. To configure a join rule

    1. Click New Join Rule.

    2. In the Join Rule forObjectType dialog box, under Data source attribute, click an attribute.

    3. In Mapping type, do one of the following:

    • To specify a direct mapping to a metaverse attribute, click Direct. In Metaverse object type, click the metaverse object type. In Metaverse attribute click the attribute that you want to directly map to the data source attribute.

    • To specify a rules extension, click Rules extension, select the Use rules extension to resolve check box, and then in Context, type the rules extension context.

    1. To add the join rule, click Add condition.

    2. To add additional join rules, repeat steps 1 through 4, and then click OK.

  3. To configure a projection rule

    1. Click New projection rule.

    2. In the Projection dialog box, in Type, do one of the following:

    • To declare the metaverse object type, click Declared. In Metaverse object type, confirm that the correct metaverse object type is highlighted.

    • To use a rules extension, click rules extension.

    1. To add the projection rule, click OK.

    2. To add additional projection rules, repeat steps 1 through 3, and then click OK.

Note

Join rules for a particular object type are always applied before projection rules, regardless of the order specified.

Note

For Rules Extension mapping, to select multiple data source attributes, in Data source attribute, press the CTRL or SHIFT key, and then click any additional attributes.

Note

In Join and projection rules for:  Object Type, you can define each connector attribute that you want to search for in the metaverse and the order in which you want to perform the join. You can configure a join rule for each attribute that you map to the server running FIM. After each of these searches, FIM checks the results against the conditions that you specify. Conditions are not required, but are recommended when you create a join that might contain multiple conditions. As soon as a search result passes the conditions test, the connector is joined to that entry. It is recommended that you put your attribute list in order so that the most likely and most authoritative matches are listed first.

Note

There is no limit to the number of join rules that can be applied to an object type. However, for better performance, it is recommended that you avoid including rules that are negated by rules higher in the order. There is a limit of one projection rule per object type.

Note

For more information about developing rules extensions for join and projection rules, see the FIM Developer Reference.

Note

To increase join rules performance, it is strongly recommended you select only those attribute types that can be indexed in the metaverse. Indexing increases the efficiency of your join searches. For more about using Metaverse Designer to set the indexed property for an attribute, see See Also.

See Also

Concepts

Join Rules
Using Metaverse Designer
Projection Rules
Using Joiner
Using Management Agents