| Author |
Message
|
| mqsiuser |
 Posted: Fri Aug 03, 2012 4:26 am Post subject: How do I get the mq client jars for ... |
 |
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
... MQ 7.0.1.7 for Solaris?
I have downloaded the MQ Client Version 7.0.1.7 for Solaris (Sparc), but the files I am searching for are not included.
com.ibm.mq.jar
com.ibm.mq.jmqi.jar
com.ibm.mqjms.jar
dhbcore.jar
Note that I cannot install MQ (Client) on Solaris (and then retrieve the files) and that I need the files (and cannot install the (full) MQ client  (or MQ Server))! |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Aug 03, 2012 4:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You can't unpack the files in the installer without installing it.
So, yes, you *need* to INSTALL the client and then copy the jar files out.
But you could install it into */tmp* and then copy the jar files and then *uninstall*.
But then every time you want to update the jar files you need to do this again... so it's much *more managable* to install the full client.
EDIT: Also, remember that a jar file is a jar file is a jar file, and the code within it is compiled against the JVM, not against the OS... 
Last edited by mqjeff on Fri Aug 03, 2012 4:32 am; edited 1 time in total |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Aug 03, 2012 4:32 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Get the full client installed by whoever can do it.
Always a bad idea to copy JAR files around. They will become invisible and get out of date and no-one will know until the day it causes a major problem.
Also, why not use WMQ 7.0.1.8?
JAR files are not system specific - so any platform could be used to supply them (but I repeat this is very much the wrong way to do this). |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Aug 03, 2012 4:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| zpat wrote: |
Get the full client installed by whoever can do it.
Always a bad idea to copy JAR files around. They will become invisible and get out of date and no-one will know until the day it causes a major problem.
Also, why not use WMQ 7.0.1.8?
JAR files are not system specific - so any platform could be used to supply them (but I repeat this is very much the wrong way to do this). |
 |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Fri Aug 03, 2012 4:45 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| mqjeff wrote: |
