9. On
the Configure Connector Filter screen, click Next >
?
This is where you could define filters to only include objects
that have a department field equal to ?Sales,? for example.
10. Configure join and projection
rules
a.
Click on user under Data Source Object Type
b. Then
click New Join Rule? on the Configure Join and Projection Rules
screen
i)
On the Join Rule for user dialog, scroll down the ?Data source
attribute:? and select sAMAccountName
ii) Under
?Metaverse attribute:,? select uid
iii) Click Add
Condition
iv) Click OK
on the warning message that the attribute is not indexed
?
We will add an index on this attribute later to address this
issue.
v)
Confirm that your options match those below
?
This is the rule dialog where join rules are defined. In the
above example, the MA will search the metaverse for an object with a matching
value. If an object with a matching uid value is found, it will be linked
to the connector object being created by this MA.
vi) Click OK
c.
Click
New Projection Rule?
i)
Confirm that ?person? is selected under ?Metaverse object type:?
and click OK
?
The rule tells MIIS to create a new connector in the metaverse if
an existing object, one where the uid matches the sAMAccountName for the current
object in the data source being processed, does not exit. If a match is
found, the connector object will be linked to the exiting metaverse object.
If a match is not found, the projection rule is executed, which will create a
new object in the metaverse.
d.
Confirm that the join and projection rules match those below and click on
Next >
11. Configure the attribute flow
settings
a.
Confirm that ?Mapping Type? is set to Direct and ?Flow Direction?
is set to Import
b.
Select
user from the ?Data source object type:? drop-down list and
person
from the ?Metaverse object type:? drop-down list
c.
Choose ?c? under ?Data source attribute:? and ?c? under ?Metaverse
attribute? and click New
d.
Repeat for each of the following attribute pairs
|
Data source |
Metaverse |
|
cn |
cn |
|
co |
co |
|
department |
department |
|
description |
description |
|
displayName |
displayName |
|
givenName |
givenName |
|
homePhone |
homePhone |
|
info |
info |
|
initials |
initials |
|
l |
l |
|
mail |
mail |
|
mobile |
mobile |
|
postalCode |
postalCode |
|
sAMAccountName |
uid |
|
sn |
sn |
|
st |
st |
|
streetAddress |
street |
|
telephoneNumber |
telephoneNumber |
|
title |
title |
?
userAccountControl is not selected on purpose, this attribute will
be used by the rules extension later.
e.
Confirm that your selection looks similar to those below and click Next
>
12. On Configure Deprovisioning,
leave the default of Make them disconnectors and click Next
>
?
The best solution is to either create a rules extension that will
delete objects in the target domain in this scenario. This is outside the
scope of this article, but might be addressed in a later addition to the article
series.
13. On the final screen,
Configure Extensions, click Finish
