Building relationships between MV Objects to flow data
One thing that has always frustrated me with MIIS/ILM is the inability to build relationships between MV objects and flow data between them in some manner. It's trivial to join CS objects to MV objects and flow data between them, but the problem comes when you need both those objects to exist in the MV to be managed by the portal.In the portal I have the person object which I want to manage attributes like Name, Department, Location, etc. In the portal I also have account objects which have the same employeeID as the person object. When the person object changes location, the account objects with that same employeeID should also be updated with that value from the person object. Since both the person object and the account object are MV objects, there is no join and flow concept in Sync services between MV objects.I believe this can be done with MPRs and workflow activities using the enumerate resources activity, but I am concerned about the scalability of such logic. The relationship is built on the fly by enumerating the resources on the common key, and each attribute could have it's own MPR and workflow associated with it.This would have to be run continually since there is no clear relationship defined. In a large environment this could also be updating large amounts of data between those objects, so this could impact performance.Other possible solutions I see are:1 - Exporting the person profile to an ADLDS insance, and using a second Sync server to import that into the MV. Then having allmanaged systems do your classic join scenario. This way objects can be managed in the Portal instance, and any changes would be reflected in the underlying accounts associated with that person. The added cost and complexity would be an issue though, but might be better than theperformance impact to thePortal which is customer facing.PortalA -> SyncA -> ADLDS -> SyncB -> Connected Systems2 - Use Multiple MAs for each connected system on the Sync Service behind the Portal. The first one would project it's accounts in to be managed by the Portal, and the 2nd MA would join those accounts to theMV person object with export rules to flow Portal person updates toeach account. This could become unwieldly and impact theSync Services servicingthe Portal.Any other thoughts or suggestions on this?
July 17th, 2009 7:58pm

This is great feedback, and I will file a bug on your behalf. If you also want to submit this feedback in your own bug, please feel free to use http://connect.microsoft.com and use the feedback link there.AhmadAW
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2009 11:38pm

Ahmad,If you create the bug, I'll go in and mark it as an issue.Thanks!Jef
July 20th, 2009 11:53pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics