| Author |
Message
|
| ramkumarm83 |
 Posted: Sat Feb 28, 2009 5:29 pm Post subject: MQ Server - MQ Client doubt |
 |
|
Apprentice
Joined: 16 May 2007
Posts: 27
|
Hi All,
I have one mq server and need to send the message from mq client system but I don't want to install mq client on client system.
I know that mq client software is free and mq server software will come with mq client.
So, Can I copy(use) mq server library and jar file from mq server to client system to send the message to server queue manager.
Is this possible??
Can anyone help on this??
Thanks |
|
| Back to top |
|
 |
| zpat |
| Posted: Sat Feb 28, 2009 11:43 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
If you program is Java you can copy the JAR files that comprise the MQ client into the classpath. mq.jar, mqjms.jar - there are some others that will become obvious once you try and run it.
Why not install the MQ client? It's really a bad idea to look for work-arounds that appear to make life easier for you. Do the right thing for your customer. |
|
| Back to top |
|
|
| MQEnthu |
| Posted: Sun Mar 01, 2009 9:47 pm Post subject: |
|
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
| ramkumarm83 wrote: |
| ...but I don't want to install mq client on client system. |
Why not  when you want read/write the messages into queue?? MQ client is meant for this..
_________________
-----------------------------------------------
It is good to remember the past,
but don't let past capture your future |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Wed Mar 04, 2009 9:41 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| Just install the client. We've had issues with support in the past with rogue applications distributing the jar files only with their apps. |
|
| Back to top |
|
|
| Tibor |
| Posted: Thu Mar 05, 2009 12:34 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
Disagree, sorry  . If it is a pure java application, I prefer deploying only the needed jars over installing a full client. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Mar 05, 2009 12:42 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Tibor wrote: |
| Disagree, sorry . If it is a pure java application, I prefer deploying only the needed jars over installing a full client. |
And how do you maintain the installation? How do you keep control of your infrastructure?
_________________
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 |
|
|
| Tibor |
| Posted: Thu Mar 05, 2009 12:59 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
exerk,
Please don't focus on MQ rather an standalone Java application. In this case all of the jars are the parts of it (e.g. the xerces, xalan, or whaterver else) and all of these have to be maintained. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 05, 2009 1:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I think the point here is if your site has really good controls, and really good distribution techniques, then you can distribute the jar files for all the needed components (WMQ, database, etc, etc).
The flip side of this is you move control of software levels away from the administrators and onto the application bundling. So WMQ et al cease to be part of the infrastructure and become instead application pre-reqs.
Really hinges on how the site is organised and how frequently things change (or not).
IMHO it's not a good idea, but then I don't spend a lot of time in pure Java environments with that tight a grasp on software. I find it easier to play it safe, install the full client & avoid contact admin surprises 3 months later. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Mar 05, 2009 1:18 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Hence why I asked the question - I'm not at all up on WMQ and Java applications, and I should be 
_________________
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 |
|
|
| Toronto_MQ |
| Posted: Thu Mar 05, 2009 6:29 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
As I mentioned earlier, on top of the obvious version contol issues you would face as an MQ admin, we have had problems with support (IBM) in these types of situations.
We've opened a PMR for problems in the past and because there was no full MQ client installed and only a few jar files residing in an application directory and not in /opt/mqm/java/lib, IBM would not continue the PMR until we placed a full client installation on the machine and re-tested.
Just something to be aware of, and your experiences may vary. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Mar 05, 2009 7:49 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
MQ client should be part of the environment's system software, not the application software.
I have seen examples of MQ JAR files being way downlevel and no-one knew about them because they were hidden in application directories.
Until one day when they stopped working after a queue manager upgrade - which is something the application people cannot control.
Why "control" the client version if you can't control the queue manager version? - it does not make sense. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 05, 2009 8:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zpat wrote: |
| Until one day when they stopped working after a queue manager upgrade - which is something the application people cannot control. |
Exactly my point. Unless the application people have control of the infrastructure by specifying pre-reqs (or other methods) it's an accident waiting to happen.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Mar 12, 2009 7:22 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I've had no problems getting PMR support for jar file only MQ Clients.
Explain to a Java person why they need to install a full client anything when just the jars work and just the jars is the Java way.
There is nothing in the MQ manuals that says you need to install the full MQ Client for a Java only install.
For years MA88 was the only way to get a Java client to MQ, and that was just the jar files.
Since a Java app will work just fine with just the jar files, you can install the full MQ Client, but there is nothing forcing the Java apps on that server to use the MQ Client files you installed. (other than a trout)
BUT, there is also no documentation that says you CAN have a Java client only use the jar files instead of a full install.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 13, 2009 12:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| PeterPotkay wrote: |
| I've had no problems getting PMR support for jar file only MQ Clients. |
With your aura and sense of authority I can understand that. But...
| PeterPotkay wrote: |
there is also no documentation that says you CAN have a Java client only use the jar files instead of a full install. |
Now I'd be the last person to suggest this would be used to wiggle on a support call and/or play for time. But given the number of times I've heard "apply the latest maintenance and retry" there is suspicion.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Mar 13, 2009 6:31 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Vitor wrote: |
| PeterPotkay wrote: |
| I've had no problems getting PMR support for jar file only MQ Clients. |
With your aura and sense of authority I can understand that. But...
| PeterPotkay wrote: |
there is also no documentation that says you CAN have a Java client only use the jar files instead of a full install. |
Now I'd be the last person to suggest this would be used to wiggle on a support call and/or play for time. But given the number of times I've heard "apply the latest maintenance and retry" there is suspicion. |
If they wiggled to the left with that, I'd wiggle to the right with "Show me where it says the full MQ Client DOES have to be installed for Java only MQ Clients." 
I brought this up at last year's MQ Conferance. The lack of clarity on this topic in the manuals was "acknowledged". 
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
