| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| channel............. |
« View previous topic :: View next topic » |
| Author |
Message
|
| bkiran2020 |
 Posted: Tue Mar 27, 2012 9:08 pm Post subject: channel............. |
 |
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
| the server connection channel is bi direction why we should have the client server channel connection is by bi direction ........... |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Mar 27, 2012 10:02 pm Post subject: Re: channel............. |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| bkiran2020 wrote: |
| the server connection channel is bi direction why we should have the client server channel connection is by bi direction ........... |
Are you asking what the difference is between a SVRCONN and CLNTCONN channel?
If yes, read the WMQ Intercommunications manual, or go to the InfoCenter, and search for these channel types.
If this is not what you are asking, please try again to explain exactly what you want to know.
_________________
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 |
|
|
| bkiran2020 |
| Posted: Tue Mar 27, 2012 10:10 pm Post subject: |
|
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
My question is that SVR Connection channel is bidirectional which indicates we can communicate from server and client to server.so ,why do we need a client connection channel?
I have gone through the documents but they just say, how we define the channels and how they communicate.
 |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Mar 28, 2012 12:02 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| bkiran2020 wrote: |
My question is that SVR Connection channel is bidirectional which indicates we can communicate from server and client to server.so ,why do we need a client connection channel?
I have gone through the documents but they just say, how we define the channels and how they communicate.
|
ALL channels have two ends, ALL channels! Try defining a CLNTCONN to a non-existent SVRCONN and see what happens, then come back and restate your question.
_________________
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 Mar 28, 2012 7:39 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
This is well-documented.
There are two bindings choices for WMQ applications:
1) server-bindings - where the application runs in the same o/s instance where the qmgr runs; AND the MQI calls are shipped cross-memory to the qmgr for execution.
2) client-bindings - where the application is not (necessarily) running in the same o/s as the qmgr; AND the MQI calls are shipped cross-network to the qmgr for execution.
SVRCONN channel definitions are used by qmgrs to accept inbound connections from 2) above - client-bindings applications.
For client-bindings apps, environment variables need to be set that identify the qmgr and SVRCONN channel to which to send the MQI calls. Or, in the alternative, to identify a Client Channel Definition Table (CCDT) that offers the app one or more qmgr alternatives to which to connect.
CLNTCONN channel definitions are used to populate a Client Channel Definition Table (CCDT) that offers the definition of multiple qmgrs and SVRCONN channels for the app to connect.
_________________
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.
Last edited by bruce2359 on Wed Mar 28, 2012 8:45 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Mar 28, 2012 7:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Every instance of a SVRCONN channel is always associated with a CLNTCONN definition.
Not all CLNTCONNs are manually defined, however. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Mar 28, 2012 8:46 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| mqjeff wrote: |
| Every instance of a SVRCONN channel is always associated with a CLNTCONN definition. |
With MQSERVER= environment variable, no CCDT and CLNTCONN channel definition is needed.
_________________
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 |
|
|
| mqjeff |
| Posted: Wed Mar 28, 2012 8:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| bruce2359 wrote: |
| mqjeff wrote: |
| Every instance of a SVRCONN channel is always associated with a CLNTCONN definition. |
With MQSERVER= environment variable, no CCDT and CLNTCONN channel definition is needed. |
No, that's not correct.
With MQSERVER=environment variable, a default CLNTCONN channel definition is USED.
Every instance of a SVRCONN channel always has an associated instance of a CLNTCONN channel. Please note, Bruce, that I am being precise when I use the word 'instance'.
Not all CLNTCONNS are manually defined, however. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Mar 28, 2012 10:02 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Got it, thanks Jeff.
_________________
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 |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