| Also, remember that a jar file is a jar file is a jar file, and the code within it is compiled against the JVM, not against the OS... |
| zpat wrote: |
| JAR files are not system specific - so any platform could be used to supply them. |
I have the files for AIX and Windows here and they vary in size... it is a nice theory, that Java is OS-independent... but what about Java Native Interface or whatever else might happen... also why are the files (for AIX and Windows) different in size ?!
Is this 100% that I can just take the 4 files from any platform and use them on any other ?
How could it be that they are in included in the MQ Client bundle (the link in my first post), but that I can't get them out of there (but only when installing)? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Aug 03, 2012 4:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| mqsiuser wrote: |
| Is this 100% that I can just take the 4 files from any platform and use them on any other ? |
The only time the MQ client uses native APIS that would require platform specific binaries is when you're doing a bindings connection.
That said, it's 90% that you can move jars.
| mqsiuser wrote: |
| How could it be that they are in included in the MQ Client bundle (the link in my first post), but that I can't get them out of there (but only when installing)? |
because the client package is an installer, not a software bundle. You certainly *can* get them out of the installer package, but not *easily*. The *easy* way is to *run the installer*. The other way is to reverse engineer the installer packaging of it's binary source files. This is *hard* and *error prone*.
But again, this is not a simple technology issue.
It's a change management issue. USE THE INSTALLER, INSTALL THE FULL CLIENT. |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Fri Aug 03, 2012 4:59 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| mqjeff wrote: |
The only time the MQ client uses native APIS that would require platform specific binaries is when you're doing a bindings connection.
That said, it's 90% that you can move jars. |
With bindings you mean a local binding (not through a channel) and you seem to do that in 10% of all cases
And it won't work for the Solaris machine if I'd give them the AIX-jars !?
| mqjeff wrote: |
| USE THE INSTALLER, INSTALL THE FULL CLIENT. |
It just is the way it is. I do not decide that.
What are the steps to extract the files from mqc7_7.0.1.7_solaris-sparc.tar.Z (268 MB) ? |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Aug 03, 2012 5:03 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mqsiuser wrote: |
| What are the steps to extract the files from mqc7_7.0.1.7_solaris-sparc.tar.Z (268 MB) ? |
| mqjeff wrote: |
You can't unpack the files in the installer without installing it.
So, yes, you *need* to INSTALL the client and then copy the jar files out.
But you could install it into */tmp* and then copy the jar files and then *uninstall*.
But then every time you want to update the jar files you need to do this again... so it's much *more managable* to install the full client. |
_________________
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 |
|
|
| mqsiuser |
| Posted: Fri Aug 03, 2012 5:29 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
ok, we are using the client jars with WAS (WebSphere Application Server) with "CLIENT" binding and JMS.
So let's say the AIX jars will be fine for the Solaris machine !?
And: I am really sorry that we use the jar files (instead of installing the mq client)
Last edited by mqsiuser on Fri Aug 03, 2012 5:51 am; edited 2 times in total |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Aug 03, 2012 5:33 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqsiuser wrote: |
| And it won't work for the Solaris machine if I'd give them the AIX-jars !? |
The binding will not work on Solaris with the AIX code. A Solaris client probably will but it's not guaranteed.
| mqsiuser wrote: |
| It just is the way it is. I do not decide that. |
No, but you're the one who should point out to whoever does decide it that this is not a good idea and underline to them the risks of doing this. Especially if the person making the decision is not especially technical and/or does not fully understand the architecture. Typically decision makers rely on people like us to point out when they're heading for a cliff. Good decision makers change direction when so warned.
| mqsiuser wrote: |
| What are the steps to extract the files from mqc7_7.0.1.7_solaris-sparc.tar.Z (268 MB) ? |
As indicated above, you reverse engineer the steps taken by the installer included in that tar file when it builds the jar files as part of the install, then perform those steps.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Fri Aug 03, 2012 5:52 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| Quote: |
ok, we are using the client jars with WAS (WebSphere Application Server) with "CLIENT" binding and JMS.
So let's say the AIX jars will be fine for the Solaris machine !? |
There will be a connection channel (Connection Factory) in the WAS console and the MQ Server will be/reside remotely (it will be on another machine !)...
"CLIENT" just means MQ Client (I think) and JMS... I hightly guess it will work.
"(local) binding" would require MQ and the application (e.g. WAS) to be on the same machine... and this is what would not work.
I will give them the AIX jars. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Aug 03, 2012 5:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
What I meant is that if you are making a BiNDINGS connection to the queue manager (which uses shared memory to talk to the qmgr on the same machine), then the AIX jars will not work on solaris.
If you are using a CLIENT connection, then it is 90% sure that the AIX jars will work on Solaris. It should be 100%, but there may be cases with JMS and some internal things where it's not quite. Or at least, I do not personally feel qualified to guarantee that it will work. It *should* work, but don't take my word for it. |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Fri Aug 03, 2012 10:06 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
What limitations in your company are preventing you from doing a proper install and having a fully supported installation?
Moving the jar files around is just a bad idea for many reasons. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Aug 03, 2012 10:44 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Toronto_MQ wrote: |
What limitations in your company are preventing you from doing a proper install and having a fully supported installation?
Moving the jar files around is just a bad idea for many reasons. |
And by 'bad idea' we mean not a best-practice.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Fri Aug 03, 2012 11:20 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
Obviously 'just the jar files' are much much smaller ... that is an advantage.
I can imagine that someone (e.g. a Java guy) might find 4 jar files much less scary than an installer, which comes with 268 MB (It took me more than 10 Minutes to download it).
These are a lot of objections which I do not (fully) understand:
| zpat wrote: |
| Always a bad idea to copy JAR files around. They will become invisible and get out of date and no-one will know until the day it causes a major problem. |
There are known places for jar files. And you can always do a "find . -name myJarFile.jar". And look into the jar files (manifest).
| Toronto_MQ wrote: |
| Moving the jar files around is just a bad idea for many reasons. |
Which?
| bruce2359 wrote: |
| And by 'bad idea' we mean not a best-practice. |
|
|
| Back to top |
|
|
|
|
