| Author |
Message
|
| George Carey |
 Posted: Thu May 17, 2012 12:58 pm Post subject: MQ clients |
 |
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
Have a number of app servers in dev and test ... MQ jar files were picked up and put into appropriate app server directories for builds and the like ... some are needing to be upgraded ... what is the best/easiest way to determine the version of a set of Client MQ Jar files.
TIA
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu May 17, 2012 1:49 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
dspmqver? Oh, you can't do that with a half-baked 'install' 
_________________
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 May 17, 2012 2:50 pm Post subject: Re: MQ clients |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| George Carey wrote: |
| what is the best/easiest way to determine the version of a set of Client MQ Jar files. |
Ask the guy who decided it was a good idea to bundle the MQ jar files individually with the app(s) what version he decided to bundle? Look in the documentation they left behind? 
It's because there's no good way of determining this after the event that best practice is to install the client centrally & reference it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mvic |
| Posted: Thu May 17, 2012 4:00 pm Post subject: Re: MQ clients |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| George Carey wrote: |
| what is the best/easiest way to determine the version of a set of Client MQ Jar files. |
You could use the command "strings" and grep output for useful strings like p600, p701 etc.
And then persuade your client / employer to give up this costly practice, and just install the MQ client and set the CLASSPATH.
What could go wrong.. |
|
| Back to top |
|
|
| ramires |
| Posted: Fri May 18, 2012 1:17 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
Each jar file has a MANIFEST.MF file with the info about it, you can expand the jar with a zip utility. Or doing trace.
This is from:
<mq_home>\java\lib\com.ibm.mq.jar\META-INF\MANIFEST.MF
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.1
Created-By: 2.3 (IBM Corporation)
Copyright-Notice: Licensed Materials - Property of IBM 5724-H72,
5655-R36, 5724-L26, 5655-L82 (c) Copyright IBM Corp. 2008 A
ll Rights Reserved. US Government Users Restricted Rights -
Use,duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.
Sealed: false
Specification-Title: WebSphere MQ classes for Java
Specification-Version: 7.1.0.0
Specification-Vendor: IBM Corporation
Implementation-Title: WebSphere MQ classes for Java
Implementation-Version: 7.1.0.0 - k000-L111005.1
Implementation-Vendor: IBM Corporation
Class-Path: com.ibm.mq.headers.jar com.ibm.mq.pcf.jar com.ibm.mq.jmqi.
jar connector.jar com.ibm.mq.commonservices.jar |
|
| Back to top |
|
|
| George Carey |
| Posted: Fri May 18, 2012 11:26 am Post subject: expertise |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
| Quote: |
"Each jar file has a MANIFEST.MF file with the info about it, you can expand the jar with a zip utility. Or doing trace. "
...
"Specification-Version: 7.1.0.0" |
Now there is a guy who knows what he is doing! 
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri May 18, 2012 11:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| It's only reliable for newer levels of MQ. |
|
| Back to top |
|
|
| George Carey |
| Posted: Fri May 18, 2012 11:56 am Post subject: What's newer? |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
So what would be newer levels?
And why would JAR manifest files be unreliable on older levels?
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri May 18, 2012 12:20 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| they didn't add the specific version information to the manifest file until somewhere around 7.0, as far as I recall. |
|
| Back to top |
|
|
| ramires |
| Posted: Fri May 18, 2012 2:31 pm Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
I don't know when this was introduced. The oldest com.ibm.mq.jar I found with info in the manifest.mf is from version 6.0.0.0.
_________________
Obrigado / Thanks you |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat May 19, 2012 4:11 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| ramires wrote: |
| I don't know when this was introduced. The oldest com.ibm.mq.jar I found with info in the manifest.mf is from version 6.0.0.0. |
hrm. Maybe it was at 6.0 they introduced it.
Or maybe I'm remembering wrong entirely.
  |
|
| Back to top |
|
|
| SAFraser |
| Posted: Sat May 19, 2012 5:10 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
I've found information in manifest files that is so old it indicates MA88. It wasn't clear which point release of MA88, but it was clear it was MA88 (I think from the date, I can't remember exactly).
That's been a couple of years ago, when the MQ Team slayed the Improper Client Installation Dragon across our estate. It was bloody. And even after proper installations, the developers still compiled the jars inside the EARS. We thought we'd fixed that by explicit environment variables in WAS, but we sometimes saw behavior that suggested we didn't know WHERE the source jars were being read.
Oh that's a trip down memory lane, offered as empathy for George Carey. All this went away when WAS was upgraded from 5.1 to 7.0 and now the MQ jars shipped with WAS are referenced. Life is much better now. |
|
| Back to top |
|
|
| George Carey |
| Posted: Sat May 19, 2012 8:49 am Post subject: Not WAS |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
And if you're not using WAS ... but an Oracle app server I assume the Jar Manifest files can be relied upon as accurate!?
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat May 19, 2012 4:25 pm Post subject: Re: Not WAS |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| George Carey wrote: |
| And if you're not using WAS ... but an Oracle app server I assume the Jar Manifest files can be relied upon as accurate!? |
Even in Oracle you should reference an additional jar file path (/opt/mqm/java/lib) and not copy the jars... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| SAFraser |
| Posted: Sat May 19, 2012 4:42 pm Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
I believe that Oracle App Server has MQ JMS support (as an adapter?). Which I presume means that MQ jars are placed within the app installation itself, like in WAS?
Bad, bad developers, compiling MQ jars into their code.  |
|
| Back to top |
|
|
|
|
