DSXchange

Hi,

We were earlier on DS 7.1 version. Now we want to move onto DS 7.5.1.

One option we had is - install DS 7.5.1 on a separate box and then export/import jobs onto it.

Rather than going for it, we were thinking of the following option:
On the same box on which DS 7.1 is running (default port), take the DS 7.1 engine down. Install DS 7.5.1 on the default port.
Start the DS 7.5.1 engine on the default port.

If something goes wrong during the 7.5.1 install then take that engine down and start the DS 7.1 again.

So both the DS 7.1 and 7.5.1 will be there on the box, but at one time one will be up.

The reason why we want to go for this is - we want to avoid one more prod box cost and if on production something goes wrong in DS 7.5.1 install, then we can keep the prod up using DS 7.1.

Is this possible? Has anyone tried this?

But 7.5.1 will over ride the 7 installation. Do you mean at different location?

Ya Kumar!!!

We have to install both versions such that 7.5.1 should not override the 7.1 install. Ya so 7.5.1 will be installed at diff location on the same server.

Read the multiserv.pdf aka the Installing Multiple Servers pdf installed on your PC with your 7.5 client. It explains the procedure. You'll install to two different locations with two different 'instance tags' and use two different ports and thus can have both up and running at the same time.

Thanks Craig! I just checked it!!

The thing is - we have some scripts where we have hard coded server name. Now if the new DS install is on port number then these script will have to be changed and if possible wer want to avoid that change.

So we were thinking of installing new DS again on the same default port and just running the any one of the DS Engines. So only 7.5.1 engine will be up for production. If something goes wrong with 7.5.1 install. We will clean it up and just start the already existing DS 7.1 engine on default port and production will not be stopped.

So is it possible?

Do you mean scripts involving Port No .
If you are referring to command line executables, it will refer to the user id to which the corresponding dsenv is configured.

We have scripts with hard code server param in the dsjob command. Does this mean using dsenv we can avoid it?

Actually we want to run DS 7.5.1 on default port is because we wanna avoid any change in the script.

If that's the way you want to play the game, then fine. As long as only one or the other is running at any given time you should be fine. You'll also need some (if not all) of your people to install both clients and install (and possibly use) the MCM or Multi-Client Manager.

Much like the Server, the clients will need to be installed in two separate locations and then the MCM can switch you between them. Unlike the Server, however, you must run only one client at a time.

Thanks a lot, Craig!!!

Before trying it out wanted inputs of some gurus like you people. I will post the result once it is done.

For Client end GUI perspective, MCM should take care.
For the command line, the DSHOME that you are referring based on the users .profile and dsenv, should take care.