Join rules determine the linking of a connector space object with an existing metaverse object. Join rules can have two parts: search criteria and resolution. You use the search criteria to compare connector space object attribute values and metaverse object attribute values. The search criteria are listed in the join rules in order of precedence. When you run a management agent, a join search is applied to each object in the connector space, which attempts to find a corresponding object in the metaverse, based on the search criteria.
The following table shows the action taken when a search returns a result.
|For this search result||The following occurs|
|Not one metaverse object is acceptable||The next search criteria in the precedence list is evaluated. If there is no more criteria in the precedence list, processing proceeds to the projection rules, if they exist.|
|Exactly one metaverse object is acceptable||If there is no rules extension for join resolution, the connector space object is joined, or linked, with the metaverse object. If you have configured a rules extension for join resolution, the rules extension will determine if the object will be joined.|
|More than one metaverse objects are acceptable||The connector space object is not joined with the metaverse
object. If you have configured a rules extension for join
resolution, the rules extension will attempt to determine which
object to select. Alternately, you can use Preview to diagnose the
reason for the multiple search results, and then use Joiner to
manually join the connector space object to the metaverse. For more
information about configuring a rules extension for join
resolution, open the Microsoft Identity Integration Server 2003 Developer Reference.
The following flow chart shows the sequence in which management agent rules are applied.