| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| CLNTCONN vs SVRCONN |
« View previous topic :: View next topic » |
| Author |
Message
|
| bruce2359 |
 Posted: Tue Aug 09, 2011 1:02 pm Post subject: |
 |
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
| mvic wrote: |
| rconn2 wrote: |
| I never use CLNTCONN. I guess in the past I learned that I needed to use SVRCONN and that was that... and I wondered why reading the OP. Sometimes we just ask for the time of day and don't want to make a big deal out of it. |
When you start a client program, you use (whether you realise or not) a CLNTCONN channel definition in your client.
The CLNTCONN channel definition in your client describes to the MQI library code how to reach a SVRCONN somewhere.
You would also need a SVRCONN channel definition on your server, having the same name as the CLNTCONN on your client. This SVRCONN allows the queue manager to create the server side of the client-server connection.
For maximum control over your CLNTCONN channel defintion, you generate your own MQCD in your client program, and pass this via the MQCNO you provide to your MQCONNX call.
Hope this helps. |
When you start a client application, one of two possible methods are used by MQ Client software to contact the queue manager (on behalf of your client application), and both connect through a SVRCONN channel on the qmgr.
Method 1 makes use of environment variable MQSERVER= at the client to name the channel/the protocol/ipaddress(port).
Method 2 makes use of a Client Channel Definition Table (CCDT) that is populated with CLNTCONN definitions, and made available to the MQ Client; AND requires different environment variables at the client. This method allows the MQ Client software to attempt to connect through the SVRCONN channel through zero, one or more CLNTCONN channel definitions in the CCDT.
This is documented in the WMQ Clients documentation.
_________________
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 |
|
 |
| exerk |
| Posted: Tue Aug 09, 2011 1:08 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| bruce2359 wrote: |
When you start a client application, one of two possible methods are used by MQ Client software to contact the queue manager (on behalf of your client application), and both connect through a SVRCONN channel on the qmgr.
Method 1 makes use of environment variable MQSERVER= at the client to name the channel/the protocol/ipaddress(port).
Method 2 makes use of a Client Channel Definition Table (CCDT) that is populated with CLNTCONN definitions, and made available to the MQ Client; AND requires different environment variables at the client. This method allows the MQ Client software to attempt to connect through the SVRCONN channel through zero, one or more CLNTCONN channel definitions in the CCDT. |
Not forgetting Method 3, specifying the channel definition structure on the MQCONNX call 
_________________
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 |
|
|
| bruce2359 |
| Posted: Wed Aug 10, 2011 1:04 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
See? A concise, succinct compare and contrast of SVRCONN and CLNTCONN is not that simple. Much prerequisite knowledge is required to fully grasp the issue.
_________________
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 |
|
|
| mvic |
| Posted: Wed Aug 10, 2011 2:24 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| bruce2359 wrote: |
| See? A concise, succinct compare and contrast of SVRCONN and CLNTCONN is not that simple. Much prerequisite knowledge is required to fully grasp the issue. |
It's not that difficult, IMHO. Also it's not that difficult for a forum full of experienced people to explain it to a newbie in a few sentences. Actually I think we did a pretty good job in this thread, better than usual. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
