| Author |
Message
|
| paulgroo |
 Posted: Wed May 28, 2014 11:59 pm Post subject: WebSphere MQ version question |
 |
|
Centurion
Joined: 07 Jul 2005
Posts: 138
Location: Ireland
|
Hey everyone,
I'm trying to engineer a temporary workaround for all our Mid-Tier Java applications to facilitate an MQ upgrade on a Mainframe.
Here are the details:
We have a number of MQ 5.3 clients (yes, I know. VERY old) connecting to a mainframe. On the Mainframe, we also have MQ Server 5.3.
The upgrade of our MQClients to version 7.1 depends heavily on our java applications also being upgraded to a higher level of Java.
The upgrade on the mainframe to 7.1 needs to happen a little more urgently.
I'd like to create an intermediary 'hub' which will allow the 5.3 clients to route messages to/from the mainframe.
Questions:
Has anyone done this before?
Is there a version of MQ that is compatible with both MQ 5.3 and also MQ 7.1?
Does anyone have any other suggestions that might work?
Thanks!! |
|
| Back to top |
|
 |
| zpat |
| Posted: Thu May 29, 2014 12:05 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Have you tried connecting MQ 7.1 clients to MQ 5.3?
They should negotiate a suitable level of the FAP protocol - but Paul Clarke would be the expert on this.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| paulgroo |
| Posted: Thu May 29, 2014 1:08 am Post subject: |
|
|
Centurion
Joined: 07 Jul 2005
Posts: 138
Location: Ireland
|
Hi Pat,
Thanks for the reply. Yes, I think the higher version client is backwards compatible with the lower version of the server, but it's the reverse that I need to get working.
The Java applications will take longer to update/re-engineer and so are stuck using the 5.3 client until that redevelopment work is done.
The mainframe holds a central queue manager(s) for a number of systems. When that upgrade to 7.1 happens, most systems will be fine with the exception of the java based apps.
We've painted ourselves into a corner, to be honest. If I can get this MQ Hub idea working with a version of MQ that will work with both 5.3 and 7.1, I think we can buy ourselves more time. |
|
| Back to top |
|
|
| markt |
| Posted: Thu May 29, 2014 1:41 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
| All levels of client and server interoperate. |
|
| Back to top |
|
|
| rammer |
| Posted: Thu May 29, 2014 2:05 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
Hi Paul,
We have a MQ Hub running 7.5 that acts as a gateway into version 5.3, 6, 7.0 and 7.5 MQ Application Servers and this runs fine. The hub has also been at version 7.0 until we recently upgraded. The only difference is we do not have any clients connecting into our Hub they are all cluster sender / receivers. |
|
| Back to top |
|
|
| paulgroo |
| Posted: Thu May 29, 2014 3:44 am Post subject: |
|
|
Centurion
Joined: 07 Jul 2005
Posts: 138
Location: Ireland
|
Thanks for the replies everyone!
This is good news. I had a read through some of the MO72 release document. My understanding is that I'll need to configure the "Client Channel Definition Table" on the MQ7.1 side to allow the connectivity from the 5.3 clients to work.
Is this correct?
Rammer, is this configuration a 'black art' or is it easy enough? would you have a sample of your CCDT table so I can see what needs to be adjusted?
Do all of your 5.3 clients talk to MQServer 7.1? |
|
| Back to top |
|
|
| zpat |
| Posted: Thu May 29, 2014 4:11 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
It would be a lot quicker to just try it.
You can use older versions of CCDT with newer clients, but not vice-versa.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu May 29, 2014 7:17 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And be aware that there is a minimum required version of Java to connect to the qmgr at version 7.5.x or 7.1.x
If your applications do not meet that requirement you cannot upgrade MQ before you upgrade your java version. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rammer |
| Posted: Thu May 29, 2014 8:17 pm Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
| paulgroo wrote: |
Thanks for the replies everyone!
Rammer, is this configuration a 'black art' or is it easy enough? would you have a sample of your CCDT table so I can see what needs to be adjusted?
Do all of your 5.3 clients talk to MQServer 7.1? |
Hi, we dont have clients connecting into our hub there are all application servers using cluster channels. But I do think we still have some old 5.x clients connecting into our 7.0 gateway. I'll try to take a look tomorrow if I wake up, but ive been up over 24 hours travelling from England to California so may skip tomorrow. Cheers |
|
| Back to top |
|
|
|
|
