How to Install Second instance of IDM on same Tree

[dkoepke]

Current Old Environment

IDM 4.0.2

• Context IDM.<School Name>.Vault

2 - SLES 11.3

eDirectory - 8.8 SP8

• Tree "Vault"

Running Drivers

• JDBC (2)
• Google
• AD
• eDirectory

Projected new Environment

IDM 4.7.3

• Context IDM2.<School Name>.Vault

2 - SLES 12.4

eDirectory – 9.1.3

• Tree "Vault"

Running Drivers 

• Delimited

The old environment is being phased out and the school is moving from the old Database school system to a cloud based system with data access from downloads.

I have installed two SLES server (12.4) in a new context within the same tree.

The goal is to install IDM 4.7.3 in the new context, install / configure the delimited driver to process the new data format.

The old drivers will be migrated from the 4.0.2 IDM to 4.7.3 IDM one at a time after validation before addressing the next driver. The JDBC drivers will not be migrated and no driver will be running in both environments at the same time. After all is migrated to 4.7.3 the old IDM system will be removed and SLES 11.3 server also removed

I looked through the silent.properties options but may be missing the correct combination

I need to install 4.7.3 without touching the old 4.0.2 version.

Is there an option to install but not upgrade current systems?

Thanks

Dan

[al_b · Accepted solution]

Hi Dan,

You in the right direction.

>The old drivers will be migrated from the 4.0.2 IDM to 4.7.3 IDM one at a time after validation before addressing the next driver.

I use for my migration same approach.

[geoffc]

I think Alex missed an important point, which is, do NOT make a new driverset in a new context. Instead add a new server with new IDM into the existing driverset and move the drivers over one by within the driverset, simply by disabling on the old server and running on the new one.

The only real compatability issue will be the User App which needs to run the right driver and Web app at the same time so move them together.  There reinstalling a new instance may just be easier.  But a new web app not a new IDM system.

[al_b]

>do NOT make a new driverset in a new context. 

It depends... Sometimes creation of new driverset will have a sense...

Simple driver disabling on the old server and enabling on the new server, when both servers part of the same driverset,  remove needs to fix driver associations.

[geoffc]

True enough.  There are always exceptions.

In general if doing an upgrade, it is rarely a good idea to make a new driver set.

[dkoepke]

Thanks for everyone's input
I'm like the idea of a new clean system but I understand there are pros and cons of using the old driver set vs new driver set.
This system been running for at least ten years and the school is happy with all that it does.

One area that I not sure and I'm maybe missing the correct doc is the IDM version.
At one point I see a line that only 4.5 or above can be migrated to 4.7.
So based on that line and using the old driver set, do I need to either install 4.0.2 on the second server and upgrade the new server after everything is moved and tested or do I need to upgrade the 4.0.2 to 4.5 or above?

Preferred model can I install 4.7 on the second server and able to migrate to the new server / 4.7

Also, and I feel stupid with this question. But every time I try to install 4.7 it asks to upgrade the current 4.0.2 environment.
What is needed to not upgrade the 4.0.2 or is later in the process I have a more options?

I am setting up a test model in a virtual environment to test my questions.
IDM is mission critical to the school and school starts soon so I can not impact the school

Thanks
Dan