| Author |
Message
|
| HenriqueS |
 Posted: Tue Jan 22, 2008 7:53 am Post subject: WMQ client vs. jar files |
 |
|
Master
Joined: 22 Sep 2006
Posts: 235
|
Folks,
What´s the deal of copying into a developer machine solely
-dhbcore.jar.
-com.ibm.mq.jar
-com.ibm.mqjms.jar
And differently, installing a full WMQ client on his/her machine?
What beyond does the WMQ client provides to a developer workstation?
If the client is installed the .jars will have access to native code in .dlls and will run faster?
Any pointers?
_________________
HenriqueS
Certified Websphere MQ 6.0 System Administrator |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Jan 22, 2008 8:02 am Post subject: Re: WMQ client vs. jar files |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| HenriqueS wrote: |
What´s the deal of copying into a developer machine solely
-dhbcore.jar.
-com.ibm.mq.jar
-com.ibm.mqjms.jar
And differently, installing a full WMQ client on his/her machine?
|
Installing the full client is a supported configuration. Copying just the jars is not.
Given the trivial work involved in installing the client there's no good reason just to hump some jar files around. Especially when you come to upgrade.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Jan 22, 2008 5:44 pm Post subject: Re: WMQ client vs. jar files |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Vitor wrote: |
| Installing the full client is a supported configuration. Copying just the jars is not. |
I am of the opinion that this is not clear in any of the manuals one way or the other.
MA88 was a Cat 3 Support Pac that was just the java MQ jars and that was the only way to MQ with Java for years. And it was supported. Then one day those jars are added to the base product. But never was there a statement that said you now need the full MQ Server or the full MQ Client to continue to MQ in client mode with Java. An MQ Client instal was never a prereq to use MA88.
Its very "un-Java" to have to install a whole MQ Client when 100% of the functionality you need is provided in a few jars. And that was the explicitly official way to do it for years.
This is my unofficial opinion, take it for what its worth. Or show me official IBM doc contradicting this. 
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 23, 2008 1:12 am Post subject: Re: WMQ client vs. jar files |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| PeterPotkay wrote: |
| This is my unofficial opinion, take it for what its worth. Or show me official IBM doc contradicting this. |
Ok, good point well taken.
I can't find an explict statement one way or the other, all I can find is the comment that MA88 is rolled into the base product & MA88 should be removed. My (equally unofficial) position is that if you perform a standard install of either client or server it's definiately supported, where if you copy 1-n files into the path there may be a wobble if you raise a PMR.
Now if the client took 2 hours to install, consumed 14Gb of disc & could only be performed sitting at the target machine wearing a safety helmet I'd be with you & would start copying individual files round. It doesn't (but the safety helmet does alarm people nicely!)
My Java phobia may be a factor. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Jan 23, 2008 1:19 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Given that MQ clients are free and can be installed unattended using the correct techniques, I would favour rolling it out.
That way if a non-Java MQ application comes along - it's all set up. Also various support tools that may help diagnose MQ related issues need the MQ client.
If you don't install the client, you have the potential nightmare of tracking the version of the jars files which have been deployed. When you come to try and upgrade your client level - it makes it more complex. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jan 23, 2008 4:26 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I believe as well that if you use just the jar files you will be running into CCSID/Encoding problems that will not appear if you reference the jar files in their installation path... (try browsing a text message on the MF when it is in CCSID 37 or 500....)
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| HenriqueS |
| Posted: Wed Jan 23, 2008 9:54 am Post subject: |
|
|
Master
Joined: 22 Sep 2006
Posts: 235
|
Good discussion. Thanks for the feedback!
_________________
HenriqueS
Certified Websphere MQ 6.0 System Administrator |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 23, 2008 9:54 am Post subject: Re: WMQ client vs. jar files |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Vitor wrote: |
| there may be a wobble if you raise a PMR. |
I've opened a couple PMRs over the years for this type of cinfiguration and it wasn't a problem for those cases.
| zpat wrote: |
| If you don't install the client, you have the potential nightmare of tracking the version of the jars files which have been deployed. When you come to try and upgrade your client level - it makes it more complex. |
You could install the full client, but in the end there isn't anything preventing the individual apps running on that server from bundling the jars they tested with into their EAR and ignoring what you installed.
If it used to be the officially supported way of MQing with Java, if there is nothing now contradicting it, if it works and if its the "Java-way" of doing things, I'm inclined to recomend thefull client gets installed, but not losing sleep if the app wants to just jar.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
