Understanding Attribute Flow in ILM 2
Hello I'm familiar with MIIS 2003 and new to ILM 2. I have been running through the TechNet scenarios and still am unclear as the best place to flow attributes (from the MA or the Sync Rule in the portal)If I understand correctly the Sync Rule in the portal allows you to create attributes in related connector spaces rather than having to write code to do so in the previous version. It also appears that you can flow attributes from the MA or the Sync rule. Is one better than the other ?I have set up the scenario 2 under the TechNet examples; its supposed to create a group in AD with members from the portal. The group is successfully created. The sync rule is set to flow a number of attributes including members. The metevers shows the group as well as all the attributes defined in the sync rule. In the ad connector space the group is present but only appears to flow the four attributes that were check as initial flow only in the sync rule. Subsequent syncs never flowed the additional attributes. The only way I was able to get it to work was to add the attribute flow to the MA rather than the sync rule. Is this to be expected? Am I missing something?
June 9th, 2009 7:38pm
In Sync Rules: 1) You can easily create the objects in the ILM Portal 2) Do simple string manipulation without writing code 3) Use scoping to handle multiple connectors in one MA a little betterIn Sync Rules you can't: 1) Process multi-value to single value handling (like Notes) 2) Do complex/advanced processinghandling outside of Workflow activities 3) Do pre-processing of data prior to in getting into the MetaverseIn consulting parlance, "It depends on you needs"... That is just an off the cuff... EricEric
June 9th, 2009 11:12pm
Thanks Eircthat makes sense. Any idea why I'm unbale to get attributes to flow from the portal to AD if they are not checked for "initial flow only"
June 11th, 2009 12:38am
My first thought would be attribute precedence.. In RC0 there is an issue where the ILM MA wants to be the highest precedence source everytime the Synch Rule object is imported and processed.After a little more thought, I would add on other point to using Portal vs "classic" ILM. In the portal, you can use workflow activities to make changes to objects not directly related to current object. In ILM 2007, you can only make changes to the connector space object or the associated Metaverse objects. This make is hard in situation where you want to update another object based on changes to the first without going external. Granted, it's not a classic vs. Sync Rule discussion but it is something that I'm going to use a lot in my current engagement.Eric
June 11th, 2009 3:07pm