Novell Designer for Identity Manager 3.5, Manual, Page: 128 / 510

128 Policies in Designer 3.5
no
vd
ocx
(e
n)
13
Ma
y 20
09
8 A file conflict window appears with the message “
Before editing this item you need
to save. Do you wish to save the editor’s changes and continue?
” Click Yes .
The Policy Builder is launched and the new Matching policy is saved.
9 Continue with Importing the Predefined Rule .
8.11.2 Importing the Predefined Rule
1 Right-click in the Policy Builder, then click New > Predefined Rule > Insert Predefined Rule
Before or Insert Predefined Rule After .
2
Select Matching - Publisher Mirrored , then click OK .
3 Expand the predefined rule.
4 Edit the condition by double-clicking the Conditions tab.
5
In the Value field, browse to and select the container in the source hierarchy where you want
the matching to start, then click OK .
6 Click OK .
7 Edit the action by double-clicking the Actions tab.
8 Delete [Enter base of destination hierarchy] from the Specify string field.
9 Click the Edit the arguments icon to launch the Argument Builder.
10 Select Text in the noun list.
11 Double-click Text to add it to the argument.
12 In the editor, click the browse button, browse to the container in the destination hierarchy
where you want the source structure to be matched, then click
OK .
13 Click Finish .
14
Save the rule by clicking File > Save .
8.11.3 How the Rule Works
This rule matches for objects in the Identity Vault by using the mirrored structure in the data store
from a specified point. When an Add event occurs and the driver checks to see if the object exists, it
starts checking at the specific DN in the data store. The driver then sets a local variable of dest-base
to be the starting point in the Identity Vault that the structure is mirrored to in the data store. The
driver then creates the context it is searching by adding the local variable of dest-base plus a \ and
the source DN of the object. It creates the path it is looking for in the slash format.