IDM Co-existence Question

Is it possible to have two separate IDM environments using the same tree on a temporary basis for a staggered migration? Something like server A is running IDM 4.02 and connecting to tree A (running eDirectory 8.8.8). Server B is running IDM 4.7 and connecting to tree A (running 9.x). Can we migrate drivers from 4.02 to 4.7 one by one and would this be supported?

Thank you
Tom
  • TSchmauch,
    >
    > Is it possible to have two separate IDM environments using the same tree
    > on a temporary basis for a staggered migration? Something like server A
    > is running IDM 4.02 and connecting to tree A (running eDirectory 8.8.8).
    > Server B is running IDM 4.7 and connecting to tree A (running 9.x).
    > Can we migrate drivers from 4.02 to 4.7 one by one and would this be
    > supported?
    >
    > Thank you
    > Tom
    >
    >

    I'm not sure you can go directly from 4.02 to 4.7, but this approach
    should work for going from 4.02 to 4.6.3. I can say that because I just
    did it. I can provide high-level step-by-step instructions if you need
    them.

  • Just to be clear, there aren't "two separate IDM environments" in my
    approach. Rather, I added a new IDM 4.6.3 server to my existing driver
    set, copied the server-specific data, then stopped the driver running on
    the old server and started it on the new one.
  • 6423241 <dougperiodblack@osumcperiod.edu> wrote:
    > TSchmauch,
    >>
    >> Is it possible to have two separate IDM environments using the same tree
    >> on a temporary basis for a staggered migration? Something like server A
    >> is running IDM 4.02 and connecting to tree A (running eDirectory 8.8.8).
    >> Server B is running IDM 4.7 and connecting to tree A (running 9.x).
    >> Can we migrate drivers from 4.02 to 4.7 one by one and would this be
    >> supported?
    >>
    >> Thank you
    >> Tom
    >>
    >>

    > I'm not sure you can go directly from 4.02 to 4.7, but this approach
    > should work for going from 4.02 to 4.6.3. I can say that because I just
    > did it. I can provide high-level step-by-step instructions if you need
    > them.
    >


    you can definitely use a migrate to new server approach to go from 4.0.2 to
    4.7. without going through interim 4.6.x stage.

    I have done that recently.

    The wrinkles come with upgrading specific drivers especially user
    application, but even that can be solved.

  • On 4/2/2019 4:24 PM, TSchmauch wrote:
    >
    > Is it possible to have two separate IDM environments using the same tree
    > on a temporary basis for a staggered migration? Something like server A
    > is running IDM 4.02 and connecting to tree A (running eDirectory 8.8.8).
    > Server B is running IDM 4.7 and connecting to tree A (running 9.x).
    > Can we migrate drivers from 4.02 to 4.7 one by one and would this be
    > supported?


    The Engine is a honey badger, and the Engine don't care.

    User App is a high maintenance partner and is somewhat picky.


  • Thank you for the help! My thought was to create 2 new driver sets to get the critical drivers over to 4.7, then for the less critical ones migrate the existing to 4.7.

    The driver upgrades we did in our development environment and they were entertaining :)
  • 6423241;2497665 wrote:
    TSchmauch,
    >
    > Is it possible to have two separate IDM environments using the same tree
    > on a temporary basis for a staggered migration? Something like server A
    > is running IDM 4.02 and connecting to tree A (running eDirectory 8.8.8).
    > Server B is running IDM 4.7 and connecting to tree A (running 9.x).
    > Can we migrate drivers from 4.02 to 4.7 one by one and would this be
    > supported?
    >
    > Thank you
    > Tom
    >
    >

    I'm not sure you can go directly from 4.02 to 4.7, but this approach
    should work for going from 4.02 to 4.6.3. I can say that because I just
    did it. I can provide high-level step-by-step instructions if you need
    them.


    If you can send high level instructions, that would be very helpful. Thank you!
  • On 4/2/2019 7:54 PM, TSchmauch wrote:
    >
    > Thank you for the help! My thought was to create 2 new driver sets to
    > get the critical drivers over to 4.7, then for the less critical ones
    > migrate the existing to 4.7.


    Do not make a new driver set. Just have the 4.02 annd 4.7 servers in the
    same driver set and stop each driver on one, restart on th eother (after
    copying server specific info).


  • On 02.04.19 22:24, TSchmauch wrote:
    >
    > Is it possible to have two separate IDM environments using the same tree
    > on a temporary basis for a staggered migration? Something like server A
    > is running IDM 4.02 and connecting to tree A (running eDirectory 8.8.8).
    > Server B is running IDM 4.7 and connecting to tree A (running 9.x).
    > Can we migrate drivers from 4.02 to 4.7 one by one and would this be
    > supported?
    >
    > Thank you
    > Tom
    >
    >


    To my understanding, you cannot officially go directly from 4.0.2 to
    4.7. You need 4.5.6 or 4.6.x

    The documentation for 4.6 spells out that you need 4.5 if you come from
    4.0.2.

    The easiest is 4.0.2 -> 4.5.6 -> 4.7

    Documentation:
    https://www.netiq.com/documentation/identity-manager-47/setup_linux/data/supported-upgrade-paths.html



    Casper
  • On 4/3/2019 5:23 AM, Casper Pedersen wrote:
    > On 02.04.19 22:24, TSchmauch wrote:
    >>
    >> Is it possible to have two separate IDM environments using the same tree
    >> on a temporary basis for a staggered migration?  Something like server A
    >> is running IDM 4.02 and connecting to tree A (running eDirectory 8.8.8).
    >> Server B is running IDM 4.7 and connecting to tree A (running 9.x).
    >> Can we migrate drivers from 4.02 to 4.7 one by one and would this be
    >> supported?
    >>
    >> Thank you
    >> Tom
    >>
    >>

    >
    > To my understanding, you cannot officially go directly from 4.0.2 to
    > 4.7. You need 4.5.6 or 4.6.x
    >
    > The documentation for 4.6 spells out that you need 4.5 if you come from
    > 4.0.2.
    >
    > The easiest is 4.0.2 -> 4.5.6 -> 4.7
    >
    > Documentation:
    > https://www.netiq.com/documentation/identity-manager-47/setup_linux/data/supported-upgrade-paths.html


    Is that really an engine issue or just a UA issue?

  • Casper Pedersen <cpedersen@no-mx.forums.microfocus.com> wrote:
    > On 02.04.19 22:24, TSchmauch wrote:




    >
    > To my understanding, you cannot officially go directly from 4.0.2 to
    > 4.7. You need 4.5.6 or 4.6.x
    >
    > The documentation for 4.6 spells out that you need 4.5 if you come from
    > 4.0.2.
    >
    > The easiest is 4.0.2 -> 4.5.6 -> 4.7
    >
    > Documentation:
    > https://www.netiq.com/documentation/identity-manager-47/setup_linux/data/supported-upgrade-paths.html
    >


    This is for an in-place upgrade and is due to JRE constraints as far as I
    know.

    I was referring to a migrate to new IDM server (or Aaronâ€Tms identity
    transfer) approach. This way you are primarily constrained by eDirectory
    version interoperability.