Micro Focus Contributor
Micro Focus Contributor
155 views

IDM 3.5 upgrade


Good afternoon,

We have IDM 3.5.2 (I believe that is the correct version) and are
looking to upgrade the product to the latest (version 4.0.1) what is the
best method for doing so, and is there a Best practices guide that would
be able to walk us through the general procedure on how to "properly"
upgrade (update) the software. We currently have two drivers eDir to
eDir (eDirectory) and eDir to AD (the Vault server to AD).

Any thoughts would be most appreciated.

DS


--
dschaldenovell
------------------------------------------------------------------------
dschaldenovell's Profile: http://forums.novell.com/member.php?userid=93234
View this thread: http://forums.novell.com/showthread.php?t=454833

Labels (1)
0 Likes
3 Replies
Knowledge Partner
Knowledge Partner

Re: IDM 3.5 upgrade

On 4/19/2012 12:16 PM, dschaldenovell wrote:
>
> Good afternoon,
>
> We have IDM 3.5.2 (I believe that is the correct version) and are
> looking to upgrade the product to the latest (version 4.0.1) what is the
> best method for doing so, and is there a Best practices guide that would
> be able to walk us through the general procedure on how to "properly"
> upgrade (update) the software. We currently have two drivers eDir to
> eDir (eDirectory) and eDir to AD (the Vault server to AD).


The docs are basically pretty good for this.

Core issues is you need eDir 8.8.6 on a supported platform to run IDM 4 on.
The only reason that matters more than previous (pre 3.6) upgrades is
that Netware is not supported on IDM 3.6 or 4.

So you could simply add a supported platform (SLES, AIX, Winders, etc)
with eDir to your tree. Then install IDM4 on it.

Then add it to your driverset. Easier to use Designer to migrate to the
new server, since that properly copies the server specific attributes.
But easy enough to do by hand. I did 5 drivers this way a couple of
weeks ago, and I can get it done in about 5-10 minutes per server.

Remote Loader side, nice to upgrade to latest RL and latest shim, but
not 100% required. Shim upgrade is important (bug fixes, new features)
but RL mostly works fine.

When done you have the driverset on two servers (perfectly normal) and
all drivers running on the new server, disabled on the old one.

Then you remove the old server, and now you are mostly done. (Don't
forget to license the tree with the IDM4 license, etc... But that is
just details).


0 Likes
Micro Focus Contributor
Micro Focus Contributor

Re: IDM 3.5 upgrade


geoffc;2190207 Wrote:
> On 4/19/2012 12:16 PM, dschaldenovell wrote:
> >
> > Good afternoon,
> >
> > We have IDM 3.5.2 (I believe that is the correct version) and are
> > looking to upgrade the product to the latest (version 4.0.1) what is

> the
> > best method for doing so, and is there a Best practices guide that

> would
> > be able to walk us through the general procedure on how to

> "properly"
> > upgrade (update) the software. We currently have two drivers eDir to
> > eDir (eDirectory) and eDir to AD (the Vault server to AD).

>
> The docs are basically pretty good for this.
>
> Core issues is you need eDir 8.8.6 on a supported platform to run IDM 4
> on.
> The only reason that matters more than previous (pre 3.6) upgrades is
> that Netware is not supported on IDM 3.6 or 4.
>
> So you could simply add a supported platform (SLES, AIX, Winders, etc)
> with eDir to your tree. Then install IDM4 on it.
>
> Then add it to your driverset. Easier to use Designer to migrate to
> the
> new server, since that properly copies the server specific attributes.
> But easy enough to do by hand. I did 5 drivers this way a couple of
> weeks ago, and I can get it done in about 5-10 minutes per server.
>
> Remote Loader side, nice to upgrade to latest RL and latest shim, but
> not 100% required. Shim upgrade is important (bug fixes, new
> features)
> but RL mostly works fine.
>
> When done you have the driverset on two servers (perfectly normal) and
> all drivers running on the new server, disabled on the old one.
>
> Then you remove the old server, and now you are mostly done. (Don't
> forget to license the tree with the IDM4 license, etc... But that is
> just details).



When you mentioned the license for IDM 4, are you referring to the
activation license for the driver set, along with the activation code
itself for 4? Or is this another license that your referring too? Thanks
for the clear description in the upgrade steps.


--
dschaldenovell
------------------------------------------------------------------------
dschaldenovell's Profile: http://forums.novell.com/member.php?userid=93234
View this thread: http://forums.novell.com/showthread.php?t=454833

0 Likes
Knowledge Partner
Knowledge Partner

Re: IDM 3.5 upgrade

On 4/25/2012 11:56 AM, dschaldenovell wrote:
>
> geoffc;2190207 Wrote:
>> On 4/19/2012 12:16 PM, dschaldenovell wrote:
>>>
>>> Good afternoon,
>>>
>>> We have IDM 3.5.2 (I believe that is the correct version) and are
>>> looking to upgrade the product to the latest (version 4.0.1) what is

>> the
>>> best method for doing so, and is there a Best practices guide that

>> would
>>> be able to walk us through the general procedure on how to

>> "properly"
>>> upgrade (update) the software. We currently have two drivers eDir to
>>> eDir (eDirectory) and eDir to AD (the Vault server to AD).

>>
>> The docs are basically pretty good for this.
>>
>> Core issues is you need eDir 8.8.6 on a supported platform to run IDM 4
>> on.
>> The only reason that matters more than previous (pre 3.6) upgrades is
>> that Netware is not supported on IDM 3.6 or 4.
>>
>> So you could simply add a supported platform (SLES, AIX, Winders, etc)
>> with eDir to your tree. Then install IDM4 on it.
>>
>> Then add it to your driverset. Easier to use Designer to migrate to
>> the
>> new server, since that properly copies the server specific attributes.
>> But easy enough to do by hand. I did 5 drivers this way a couple of
>> weeks ago, and I can get it done in about 5-10 minutes per server.
>>
>> Remote Loader side, nice to upgrade to latest RL and latest shim, but
>> not 100% required. Shim upgrade is important (bug fixes, new
>> features)
>> but RL mostly works fine.
>>
>> When done you have the driverset on two servers (perfectly normal) and
>> all drivers running on the new server, disabled on the old one.
>>
>> Then you remove the old server, and now you are mostly done. (Don't
>> forget to license the tree with the IDM4 license, etc... But that is
>> just details).

>
>
> When you mentioned the license for IDM 4, are you referring to the
> activation license for the driver set, along with the activation code
> itself for 4? Or is this another license that your referring too? Thanks
> for the clear description in the upgrade steps.


You got it.


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.