ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » version of jar file

Post new topic  Reply to topic
 version of jar file « View previous topic :: View next topic » 
Author Message
George Carey
PostPosted: Mon Mar 05, 2012 3:50 pm    Post subject: version of jar file Reply with quote

Knight

Joined: 29 Jan 2007
Posts: 500
Location: DC

How does one determine the version of a jar file:

com.ibm.mqjms.jar no other context to determine its version

Is there a way to do it?

like 'strings com.ibm.mqjms.jar | grep {something useful}'

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
View user's profile Send private message Visit poster's website AIM Address
mqsiuser
PostPosted: Tue Mar 06, 2012 1:19 am    Post subject: Re: version of jar file Reply with quote

Yatiri

Joined: 15 Apr 2008
Posts: 637
Location: Germany

Open the jar with an (un-)zipper tool. Search and open the MANIFEST file.

Can be done with shell commands.
_________________
Just use REFERENCEs
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Mar 06, 2012 2:31 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

You determine the version of an MQ jar file by installing the client at a specific, known level.

Or by using dspmqver on the client install to tell what version the client is.

If you have a random MQ jar completely unrelated to an MQ client install, then you need to assume that it's a horrendously out dated version, and remove it, and then recofigure the application to use a full MQ client install.
Back to top
View user's profile Send private message
mqsiuser
PostPosted: Wed Mar 07, 2012 12:34 am    Post subject: Reply with quote

Yatiri

Joined: 15 Apr 2008
Posts: 637
Location: Germany

mqjeff is right, you should be aware of what you have deployed and of what you are doing... but... Java is Java and Jar-Files (always) have a Manifest-File: com.ibm.mqjms.jar\META-INF\MANIFEST.MF
_________________
Just use REFERENCEs
Back to top
View user's profile Send private message
SAFraser
PostPosted: Thu Mar 08, 2012 11:10 am    Post subject: Reply with quote

Shaman

Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA

And if you inherit an MQ installation without documentation, what's to be done?

Look at the manifest file.

Even with documentation, I would check the manifest file of an inherited installation.

Mr. Carey is a long-time participant on this forum. I doubt he needs a lecture on documentation.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Thu Mar 08, 2012 11:28 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

SAFraser wrote:
And if you inherit an MQ installation without documentation, what's to be done?


As I said, you replace it with a known version.

When complaints are made that this now requires extensive and expensive testing, agree that yes indeed proper documentation would have been cheaper.

And, yes, I agree, Mr Carey is a long standing member of this community who does not need lectures on proper documentation. That doesn't change my opinion of the correct solution for the problem at hand.

It's all well and good to continue to slap duct tape on a tyre to keep it from leaking air... but at some point, you are absolutely going to *have* to bite the bullet and buy new ones. And the *less* duct tape you have on your tires, the *less* risk you run during that sudden unexpected ice storm.
Back to top
View user's profile Send private message
mqsiuser
PostPosted: Thu Mar 08, 2012 3:25 pm    Post subject: Reply with quote

Yatiri

Joined: 15 Apr 2008
Posts: 637
Location: Germany

It is all about the freedom (to choose what is the right approach for you).

Sometimes I would check all possible checks and then think about the (different ) results this gave me. All possible checks are:

1. Docu, (if there)
2. display version command
3. Manifest file

@mqjeff: There is CSV (Computer Systems Validation). This can like "totally" disallow any change (to the runtime).
_________________
Just use REFERENCEs
Back to top
View user's profile Send private message
ramires
PostPosted: Thu Mar 08, 2012 3:38 pm    Post subject: Reply with quote

Knight

Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa

I found more then one time WAS installations with different com.ibm.mqjms.jar's . The deployed application includes these mq jar's . Of course this is not the correct way to tho things...
_________________
Obrigado / Thanks you
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » version of jar file
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.