sma2006 Outstanding Contributor.
Outstanding Contributor.

Re: IDM Co-existence Question

I think NetIQ does not support upgrade/migration from 4.02 to 4.7 because they did not tried it, but I confirm I did it without any problem:
1) Add new servers with IDM 4.7 in the tree
2) Migrate you drivers one by one from IDM 4.02 servers to IDM 4.7 servers (use Migrate option in Designer to copy config to new servers and then deploy the driver)
3) Upgrade the Remote loader if any
4) Optionally you can upgrade the drivers configuration/package, but it's a lot of work.
5) If you have RBPM (AE edition) you must upgrade your drivers configuration (Roles, UserApp)
0 Likes
Knowledge Partner
Knowledge Partner

Re: IDM Co-existence Question

On 4/9/2019 10:24 AM, sma wrote:
>
> I think NetIQ does not support upgrade/migration from 4.02 to 4.7
> because they did not tried it, but I confirm I did it without any
> problem:
> 1) Add new servers with IDM 4.7 in the tree
> 2) Migrate you drivers one by one from IDM 4.02 servers to IDM 4.7
> servers (use Migrate option in Designer to copy config to new servers
> and then deploy the driver)
> 3) Upgrade the Remote loader if any
> 4) Optionally you can upgrade the drivers configuration/package, but
> it's a lot of work.
> 5) If you have RBPM (AE edition) you must upgrade your drivers
> configuration (Roles, UserApp)


I really think that the conversation about upgrading and requiring a
pass through a particular version (4.5.3 or 4.6.x) to get to the latest
is really about the User App/Identity Apps. And there it is really about
keeping the database intact.

We would be far better off if we could export the actual DB data, throw
away the old one, simply reinstall a new one and put back what we want.

the engine itself very rarely cares about upgrades and the path you took
it through.

Biggest compatability issues are things like Remote Loaders, needing a
JVM that matches the engine JVM so SSL/TLS/Ciphers all match. Easy to fix.

Also, the change from JDBM to MapDB to ZoomDB means you need to make
sure to update shims as well sometimes.

So always distinguish between engine and Identity Apps.

Also, there are platform support changes (Sometimes you need a new OS to
run the latest eDir which is needed by the latest IDM...)

I do wish it were simpler though.


0 Likes
Knowledge Partner
Knowledge Partner

Re: IDM Co-existence Question

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’s identity
transfer) approach. This way you are primarily constrained by eDirectory
version interoperability.

Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.