none
Migrating an ECMA1 to an ECMA2 RRS feed

  • Question

  • Hi all,

    I have several custom ECMA1 MAs that have started to behave pretty badly after I upgraded to FIM R2, as there are some undocumented changes in the way FIM reacts to exceptions thrown by the MAs.

    I would need to "migrate" my old custom management agents to ECMA2 management agents, and I was wondering if there would be a way to change the type of the existing ones to Extensible Connectivity 2 without creating a brand new MA and re-configuring everything, and migrating all the existing data.

    Is this possible at all?


    Paolo Tedesco - http://cern.ch/idm

    Wednesday, June 10, 2015 3:48 PM

Answers

All replies

  • Paolo

    Unfortunately for you (and many of us in the same boat as yourself, facing the same problem at many sites) the answer is no - it's not possible to upgrade an existing MA in this way.  Of course, if you have used declarative sync rules you have even more of a challenge because of the way the SRs cannot be 'transferred' to a new MA via the FIM web UI.  You can, however, achieve this outcome by exporting and re-importing the sync rules via PowerShell - if you have this problem let me know and I can look at posting some scripts on the FIMTeam community site that I have developed to do this.

    Of course this doesn't help with precedence :/ ... however if you introduce your new MA in parallel with your existing one, you will be able to fix precedence in your lab and deploy (via server export/import) to your production environment so at least you can manage the transition (precedence of each attribute contributed by your new ECMA2 MA are 1 less than the existing ECMA1 attributes).

    It would be fantastic if there WAS a way of retaining the connector spaces of these MAs, or transferring them to new ones, but there's no supported way of doing this.  Maybe we should ask the FIM PG for such a feature?


    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

    • Proposed as answer by UNIFYBobMVP Friday, June 19, 2015 3:17 PM
    Friday, June 19, 2015 3:00 PM
  • Hi Bob,

    Thanks for the answer and the tips.

    I'm using declarative provisioning, but my rules are pretty simple. I'll see if it's worth writing a migration script, but in case I think I can manage to write it, thanks :)

    For me the worst part of the migration would be re-importing and re-joining existing data, because usually it takes a lot of time (several hours).

    How can we request the PG for a connector space migration tool?


    Paolo Tedesco - http://cern.ch/idm

    Friday, June 19, 2015 3:26 PM
  • Done :)

    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

    • Marked as answer by Paolo Tedesco Monday, June 22, 2015 7:30 AM
    Friday, June 19, 2015 3:36 PM
  • Awesome :)
    You submitted the request through Connect? Is there a link where I can check the status of the request?

    Thanks,
    Paolo


    Paolo Tedesco - http://cern.ch/idm

    Monday, June 22, 2015 7:29 AM
  • Sorry no, Paolo - Connect isn't for anything that has RTM'd.  I have raised this issue for discussion with the PG via a private channel - will let you know if anything comes of it.  I suggest you make your own plans for now.

    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

    Monday, June 22, 2015 7:34 AM
  • Ok, I see.

    Well, I expect that even if something comes out of this, it will not be for the immediate future in any case :)

    Thanks again for all your help.


    Paolo Tedesco - http://cern.ch/idm

    Monday, June 22, 2015 7:41 AM