Jorge's Quest For Knowledge!

All You Need To Know About Identity And Security On-Premises And In The Cloud. It's Just Like An Addiction, The More You Have, The More You Want To Have!

(2010-08-17) ILM/FIM Sync Engine Terminology

Posted by Jorge on 2010-08-17


The past week I delivered the FIM 2010 Foundation course that is made available by Oxford Computer Group. One of the things I noticed is that people struggle with all the terms and abbreviations. Because of that I promised my attendees to create a nice picture and include explanations. So here goes!

The picture below shows all possible actions that can be execute through one or more Run Profiles which have one or more steps.

image

MA = Management Agent

CS = Connector Space

MV = Metaverse

INBOUND ATTRIBUTE FLOW [1]: This flow is either caused by executing a Full Sync (touching all objects in the CS) or a Delta Sync (touching only changed objects in the CS) on a certain MA. This is the flow of data from a connector space object to a metaverse object. This only applies to CS objects that are in the same MA as for which the Run Profile was executed.

OUTBOUND ATTRIBUTE FLOW [2]: This flow is either caused by executing a Full Sync (touching all objects in the CS and corresponding MV objects) or a Delta Sync (touching only changed objects in the CS and corresponding MV objects) on a certain MA. This is the flow of data from a metaverse object to a connector space object in any affected MA. This applies to CS objects that are in the same MA as for which the Run Profile was executed and all other MAs that are affected by the inbound attribute flow from the MA as for which the Run Profile was executed.

PROJECTION [3]: This is the creation of a metaverse object based upon a connector space object when executing a Full Sync (touching all objects in the CS) or a Delta Sync (touching only changed objects in the CS). This only occurs when at least one projection rule has been configured in the MA and/or Sync Rule and when no joining rule was satisfied and when the connector filter in the MA is not met. This only applies to CS objects that are in the same MA as for which the Run Profile was executed. After projection, provisioning and inbound/outbound attribute flow may occur.

PROVISIONING [4]: This is the creation of a connector object based upon a metaverse object when executing a Full Sync (touching all objects in the CS and corresponding MV objects) or a Delta Sync (touching only changed objects in the CS and corresponding MV objects). This only occurs when provisioning is enabled in the metaverse and when either a Provisioning Rules Extension exists with provisioning code for one or more MAs or when an Outbound Sync Rule has been configured for one or more MAs with the option to create a resource in the target system. This only applies to MV objects that were "touched" because of the execution of Full/Delta Sync Run Profile on a certain MA.

JOINING [5]: This is the matching of connector space object with a metaverse object based upon certain (unique) identity data (e.g. employeeID) when executing a Full Sync (touching all objects in the CS) or a Delta Sync (touching only changed objects in the CS). This only occurs when at least one join rule has been configured in the MA and/or Sync Rule and when the connector filter in the MA is not met. This only applies to CS objects that are in the same MA as for which the Run Profile was executed. After joining, inbound/outbound attribute flow may occur.

IMPORT: This is the import of scoped data from a connected data source into the corresponding connector space. Either a Full Import or a Delta Import cam be performed. A Full Import just asks for all scoped data, whether or not it is new or has changed, and the sync engine determines new objects and/or changes by comparing it against existing CS objects. A Delta import asks the connected data source for the changes (assuming it can provide those) and the sync engine processes those changes.

EXPORT: This is the export of new/changed data (pending exports – adds, updates, deletes) from the connector space into the connected data source. Exports are always delta. Some connected data sources may want or expect a Full Export and it that case you would need to create your own MA for those connected data sources that expect it.

UPDATE 2013-01-15:

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER:
https://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
#########
http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————

3 Responses to “(2010-08-17) ILM/FIM Sync Engine Terminology”

  1. Hi Jorge,
    just what the doctor ordered..
    thank you!
    Chris

  2. Mikael Puusaari said

    Nice reading, but you made a rookie-mistake with the image with helicopter-view of the sync engine

    The management-agent is rather located over the CS-area than between the CS and CD, for example it handles export to other CDs CS when you make a sync in a contributing MA, but also the import from CD to CS. As far as i know it doesnt handle it doesnt handle exports, since that data is handled and ready to be exported

    The import/export(step 1&2 in the Image) sides in the attribute flow tab in the MA is often confusing new IDM-techs since it has more to do with what happens inside the synchronization than in the import/export, ive explained this to many struggling with the terminology

    Right me if im wrong, always willing to learn more

    • Jorge said

      Hi,

      Thanks for your comment. However, this is for sure NOT rookie-mistake. The blue part of the “donut” shows you the connector space of each connected data source. The MA is shown this way to specify that’s the part that contains the logic and information of how to interact with the connected data source.

      Thanks,
      Jorge

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: