| Author |
Message
|
| rickwatsonb |
 Posted: Wed Aug 03, 2011 1:08 pm Post subject: MQ client on Websphere application server |
 |
|
Voyager
Joined: 15 Aug 2006
Posts: 87
Location: USA: Mid-West
|
Hi,
My question is: Is it an acceptable configuration (or wise) to permanently use a MQ client installation on a WAS server to connect a JMS application to a MQ server?
We are currently out of support with WAS 6.0.2.x which runs a JMS application to connect to queues on a MQ server via TCP/IP client mode utilizing the embedded MQ slim client (5.3) in WAS. Since WAS 6.0.2.x is out of support, the embedded MQ 5.3 slim client is also out of support, and thus the WAS MQ connection to the MQ server is out of support.
The WAS also runs a JAVA application and we cannot upgrade to WAS 7 or 8, and get in support, until next year when the JAVA is upgraded; this all due to the newer WAS JAVA system requirements.
In order to get in support with MQ, it is recommended that we install a supported MQ client. We plan to install a MQ V7.x client on the WAS 6.0.2.x server to connect to a MQ 7.x server.
My question pertains to the idea that we are considering keeping the MQ client installation on WAS after we upgrade to 7/8. The thinking behind this is that firstly, we can always keep a MQ upgrade independent of any delays in a WAS upgrade, and secondly we can keep a MQ client which will also be used on a separate batch server in sync with the version of MQ being used on WAS.
Any thought from experienced WAS and MQ admins would be appreciated.
Thanks for your time and help. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Aug 03, 2011 1:23 pm Post subject: Re: MQ client on Websphere application server |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| rickwatsonb wrote: |
Hi,
My question is: Is it an acceptable configuration (or wise) to permanently use a MQ client installation on a WAS server to connect a JMS application to a MQ server?
We are currently out of support with WAS 6.0.2.x which runs a JMS application to connect to queues on a MQ server via TCP/IP client mode utilizing the embedded MQ slim client (5.3) in WAS. Since WAS 6.0.2.x is out of support, the embedded MQ 5.3 slim client is also out of support, and thus the WAS MQ connection to the MQ server is out of support.
The WAS also runs a JAVA application and we cannot upgrade to WAS 7 or 8, and get in support, until next year when the JAVA is upgraded; this all due to the newer WAS JAVA system requirements.
In order to get in support with MQ, it is recommended that we install a supported MQ client. We plan to install a MQ V7.x client on the WAS 6.0.2.x server to connect to a MQ 7.x server.
My question pertains to the idea that we are considering keeping the MQ client installation on WAS after we upgrade to 7/8. The thinking behind this is that firstly, we can always keep a MQ upgrade independent of any delays in a WAS upgrade, and secondly we can keep a MQ client which will also be used on a separate batch server in sync with the version of MQ being used on WAS.
Any thought from experienced WAS and MQ admins would be appreciated.
Thanks for your time and help. |
Don't keep out of your sight that an upgraded MQ client will require a higher level of Java too. I believe the lowest level of java for MQ 7 is java 1.4 whereas I would not be surprised if your WAS was still running on java 1.3 ... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sigormley |
| Posted: Tue Sep 13, 2011 7:48 am Post subject: |
|
|
Newbie
Joined: 24 Feb 2004
Posts: 6
|
Looks like WAS 6.0.2 comes with Java 1.4, so MQ V7 should be ok (it's even listed as a supported application server in the MQ V7 SoE...)
As for using your installed V7 client when upgrading to WAS 7/8, that's a no-go, as you have to use the WMQ JMS client shipped with the version of WAS 7/8 you are using - there's no MQ_INSTALL_ROOT variable to change that alters which WMQ client is used, although the good news is that they already come with a WMQ V7 client... |
|
| Back to top |
|
|
| rickwatsonb |
| Posted: Fri Jun 29, 2012 11:14 am Post subject: |
|
|
Voyager
Joined: 15 Aug 2006
Posts: 87
Location: USA: Mid-West
|
Thank you for your previous help.
It is now 9 months later and we have installed the MQ 7.0.1.7 client on the WAS 6.0.2.43 application server. Contrary to what I proposed, the WAS admin group did not set the MQ_INSTALL_ROOT variable but instead put the path to the MQ Client API in the CLASSPATH.
Question 1:
Will WAS 6.0.2.43 actually use the MQ Client API from the CLASSPATH, or is it actually using the WAS embedded 5.3 MQ Client? (Application servers are Solaris and Linux.)
Question 2:
The WAS admins plan to do the same configuration when we upgrade to WAS 8.5 by keeping the MQ Client and putting the path to the MQ Client API in the CLASSPATH. As sigormley stated – ‘there’s no MQ_INSTALL_ROOT variable’ with WAS 7/8, so that is not up for debate. What will WAS actually use; will it use the WAS embedded MQ JCA adapter or the MQ Client API from the CLASSPATH? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jun 30, 2012 6:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| rickwatsonb wrote: |
Thank you for your previous help.
It is now 9 months later and we have installed the MQ 7.0.1.7 client on the WAS 6.0.2.43 application server. Contrary to what I proposed, the WAS admin group did not set the MQ_INSTALL_ROOT variable but instead put the path to the MQ Client API in the CLASSPATH.
Question 1:
Will WAS 6.0.2.43 actually use the MQ Client API from the CLASSPATH, or is it actually using the WAS embedded 5.3 MQ Client? (Application servers are Solaris and Linux.)
Question 2:
The WAS admins plan to do the same configuration when we upgrade to WAS 8.5 by keeping the MQ Client and putting the path to the MQ Client API in the CLASSPATH. As sigormley stated – ‘there’s no MQ_INSTALL_ROOT variable’ with WAS 7/8, so that is not up for debate. What will WAS actually use; will it use the WAS embedded MQ JCA adapter or the MQ Client API from the CLASSPATH? |
Have you considered creating the MQ_INSTALL_ROOT variable manually?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rickwatsonb |
| Posted: Tue Jul 03, 2012 7:53 am Post subject: |
|
|
Voyager
Joined: 15 Aug 2006
Posts: 87
Location: USA: Mid-West
|
Thank you for your response fjb_saper, and sorry for the delay, but the WAS admins do NOT intend to manually set MQ_INSTALL_ROOT because they believe the MQ libraries are being utilized through the CLASSPATH.
My two questions still stand, if they are not clear please let me know.
Thanks |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jul 03, 2012 8:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| The problem with your questions is, that it depends on which classloader loads the CLASSPATH and which one might possibly load the embedded MQ client, and then the relationship of those classloaders to each other and to your java code. |
|
| Back to top |
|
|
| sigormley |
| Posted: Mon Jul 09, 2012 2:36 am Post subject: |
|
|
Newbie
Joined: 24 Feb 2004
Posts: 6
|
As mqjeff says, the MQ client used would depend on the classloader used.
However, I think you're missing the point really - you shouldn't be loading the MQ client using the CLASSPATH mechanism in WAS, as it could get very messy, and instead be sticking to the provided mechanisms - MQ_INSTALL_ROOT in WAS 6, and the MQ Resource Adapter in WAS 7+ |
|
| Back to top |
|
|
|
|
