| Author |
Message
|
| rajendra |
 Posted: Sun Nov 29, 2009 9:52 pm Post subject: Server connection and clinet connection channels |
 |
|
Novice
Joined: 06 Sep 2009
Posts: 13
|
Hi All,
I hope every one is doing well.
Please clarify this.
What is the difference between client-connection channel and server-connection channel?
and in
which situation we can use client-connection channel?
Thanks in advance.
Regards,
Rajendra. |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Sun Nov 29, 2009 9:57 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Really sorry dude, you have to go through the basics.
look out for these PDFs [manuals]
1. MQ Primer
2. MQ Fundamentals
3. MQ Intercommunication
4. MQ Client
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| rajendra |
| Posted: Sun Nov 29, 2009 10:25 pm Post subject: |
|
|
Novice
Joined: 06 Sep 2009
Posts: 13
|
Thanks for your suggestion.
i have gone through some of the PDFs.
But i am not able to get when to use the client-connection channel?
If you the exact difference you can explain it.
It may help me to understand it properly.
Regards,
rajendra. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Sun Nov 29, 2009 11:09 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
| Quote: |
| i have gone through some of the PDFs. |
read them all
_________________
Regards, Butcher |
|
| Back to top |
|
|
| rajendra |
| Posted: Sun Nov 29, 2009 11:59 pm Post subject: |
|
|
Novice
Joined: 06 Sep 2009
Posts: 13
|
|
| Back to top |
|
|
| exerk |
| Posted: Mon Nov 30, 2009 1:04 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| rajendra wrote: |
| ...But i am not able to get when to use the client-connection channel?... |
Here's a  - when the application is client based!
That's your starter, but there are at least two other ways it can be done without using a client conn, and those you will have to find in the manuals.
_________________
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 |
|
|
| mqjeff |
| Posted: Mon Nov 30, 2009 3:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| exerk wrote: |
| there are at least two other ways it can be done without using a client conn |
Rather say "without having to explicitly define a clntconn".
You ALWAYS use a clntconn. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Nov 30, 2009 3:41 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
_________________
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: Mon Nov 30, 2009 6:33 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Briefly:
The WMQ Client software is most often used on platforms where you don't want/need a queue manager instance (and license, RAM, admin support).
A SVRCONN channel is used by a queue manager to accept inbound connections from client connection applications.
A CLNTCONN channel definition is used to populate an (optional) client channel definition table. The table allows for the possibiloity of the application connecting to more than one SVRCONN connection (same or different queue manager).
Much more to be found in the WMQ Clients manual, and elsewhere.
_________________
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 |
|
|
| gbaddeley |
| Posted: Mon Nov 30, 2009 4:18 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
Briefly:
The WMQ Client software is most often used on platforms where you don't want/need a queue manager instance (and license, RAM, admin support).
A SVRCONN channel is used by a queue manager to accept inbound connections from client connection applications.
A CLNTCONN channel definition is used to populate an (optional) client channel definition table. The table allows for the possibiloity of the application connecting to more than one SVRCONN connection (same or different queue manager).
Much more to be found in the WMQ Clients manual, and elsewhere. |
A CLNTCONN channel definition can also be passed to a MQCONNX call, in a MQCD structure. The MQ Java classes hide the MQCD, but the principle is the same.
The concept of a MQ Client connection is very simple. There is a Message Channel Agent running at each end of a TCP/IP socket session. The MCA at the client side (MQIC library/class in the app) uses a CLNTCONN channel def, the MCA at the server side (queue manager) uses a SVRCONN channel def (of the same name).
_________________
Glenn |
|
| Back to top |
|
|
|
|
