Select Attributes
 In
our case, we are selecting a few more attributes than required per
our list of requirements, but the additional fields we have
identified will allow us to better connect the directories now and
for later projects.
You will certainly need to select the Show All
checkbox to get to all of these attributes:
c
cn
co
company
containerInfo
department
description
displayName
facsimileTelephoneNumber
givenName
info
initials
l
mail
mailNickname
mAPIRecipient
middleName
mobile
msExchHideFromAddressLists
msExchPoliciesExcluded
name
nTSecurityDescriptor
o
otherTelephone
ou
pager
physicalDeliveryOfficeName
postalAddress
postalCode
proxyAddresses
sAMAccountName
sn
st
street
streetAddress
targetAddress
telephoneNumber
textEncodedORAddress
title
Configure Connector Filter
The connector filter is used to specify things we
do not want to replicate. In our environment, we have chosen not to
replicate anything that does not have mail address. We have also chosen
not to replicate hidden objects. We could have just as easily filtered
based on certain key words in the Custom Attribute field or similar. The
object types you see listed in this window are specific to Active
Directory.
group –distribution list
user-mailbox
contact –custom recipient
These are the only objects you really need to focus
on when building filters in this AD management agent.
Configure Join and Projection Rules
You will need to add two rules to each of the
object types you wish to synchronize. In this example, we added the
following:
contact
- Declared Projection Rule based on the
Metaverse_Contact object type.
- Direct Join rule based on the mail field
between the “mail” data source attribute and the “mail” attribute on
“Metaverse_Contact.
Group
- Declared Projection Rule based on the
Metaverse_Contact object type.
- Direct Join rule based on the mail field
between the “mail” data source attribute and the “mail” attribute on
“Metaverse_Contact.
user
- Declared Projection Rule based on the
Metaverse_Contact object type.
- Direct Join rule based on the mail field
between the “mail” data source attribute and the “mail” attribute on
“Metaverse_Contact.
You should notice that the projection rules follow
the join rules. You can create multiple join rules for each object type
and you can specify custom rules to handle joins. For our purposes, the
standard mail mapping fields will suffice.
Configure Attribute Flow
This step will likely take the most time and you
should pay close attention to the detail. As we map fields from AD to
the metaverse and visa-versa we have to pay close attention to the flow
direction as well as any advanced rules we need to apply. As you will
find out, standard mapping rules will allow us to meet our objectives.
From the Configure Attribute Flow screen, you can see that we are
configuring flow for all three object types we wish to synchronize.
|
