eDirectory bi-directional driver

We are looking to upgrade to IDM 4.7 (linux) from IDM 4.5 in one of our trees, and it will need to connect to a legacy tree (IDM 4.0.x with eDir 8.8.x). Will the eDirectory bi-directional driver in 4.7 connect to the older IDM eDirectory bi-directional driver in the older tree?
  • schwoerb;2484563 wrote:
    We are looking to upgrade to IDM 4.7 (linux) from IDM 4.5 in one of our trees, and it will need to connect to a legacy tree (IDM 4.0.x with eDir 8.8.x). Will the eDirectory bi-directional driver in 4.7 connect to the older IDM eDirectory bi-directional driver in the older tree?


    Bi-directional driver required change-log module on eDir server. It has dependencies to eDir and no dependencies to IDM engine.
    Bi-directional driver 4.7 change-log module can run on eDirectory 8.8.8x


    https://www.netiq.com/documentation/identity-manager-47-drivers/bidirect_edirectory/data/b946tst.html
    For the Bidirectional eDirectory driver to work, you must install the change-log module on the remote eDirectory server. The change-log enables the driver to recognize changes that require publication from the remote eDirectory to the Identity Vault. The change-log module is supported on the following eDirectory versions:

    9.1.x
    9.0.x
    8.8.8.x
  • On 7/23/2018 5:54 PM, al b wrote:
    >
    > schwoerb;2484563 Wrote:
    >> We are looking to upgrade to IDM 4.7 (linux) from IDM 4.5 in one of our
    >> trees, and it will need to connect to a legacy tree (IDM 4.0.x with eDir
    >> 8.8.x). Will the eDirectory bi-directional driver in 4.7 connect to the
    >> older IDM eDirectory bi-directional driver in the older tree?

    >
    > Bi-directional driver required change-log module on eDir server. It has
    > dependencies to eDir and no dependencies to IDM engine.
    > Bi-directional driver 4.7 change-log module can run on eDirectory
    > 8.8.8x


    It has an inverse dependency. :) You cannot install Changelogon a box
    that once had IDM installed on it. (Unless they fixed that). The
    cldxevent module and dxevent module are mighty similar and conflict in
    funny ways, apparently.