Novell POLICY IN DESIGNER 3.5 - 09-18-2009 Manual page 103

Options
Merge Authority
Optimize Modification to
Identity Manager
Definitions
Default: If an attribute is not being synchronized in either channel,
no merging occurs.
If an attribute is being synchronized in one channel and not the
other, then all existing values on the destination for that channel
are removed and replaced with the values from the source for that
channel. If the source has multiple values and the destination can
only accommodate a single value, then only one of the values is
used on the destination side.
If an attribute is being synchronized in both channels and both
sides can accommodate only a single value, the connected
application acquires the Identity Vault values unless there is no
value in the Identity Vault. If this is the case, the Identity Vault
acquires the values from the connected application (if any).
If an attribute is being synchronized in both channels and only one
side can accommodate multiple values, the single-valued side's
value is added to the multi-valued side if it is not already there. If
there is no value on the single side, you can choose the value to
add to the single side.
This is always valid behavior.
Identity Vault: Behaves the same way as the default behavior if
the attribute is being synchronized on the Subscriber channel and
not on the Publisher channel.
This is valid behavior when synchronizing on the Subscriber
channel.
Application: Behaves the same as the default behavior if the
attribute is being synchronized on the Publisher channel and not
on the Subscriber channel.
This is valid behavior when synchronizing on the Publisher
channel.
None: No merging occurs regardless of synchronization.
Yes: Changes to this attribute are examined on the Publisher
channel to determine the minimal change made in the Identity
Vault.
No: Changes are not examined.
When an operation is a Modify on the Publisher channel, the
Metadirectory engine examines the current state of the object in
the Identity Vault and changes the Modify to update only the
values that are changing. For example, if an object has attributes
of a, b, c, and d and the Publisher channel receives a Modify event
to remove all existing values and add a, b, d, and e, the optimize
process knows that the minimal change is to remove d and add e.
Using this option can take a long time to process events on
attributes that have more than 1,000 values.
Controlling the Flow of Objects with the Filter 103