Anonymous_User Absent Member.
Absent Member.
234 views

Upgradestrategy for very old IDM-System (3.5 ->4.x)


I am faced with an IDM eDir->AD based on IDM 3.5 with components on Windows 32 Bit..



There is as strong need to replace both with newer Versions: the windows server and to update the IDM System.



I am struggling on the right way to upgrade it without losing associations and bringing the system in trouble.



How could i move the driver to freshly installed Win2012 servers with new IDM Software?



kind regards and thx

Gerd
Labels (1)
0 Likes
4 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Upgradestrategy for very old IDM-System (3.5 ->4.x)

On 04/06/2016 02:15 AM, Gertfried Zobel wrote:
>
> There is as strong need to replace both with newer Versions: the windows
> server and to update the IDM System.
>
> I am struggling on the right way to upgrade it without losing associations
> and bringing the system in trouble.
>
> How could i move the driver to freshly installed Win2012 servers with new
> IDM Software?


Since windows installs of eDirectory are not possible without creating an
instance of eDirectory itself (on Linxu/unix you can install the software,
and then configure the instance/DIB separately which really helps with
these situations) you are basically stuck with two ways to do this:

1. Use IDM Designer to "Migrate" a driverset, driver configs, etc. from
the old server to the new server. This is a function of Designer which
has come up several times in the past, and is documented as well.

Steps:

Install windows, eDirectory (adding it to the tree as a new server), and IDM.
Be sure all relevant partitions (probably all partitions) have real
(read/write or Master usually) replicas on the new box.
Add the new server to the Designer project within the Identity Vault
(right-click on the tan background of the Vault, Properties: Servers: Add:
etc.
Be sure you have all required JARs/etc. for your drivers on your new box.
This is simpler if you are using Remote Loaders (RL) wherever possible,
since those may be on other systems. If the RLs are on the local system,
be sure to move those over manually too.
Right-click on items and choose Migrate to move them over.

See the "Migrating Driver Configuration Data to a New Server" section of
the Designer documentation:
https://www.netiq.com/documentation/idm45/designer_admin/data/appmigrate.html

2. Do the above, but manually, and by creating a second driver.

The downside is that you're recreating a driver, which means you will
definitely need to copy over associations manually (trivial with LDAP, but
it's not automatic).

3. Hire somebody to do it (this forum includes partners/consultants who
do a lot of upgrades). In the grand scheme of IDM work, upgrades are
quick and easy, and since they have higher risk and visibility people
often opt to bring in outside help to just get it done quickly, properly,
and perhaps with some help to identify what, if anything, could be
improved at the same time.

I'd go with #1, but I do this for a living.

If you have a Linux box as the target system, then my favorite way of
doing migrations for customers is to build the new box like in #1, except
without adding it to the current tree permanently. Instead the DIB from
the source system is copied into the target system and then the source is
turned off, the target gets the IP of the source (preferably, not
required), and the target is turned on. The target system, then, takes
over the identity of the source system. It's a simple thing, and in
today's largely-virtualized world it is particularly attractive, even
easier to do remotely, etc..

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Knowledge Partner
Knowledge Partner

Re: Upgradestrategy for very old IDM-System (3.5 ->4.x)


Aaron already explained almost all available options.

I would like to add just one more option: Migration to new server with
iManager documented here
http://tinyurl.com/hvwsumt


--
If you find this post helpful, please show your appreciation by clicking
on the star below :cool:
------------------------------------------------------------------------
al_b's Profile: https://forums.netiq.com/member.php?userid=209
View this thread: https://forums.netiq.com/showthread.php?t=55662

0 Likes
Anonymous_User Absent Member.
Absent Member.

Antw: Re: Upgradestrategy for very old IDM-System (3.5 ->4.x)


thanks everybody for the fine answers. That was exactly the push in the right direction.

"Option 1" will be my favourite.



kind regards
0 Likes
Knowledge Partner
Knowledge Partner

Re: Upgradestrategy for very old IDM-System (3.5 ->4.x)

On Wed, 06 Apr 2016 08:15:46 +0000, Gertfried Zobel wrote:

> I am faced with an IDM eDir->AD based on IDM 3.5 with components on
> Windows 32 Bit..


Install new server.
Install eDir + IDM engine on new server.
Use Designer to migrate from old server to new server.
Done.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.microfocus.com

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.
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.