| Author |
Message
|
| GMcCarthy |
 Posted: Mon Feb 06, 2012 5:38 am Post subject: Migrating from V6.0.2 to V7.1 - in-place? |
 |
|
Centurion
Joined: 06 Nov 2001
Posts: 113
Location: Melville NY
|
This may be the only option I have to upgrade - in-place. Info-center has conflicting info...once it states I have to uninstall queue manager and then it states I can create a second installation. I am on SUSE zLinux 64 bit.
I also have what we believe to be MQ 5.0 JMS clients that are currently working fine when connecting to MQ 6.0.2.4. We attempted to upgrade the client to 7.0.1 and it didn't go so well. My question here is...is MQClient 5.0 compatible with MQServer 7.1?
Thanks !! |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Feb 06, 2012 5:57 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Windows is the only platform that I know of where the installer will remove an existing version for you. Otherwise, it's always a manual step.
You can, indeed, install MQ v7.1 in a second installation on the same machine. But only if the the first installation is MQ v7.0.1. or later.
The most likely reason you weren't able to upgrade your JMS clients is because the JMS runtime is using too old a level of Java. You really need to nuke those JMS clients from orbit and start with something newer like JDK 1.5 or 1.6. I don't expect that any currently supported IBM MQ Java APIs will run in anything older than JDK 1.4 - and even that may be pushing it.
So to be clear, your biggest hurdle in this space is going to be getting a compatible JVM, not whether nor not you can connect via MQ.
It's possible that MQ 7.1 will accept client connections from an MQ v5.0 client level. And in theory, you could even open a PMR if it doesn't, since the server is a supported level... But you really need to save yourself the hassle, and upgrade the clients. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Feb 06, 2012 6:01 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mqjeff wrote: |
| ...You can, indeed, install MQ v7.1 in a second installation on the same machine. But only if the the first installation is MQ v7.0.1. or later... |
With my pedantic head on, I believe it is more specifically 7.0.1.6 or later...
_________________
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 |
|
|
| GMcCarthy |
| Posted: Mon Feb 06, 2012 6:04 am Post subject: |
|
|
Centurion
Joined: 06 Nov 2001
Posts: 113
Location: Melville NY
|
This gives me more reason to push for new hardware 
As far as the client...we brought the old 5.0 jar files over to a brand new system with Java 1.6 
My plan is to try again when we are not under the gun to get that new system in. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 06, 2012 6:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| GMcCarthy wrote: |
| As far as the client...we brought the old 5.0 jar files over to a brand new system with Java 1.6 |
I did not understand that newer JVMs were binary compatible with JVMs earlier than 1.4.
I.e. I'm surprised that the v5.0 jars worked. and twice as surprised if the JVM is 1.6 that the v7 jars didn't... unless, of course, you're not using a fulll product install in both cases... ? |
|
| Back to top |
|
|
| GMcCarthy |
| Posted: Mon Feb 06, 2012 6:20 am Post subject: |
|
|
Centurion
Joined: 06 Nov 2001
Posts: 113
Location: Melville NY
|
| The V5.0 jars were not from a full MQ Client install...they've been (against my recommendations) copied each time this app has been upgraded over the years. Each time they upgrade, I have installed the latest client version and each time something goes wrong and they immediately put the 5.0 back and I have no opportunity to debug. The MQClient V7.0.1 jars were copied from a full MQClient install on those systems this time and, again, were pulled out when something went wrong. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 06, 2012 6:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Tell them that if they won't allow you to debug their installation processes, you won't support their application.
And then don't support their application.
Or at least let them try and open the PMR. |
|
| Back to top |
|
|
|
|
