After the Metadirectory engine determines that an object is to be synchronized, the following processes occur:
In the tables the following pseudo-equations are used:
There are three different combinations of selected items in the filter, they create different outputs.
The attribute is set to synchronize on the Publisher and Subscriber channels and merge authority is set to default.
Figure 8-1 Scenario One
The following table contains the values that the Metadirectory engine synchronizes when the attribute is sent through a filter that is set to the configuration for scenario one. The table shows different outputs depending upon whether the attribute comes from the Identity Vault or the Application, if the attribute is single-valued or multi-valued, and if the attribute is empty or non-empty.
Table 8-1 Output of Scenario One
The attribute is set to synchronize only on the Subscriber channel, or it is set to synchronize on both the Subscriber and Publisher channels and the merge authority is set to the Identity Vault.
Figure 8-2 Scenario Two
The following table contains the values that the Metadirectory engine synchronizes when the attribute is sent through a filter that is set to the configuration for scenario Two. The table shows different outputs depending upon whether the attribute comes from the Identity Vault or the Application, if the attribute is single-valued or multi-valued, and if the attribute is empty or non-empty.
Table 8-2 Output of Scenario Two
The attribute is set to synchronize on the Publisher channel or the merge authority is set to application.
Figure 8-3 Scenario Three
The following table contains the values that the Metadirectory engine synchronizes when the attribute is sent through a filter that is set to the configuration for scenario Three. The table shows different outputs depending upon whether the attribute comes from the Identity Vault or the Application, if the attribute is single-valued or multi-valued, and if the attribute is empty or non-empty.
Table 8-3 Output of Scenario Three