| Author |
Message
|
| zpat |
 Posted: Thu Mar 01, 2012 6:35 am Post subject: mqclient.ini and Websphere Apps Server |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Does the mqclient.ini file exist for the builtin MQ client that comes in WAS 7.0.0.19 and where is it to be found, or where should it be placed if needed?
If someone copies files like mqjms.jar and mq.jar and connects to MQ on a box without MQ client installed, do these jar files still look for mqclient.ini? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Mar 01, 2012 10:55 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
IIRC this is specified in the client manual. However you might have to read the .NET manual for that. I believe that the .NET client is the one getting the most use out of that file. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Mar 01, 2012 11:28 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I am interested only in the specific case of the embedded MQ client of WAS.
Only Java/JMS is relevant in my case and the platform is RHEL. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Mar 02, 2012 10:46 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| zpat wrote: |
I am interested only in the specific case of the embedded MQ client of WAS.
Only Java/JMS is relevant in my case and the platform is RHEL. |
There is some litterature about some defaults for the installation. Can't remember though if it uses a .ini or a .properties file...
Have you searched the infocenter for it?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| vennela |
| Posted: Sat Mar 03, 2012 4:32 pm Post subject: Re: mqclient.ini and Websphere Apps Server |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| zpat wrote: |
Does the mqclient.ini file exist for the builtin MQ client that comes in WAS 7.0.0.19 and where is it to be found, or where should it be placed if needed?
|
I don't think it exists.
The embedded client I think was more like MQ for WAS v5. Since WAS v6, there is built in messaging called SIBus or default messaging. WAS can still connect to MQ and all it needs is MQ jar files. I don't think it needs the .ini file.
| zpat wrote: |
If someone copies files like mqjms.jar and mq.jar and connects to MQ on a box without MQ client installed, do these jar files still look for mqclient.ini? |
I don't think these jar files look for it.
One other thing though
There is a WebSphere variable called MQ_INSTALL_ROOT environment variable which can point to the jar files location. Those jars can be anywhere but we just need to give the correct location for the variable. This is needed especially if configuring JMS JNDI resources within WebSphere that point to MQ resources. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Mar 03, 2012 5:30 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I have opinions on this as well.
They are mostly the opposite of vennela's.
I will attempt to do some research and find out if I have more than just opinions. |
|
| Back to top |
|
|
| zpat |
| Posted: Sun Mar 04, 2012 12:28 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Thanks, the reason I ask is that I want to use some of the options that are typically set in mqclient.ini, such as keepalive and socket_timeout. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Mar 04, 2012 2:42 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Mar 04, 2012 7:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fjb_saper wrote: |
| zpat wrote: |
| Thanks, the reason I ask is that I want to use some of the options that are typically set in mqclient.ini, such as keepalive and socket_timeout. |
Shame on you.... a simple search on mqclient.ini in the infocenter gives you all the info you're asking for:
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzaw.doc/jm41100_.htm
Look for a properties file called jms.config and specify it's location when starting the client via java -D switch... |
Which in this case is NOT a standalone client, but the full blown WebSphere Application Server.
And it's not a standalone client install, either, it's the client libraries that come with the full blown WebSphere Application Server.
This doesn't mean that setting the appropriate part of the jms config as per the above links, and potentially setting a variable on server config to include the relevant -D won't work.
But it means that it's not the most obvious choice of direction to take. |
|
| Back to top |
|
|
| zpat |
| Posted: Sun Mar 04, 2012 8:04 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Yes, it's not quite the answer I was looking for. Unless there is a default location URL for this config file? I don't want to change any java invocation parameters. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Mar 04, 2012 10:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| zpat wrote: |
| Yes, it's not quite the answer I was looking for. Unless there is a default location URL for this config file? I don't want to change any java invocation parameters. |
Didn't specifically see a default location mentioned in 7.1 but in 7.0.1 it is mentioned as being the jms.config file under <mqinstall>java/bin ?
Looks like 7.1 has the same default http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.doc/jm41100_.htm
And whether stand alone or with MQ Server I would still check it out the same and test.
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
