Author |
Message
|
sharonv |
Posted: Tue Dec 02, 2014 7:40 am Post subject: upgrade MQ7.01 to MQ7.5 issue |
|
|
Apprentice
Joined: 03 Feb 2011 Posts: 27
|
Hi
We are working with MQ 7.0.11 on linux redhut
and planning to migrate to 7.5
my plan was to install MQ 7.5 side by side with 7.0.1
then after testing migrate qmgr at a time to the 7.5 environment
the idea was to create qmgr with the same names config ,ports and when i want to test the 7.5 qmgr i take off the 7.0.1 , untill my test are ok and i remove /stop the 7.0.1
after installing 7.5.0.4 side by 7.0.1 i noticed that the mqs.ini file is shared between the versions , so therefore i cant create new 7.5 qmgrs with the same name as 7.0.1
its quite an issue to change qmgr name , since it effect the application , which some of them have an hard coded configuration
What the best way to continue ? ( assuming i dont have another computer to install 7.5 on a clean environment )
Please advice |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Dec 02, 2014 7:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Sit down with the application developers and ask them how to solve this problem. |
|
Back to top |
|
 |
sharonv |
Posted: Thu Dec 04, 2014 2:08 am Post subject: |
|
|
Apprentice
Joined: 03 Feb 2011 Posts: 27
|
regarding your suggestion my application are the banks and it is unlikely thay would agreee to do this changes .....
I had a new idea
why not use the mqs.ini file
meaning for example my qmgrs log and config (701)are in a seperate directory
then the var/mqm
if i stop all the mq process
save a copy of mqs.ini and delete a qmgr x from 701 from it
then create this queue manager x with 7.5 with the same name
i then move the logs and config to sperate direcoty of 7.5
whenever i want to return to 701 qmgr x i return to the old file
its risky i know but assuming this will be controlled and will only happen few times
what do you say ?
has anybody tried to do an upgrade from 701 to 7.5 on the samw server , ( one by one ) ..?/ |
|
Back to top |
|
 |
exerk |
Posted: Thu Dec 04, 2014 2:22 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
sharonv wrote: |
...I had a new idea
why not use the mqs.ini file
meaning for example my qmgrs log and config (701)are in a seperate directory
then the var/mqm
if i stop all the mq process
save a copy of mqs.ini and delete a qmgr x from 701 from it
then create this queue manager x with 7.5 with the same name
i then move the logs and config to sperate direcoty of 7.5
whenever i want to return to 701 qmgr x i return to the old file
its risky i know but assuming this will be controlled and will only happen few times
what do you say ?... |
I say ask IBM because their answer should dictate whether you take that approach - or not - but I think I already know what their answer will be...
sharonv wrote: |
...has anybody tried to do an upgrade from 701 to 7.5 on the samw server , ( one by one ) ..?/ |
Yes, and it wasn't a problem at all, but then any developer I find hard-coding things they shouldn't gets a visit from me with my 'patented Vitor Attitude Adjustment Tool'  _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
sharonv |
Posted: Thu Dec 04, 2014 2:43 am Post subject: |
|
|
Apprentice
Joined: 03 Feb 2011 Posts: 27
|
Hi
I see your point , i dont expect IBM to agree with me on this approch ....
nevertheless i'll open a PMR for it
it will take some effort convincing the banks to do mq configuration changes in production .... |
|
Back to top |
|
 |
exerk |
Posted: Thu Dec 04, 2014 3:17 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
sharonv wrote: |
...it will take some effort convincing the banks to do mq configuration changes in production .... |
Their problem for hard-coding as far as I'm concerned, but as always, they try and shift their issue downstream and generate a 'somebody else's problem' field. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Dec 04, 2014 5:12 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
sharonv wrote: |
it will take some effort convincing the banks to do mq configuration changes in production .... |
Banks do configuration changes in production all the time, like any large organisation. There's a degree of control change (we hope), like any large organisation.
You can and should point out that if they'd followed best practice and not hard coded the configuration they'd really be doing a configuration change not a code change (which typically is harder to organise).
You can finally ask these banks what course of action they prefer: mq configuration changes in production (which might affect 1-n applications if done incorrectly) or a dubious hack on the queue manager which IBM will not support or assist with that will affect all the applications using that queue manager.
It's called "risk management" or "pick your poison", depending on audience.....  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|