Installation guide

30 Identity Manager 4.0.1 Framework Installation Guide
Server B holds replicas of the Development and Finance containers, and the Identity Management
container holding the driver set for Server B and the GroupWise Driver object for Server B.
Because Server A and Server B both hold a replica of the Finance container, both servers hold the user
JBassad, who is in the Finance container. Without scope filtering, both GroupWise Driver A and
GroupWise Driver B would synchronize JBassad.
Figure 3-5 Two Servers with Overlapping Replicas, without Scope Filtering
The next illustration shows that scope filtering prevents both instances of the driver from managing
the same user, because it defines which drivers synchronize each container.
Figure 3-6 Scope Filtering Defines Which Drivers Synchronize Each Container
Identity Manager comes with predefined rules. There are two rules that help with scope filtering.
“Event Transformation - Scope Filtering - Include Subtrees” and “Event Transformation - Scope
Filtering - Exclude Subtrees” are documented in Understanding Policies for Identity Manager 4.0.1.
For this example, you would use the Include Subtrees predefined rule for Server A and Server B. You
would define the scope for each driver differently so that they would only synchronize the users in
the specified containers. Server A would synchronize Marketing and Finance. Server B would
synchronize Development.
Identity
Manager
Server A
Finance
Driver Set Server A
GroupWise Server A
Marketing
Identity Management
JBassad
Finance
Driver Set Server B
GroupWise Server B
Development
Identity Management
JBassad
Without scope filtering,
both GroupWise drivers try
to manage user JBassad
Identity
Manager
Server B
Identity
Manager
Server A
Finance
Driver Set
GroupWise Driver A
Marketing
Identity Management
JBassad
Finance
Driver Set
GroupWise Driver B
Development
Identity Management
JBassad
With scope filtering,
only the GroupWise driver on
Server A manages user JBassad
Identity
Manager
Server B