| Author |
Message
|
| ivanachukapawn |
 Posted: Sun Mar 07, 2010 10:57 am Post subject: V7 MQ Client Configuration File |
 |
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
| If I do not modify the MQ Client Configuration File on the MQ Client machine will client applications continue to function OK using the customary MQSERVER, MQCHLLIB, MQCHLTAB, variables etc. ? |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sun Mar 07, 2010 11:03 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Modify it to do what?
Have you tried it? What were the results?
_________________
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 |
|
|
| Vitor |
| Posted: Sun Mar 07, 2010 12:08 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ivanachukapawn wrote: |
| If I do not modify the MQ Client Configuration File on the MQ Client machine will client applications continue to function OK using the customary MQSERVER, MQCHLLIB, MQCHLTAB, variables etc. ? |
Are you asking if a v6 client configuration will still work when the target queue manager is upgraded to v7?
If so, why not just say it? Or try it?
Or perhaps just elaborate on what prompts your question?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| exerk |
| Posted: Sun Mar 07, 2010 12:39 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
The 'vanilla' mqclient.ini file comes with a remarked-out TCP stanza so is of no use to a client application, and the file is lower in the hierarchy than the environment variables so will be over-ridden by them.
_________________
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 |
|
|
| ivanachukapawn |
| Posted: Sun Mar 07, 2010 3:34 pm Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
| I do not have the opportunity of trying this config file right now, that's why I posted the question. Since we don't really need to use this file for client connectivity I am assuming that it could be useful anyway especially if we wanted to have lists of MQSERVER variables (which would be tried in sequential order by MQ) or in case where we wanted to implement automated client reconnection. I appreciate your answer as it confirms my guess as to how this works. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Mar 07, 2010 3:47 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I believe you should read the WMQ Clients manual to get the basics of client support. The MQSERVER environment variable works for one shell at a time.
You might want to read the WMQ v7 announcement to see what's new. v7 enables client-reconnection, but this has more to do with the client channel table - not the ini file, and not the MQSERVER environment variable.
_________________
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 |
|
|
| Vitor |
| Posted: Sun Mar 07, 2010 4:11 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ivanachukapawn wrote: |
| I am assuming that it could be useful anyway especially if we wanted to have lists of MQSERVER variables (which would be tried in sequential order by MQ) |
How on Earth could any mechanism produce a list of environment variables? How could any mechanism convince the OS to support such a construct? Environment variables are unique by name on all platforms I'm aware of.
| ivanachukapawn wrote: |
| I appreciate your answer as it confirms my guess as to how this works. |
If you read the client manual, you won't have to guess how the connectivity works. If you have read it, and think that's how the connectivity works, read it again. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Sun Mar 07, 2010 4:50 pm Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
Read the client manual again.
The ServerConnectionParms are equvalent to MQSERVER variables.
| Quote: |
This is equivalent to the MQSERVER environment parameter.
Start of changeSpecify ConnectionName as a comma separated list of names of machines for the stated TransportType. Typically, only one machine name is required. You can provide multiple machine names to configure multiple connections with the same properties. The connections are tried in the order they are specified in the connection list until a connection is successfully established. |
Thats how. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Mar 07, 2010 5:01 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| The ServerConnectionParms are equvalent to MQSERVER variables. |
You have only partially understood the meaning of this statement.
A requirement of an mq client connection is the channel name, protocol, and ipaddress(port) - the variables.
You have choices as to how you provide these variables to the client connection software, namely (pick one of these):
1. MQSERVER= environment variable; OR
2. MQCHLTAB= and MQCHLLIB= environment variables; OR
3. a client channel table
_________________
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 |
|
|
| ivanachukapawn |
| Posted: Sun Mar 07, 2010 5:09 pm Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
This is getting interesting. I agree that the connection attempt needs channel name, transport, and address(port) but I also see this quote.
| Quote: |
ServerConnectionParms specifies the location of the WebSphere MQ server and the communication method to be used. This attribute defines only a simple channel; you cannot use it to define an SSL channel or a channel with channel exits. It is a string of the format ChannelName/TransportType/ConnectionName. |
If this is true, why is not ServerConnectionParms another choice? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Mar 07, 2010 6:39 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The OP was about the MQ Client Configuration File.
When you quote something from a manual (or equivalent source), please cite the reference (document number, name, or URL).
Are you referring to the .NET ServerConnectionParms implementation?
The three choices I offered are those that are native to WMQ. I suppose I could also add the Java classes and JMS equivalents to the list.
_________________
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 |
|
|
| ivanachukapawn |
| Posted: Sun Mar 07, 2010 6:51 pm Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
MQ 7.0.1 Information Center. Search for MQ Client Configuration File. Then follow the link for
| Quote: |
CHANNELS stanza of the client configuration file |
The ServerConnectionParms are an attribute of the CHANNELS stanza of the client configuration file.
You say
| Quote: |
| The three choices I offered are those that are native to WMQ |
but it would appear that this is another choice for providing not only channel/transport/address(port) but a list of channel/transport/address(port) - it appears to be native to WMQ 7.0.1 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Mar 07, 2010 10:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I thought you could use a program to create the qmgr object like QueueManager(String qmgrname, Properties props) to create a qmgr object with the client connection information... This bypasses the MQEnvironment variable and allows multiple client connections from the same program.
It is well documented in the .NET and java Manuals.
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzav.doc/csqzav0567.htm
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
