Quantcast
Channel: Forum Microsoft Identity Manager
Viewing all articles
Browse latest Browse all 4767

I read a book and I read something that I need help to understand

$
0
0

Hello!

Below is text from a book that has been used in a course for Managing Microsoft Metadirectory Service 2003.
I know the book is old but most in the book is correct even today.

Here is the text.
"It is legal for more than one object from a connected directory to be joined to the same Metaverse object. However, it is not then possible to have inbound attribute flows(although export flows are allowed). This is because the synchronization engine cannot establish precedence between the competing connectors - which connector's attribute should flow inbound to the metaverse? Therefore, if you have inbound attribute flows, and the join rules would allow more than one CD object to join to the same MV object, the second(and subsequent) joins fail with "ambiguous-join-error", The first join made remains, but no sebsequent joins will be completed."

Note I just use the Synchronization Service Manager and no FIM Portal

I have two agent called agent-AD and agent-HR that simply consist of a simple database.
Assume I have an attribute in agent-AD that is called my_AD_Attribute that I read from the db and an attribute in agent-HR that is called my_HR_attribute that I also read from the db.
In MV I have the same two attributes called  my_AD_Attribute and my_HR_Attribute. I will have no problem to use import flow the CS attribute my_AD_Attribute into the MV attribute  my_AD_Attribute and no problem to do the same with  my_HR_Attribute.

Can somebody explain what the text is trying to explain because I don't understand what it means

//Tony


Viewing all articles
Browse latest Browse all 4767

Trending Articles