none
Requests not generating with Built in Sync Account on FIM Portal RRS feed

  • Question

  • Hello All,

    While exporting the attributes to FIM Portal, for few attributes the request is not generating from built in sync account which was being generated earlier. Has anyone seen any such scenario in which the requestor - built in sync account is not able to generate the requests in FIM portal? Despite the fact, the attribute's value is being updated for the user in the FIM Portal and I can see the attribute's updated value and the time in metaverse is changed too for the same attribute. As of now i believe that whenever any attribute of user changes and requestor is FIM Portal Administrator/Built In Sync Account/any other requestor, the request is generated but in our production environment the requests are not generating properly when exporting the changes to FIM Portal specially from built in sync account.

    Can anyone help me with this? Quick replies are highly appreciated in advance.

    Regards,

    Manuj Khurana

    Wednesday, February 26, 2014 1:58 PM

Answers

  • Probably you see a msidmCompositeType request in a portal and this is "boundle" of requests executed by FIM Synchronization service. Example how to dig into it:

    http://social.technet.microsoft.com/wiki/contents/articles/20284.fim-2010-r2-how-to-search-for-request-details-in-msidmcompositetype.aspx


    Tomek Onyszko, memberOf Predica FIM Team (http://www.predica.pl), IdAM knowledge provider @ http://blog.predica.pl

    • Marked as answer by Manuj Khurana Friday, February 28, 2014 2:12 PM
    Wednesday, February 26, 2014 2:30 PM
  • Hello,

    It's due to the "aggregate function" of FIM MA. When FIM MA exports lot of modification, it creates an object called msdidmCompositeType. This object replaces all requests.

    If you don't want this function and to create one request per modification (used for MPR for example), you have to edit the miiserver.exe.config file in BIN folder of Synchronization Service installation folder, and add the attribute aggregate="false" like following :

    Find current entry: <resourceSynchronizationClient />

    And replace by : <resourceSynchronizationClient aggregate="false"/>

    Note that it could reduce performance...

    Regards,

    Antho



    • Edited by Antho09 Wednesday, February 26, 2014 3:05 PM
    • Proposed as answer by kmittal82 Wednesday, February 26, 2014 7:46 PM
    • Marked as answer by Manuj Khurana Friday, February 28, 2014 2:12 PM
    Wednesday, February 26, 2014 2:54 PM

All replies

  • Probably you see a msidmCompositeType request in a portal and this is "boundle" of requests executed by FIM Synchronization service. Example how to dig into it:

    http://social.technet.microsoft.com/wiki/contents/articles/20284.fim-2010-r2-how-to-search-for-request-details-in-msidmcompositetype.aspx


    Tomek Onyszko, memberOf Predica FIM Team (http://www.predica.pl), IdAM knowledge provider @ http://blog.predica.pl

    • Marked as answer by Manuj Khurana Friday, February 28, 2014 2:12 PM
    Wednesday, February 26, 2014 2:30 PM
  • Hello,

    It's due to the "aggregate function" of FIM MA. When FIM MA exports lot of modification, it creates an object called msdidmCompositeType. This object replaces all requests.

    If you don't want this function and to create one request per modification (used for MPR for example), you have to edit the miiserver.exe.config file in BIN folder of Synchronization Service installation folder, and add the attribute aggregate="false" like following :

    Find current entry: <resourceSynchronizationClient />

    And replace by : <resourceSynchronizationClient aggregate="false"/>

    Note that it could reduce performance...

    Regards,

    Antho



    • Edited by Antho09 Wednesday, February 26, 2014 3:05 PM
    • Proposed as answer by kmittal82 Wednesday, February 26, 2014 7:46 PM
    • Marked as answer by Manuj Khurana Friday, February 28, 2014 2:12 PM
    Wednesday, February 26, 2014 2:54 PM