Microsoft IDM

Identity Management

the Microsoft way

Thursday, April 26, 2007



Dual Authoritative Data Sources

I have found that in some environments it is a requirement that MIIS sync data that can be authoritative from multiple sources.After some deep thinking, I came up with a very good way of doing this.Here's how to handle it.On each ma you setup an import flow that flow to it's own metaverse attributeExample:Import FlowData Source 1 MetaversegivenName => DS1_givenNameData Source 2 MetaversegivenName => DS2_givenNameYou need to create advanced flow rule extensions to flow to each metaverse attribute.In the advanced flows you need to check if there is a null value in the data source.This is so that when one of your data sources flows a delete, the metaverse attribute gets populated with a value. You can use any type of character or characters in the metaverse to represent a null metaverse value.We do this because if you have no value in the datasource then there will be no value in the metaverse attribute. We need to have this in the metverse attribute because any time a value is flowed to the metaverse, a date value is set.We will use this date value in the advanced export flow code to determine which value is the newest value.Example:Export FlowMetaverse Data Source 1DS1_givenName + DS2_givenName => givenNameMetaverse Data Source 2DS1_givenName + DS2_givenName => givenNameIn the export flow code you need to compare the date values on each metaverse attribute by returning the LastContributionTime value from the metaverse attribute.Here's an example.mventry("metaverse attribute").LastContributionTimeOnce you figure out which value is the newest, then you can check each value to see if it is representing a null value, if it is then you should flow a delete to the data source otherwise just flow the attribute value.When implementing a solution like this, you really need to think about how everything is going to flow and what data source will take precedence from the beginning.When you project the metaverse object from the first data source and import these values, they will have that current date timestamped on the attributes.Now when you join the other data source it will also flow values to the metaverse and these attributes will be newer than the previous data source attributes because the dates are more current then the others.With some proper planning and testing this solution can be implemented without error.Good Luck...

Posted by Joe Stepongzi

at 4/26/2007 06:02:00 AM

3 comments









Newer Posts

Older Posts

Home

Subscribe to: Posts (Atom)





MVP - Identity LifeCycle Manager (2007)(2008)(2009)





About Me

Joe Stepongzi

View my complete profile





My Frequent Access Links

Almero Steyn's puttyq Brad Turner's 1dent1ty cHa0s Microsoft Identity & Access Solutions MIIS Web Forums





Blog Archive



&;&;

2009 (18)



&;&;

July (4)

Need a couple more days for Testing Make that Sunday Night!!!! MVP for 2009!!! New Version of SQL xMA due out Saturday Night!!!!



&;&;

June (1)

Delta Generator almost done!!!!



&;&;

May (4)

Big Shout out to the Ensynch family!!!! SQL xMA Delta Generator and Exports due out shortl... ILM "X" FrameWork SQL xMA 1.0 has been released! Need one more week for the ILM "X" FrameWork SQL x...



&;&;

April (9)

ILM "X" Framework has been delayed til May 1st Sharepoint Service Pack 2 is going to be Shipping ... Oracle buys Sun??? ILM "X" FrameWork Update ILM Changing to Forefront Identity Manager 2010???... Vote on the delay of ILM "2" Congratulations!!! to the newest ILM MVP&;s!!!! ILM Extensibility Framework Going to start blogging big time!!!!

&;&; 2007 (7)



&;&;

September (2)

ILM 2007 Workshop in Boston Oct. 2&3 Presenting at DEC2008 in Chicago



&;&;

July (1)

Guess Who&;s a Microsoft MVP?



&;&;

June (1)

New Extensible Management Agent Documents added to...



&;&;

May (1)

Running more than one Lotus Notes Management Agent...

&;&; April (1)

Dual Authoritative Data Sources



&;&;

February (1)

1st Post -- Let&;s get this started