none
Changing anchor SQL management Agent RRS feed

  • Question

  • We have SQL Management agent used for creating accounts in AD/LDAP.

    Achor is Accountname , we generate it based on Fname and lname when a record is added to SQL.

    Join is AccountNumber ( which is another unique entry)

    Now we want to change Anchor for SQL to some other attribute in SQL-  we want to use column number as a new anchor.

    My understanding is if we change anchor , it will generate a record in FIM for all the objects present.

    Any suggestion or steps for changing anchor for SQL  without affecting current users in SQL / AD ?



    AdiKumar


    • Edited by Adi Kumar Friday, February 19, 2016 9:13 AM
    Friday, February 19, 2016 9:12 AM

All replies

  • Hi,

    you can of course change the anchor without createing duplicate entries in MV.

    Check you Object Deletion Rule im MV Designer so objects are not deleted if Disconnects happens from SQL MA.

    Having "when last connector disconnects" is a good setting.

    Clear connector space of SQL MA.

    Change the anchor.

    Do a Full Import and Full Sync to re-join the object. You are then in the state like before but with the new anchor in SQL MA.

    /Peter


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    • Proposed as answer by UNIFYBobMVP Sunday, February 21, 2016 12:54 PM
    Friday, February 19, 2016 11:37 AM
  • Peter is correct, but FIRST you MUST take steps to make sure that when the disconnect occurs your new CS objects will be able to join (unambiguously, 1-1) to the same Metaverse object again.  This is because the old CS object from source will no longer exist and will be replaced by a brand new CS object (with new anchor) - and by default on disconnect any Metaverse attributes which are only contributed from the source MA will be "recalled" (removed).  There will be a number of ways to engineer the correct "rejoin" - including breadcrumbing a secondary connector and then contributing a value from that same connector with a precedence of 2 - thereby causing the Metaverse attribute to "stick".  Resist the urge to turn on the MA checkbox that says "do not recall attributes" (this is being obsoleted because it almost always leads to orphaned Metaverse attributes).

    Bob Bradley (FIMBob @ TheFIMTeam.com) ... now using FIM Event Broker for just-in-time delivery of FIM 2010 policy via the sync engine, and continuous compliance for FIM

    Sunday, February 21, 2016 1:04 PM