
142
Policies in Designer 3.5
no
vd
ocx
(e
n)
13
Ma
y 20
09
8.19 Placement - Subscriber By Dept - LDAP
Format
This rule places objects from one container in the Identity Vault into multiple containers in the data
store based on the OU attribute. Implement the rule on the Placement policy in the driver. You can
implement the rule only on the Subscriber channel.
There are two steps involved in using the predefined rules: creating a policy in the Placement policy
set and importing the predefined rule. If you already have a Placement policy that you want to add
this rule to, skip to
Importing the Predefined Rule
.
Section 8.19.1, “Creating a Policy,” on page 142
Section 8.19.2, “Importing the Predefined Rule,” on page 142
Section 8.19.3, “How the Rule Works,” on page 143
8.19.1 Creating a Policy
1
From the Outline view or the Policy Flow view, select the Subscriber channel.
2
Select the Placement policy set in the Policy Set view, then click
Create or add a new policy to
the Policy Set
icon to create a new policy.
3
Click
Create a new policy
, then click
Next
.
4
Name the policy.
5
Use the default location or browse and select another location to place the policy in the driver.
6
Select
Open Editor after creating policy
, then click
Next
.
7
Select
DirXML Script
for the type of policy, then click
Finish
.
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 Placement policy is saved.
9
Continue with
Importing the Predefined Rule
.
8.19.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
Placement - Subscriber By Dept - LDAP format
, then click
OK
.
Summary of Contents for Designer for Identity Manager 3.5
Page 4: ...4 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 20: ...20 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 44: ...44 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 76: ...76 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 92: ...92 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 108: ...108 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 144: ...144 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 174: ...174 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 188: ...188 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 223: ...Conditions 223 novdocx en 13 May 2009...
Page 231: ...Conditions 231 novdocx en 13 May 2009...
Page 232: ...232 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 237: ...Actions 237 novdocx en 13 May 2009...
Page 245: ...Actions 245 novdocx en 13 May 2009...
Page 247: ...Actions 247 novdocx en 13 May 2009...
Page 263: ...Actions 263 novdocx en 13 May 2009...
Page 271: ...Actions 271 novdocx en 13 May 2009...
Page 275: ...Actions 275 novdocx en 13 May 2009 Example...
Page 324: ...324 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 333: ...Noun Tokens 333 novdocx en 13 May 2009...
Page 357: ...Verb Tokens 357 novdocx en 13 May 2009...
Page 363: ...Verb Tokens 363 novdocx en 13 May 2009 Example...
Page 390: ...390 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 418: ...418 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 474: ...474 Policies in Designer 3 5 novdocx en 13 May 2009...