| Author |
Message
|
| mchan |
 Posted: Thu Sep 29, 2011 6:17 pm Post subject: CCDT |
 |
|
Apprentice
Joined: 09 Sep 2011
Posts: 29
|
Just want to ask the following regarding CCDT, if I want to define Queue Manager Group and use CCDT and to load balancing the connection from client across a number of QMs in different host.
1) The client which use the CCDT does not need to have QM installed on the client machine, right?
2) JMS client can also use CCDT to connect with QM group?
3) If the client machine does not need to have QM installed, then on which host should the CCDT be defined via runmqsc to generate AMQCLCHT.TAB file. On any one of the server host?
Thanks a lot! |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Sep 29, 2011 8:48 pm Post subject: Re: CCDT |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| mchan wrote: |
| Just want to ask the following regarding CCDT, if I want to define Queue Manager Group and use CCDT and to load balancing the connection from client across a number of QMs in different host. |
Client applications connect to qmgrs, not to gmgr groups.
| mchan wrote: |
| 1) The client which use the CCDT does not need to have QM installed on the client machine, right? |
No, the CCDT is used on platforms with the WMQ Client software installed.
| mchan wrote: |
| 2) JMS client can also use CCDT to connect with QM group? |
Yes.
| mchan wrote: |
| 3) If the client machine does not need to have QM installed, then on which host should the CCDT be defined via runmqsc to generate AMQCLCHT.TAB file. On any one of the server host? |
Any qmgr server can be used to create the CCDT.
_________________
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 |
|
|
| fjb_saper |
| Posted: Thu Sep 29, 2011 8:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Any box running WMQ Client and support pack MO72 can be used to define a CCDT. The traditional way however is to do it on a qmgr. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mchan |
| Posted: Fri Sep 30, 2011 12:34 am Post subject: |
|
|
Apprentice
Joined: 09 Sep 2011
Posts: 29
|
| Quote: |
1) The client which use the CCDT does not need to have QM installed on the client machine, right?
No, the CCDT is used on platforms with the WMQ Client software installed. |
Just to double confirm:
That means if my JMS Java client was to use CCDT to connect to a queue manager group, for the machine running the JMS Java client:
- there is no need to install WMQ server
- BUT it is required to have WMQ client installed. Why? |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Sep 30, 2011 2:22 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mchan wrote: |
| - BUT it is required to have WMQ client installed. Why? |
Would a 'vanilla' JMS client know how to use a CCDT? Do you not wonder what might be included within the WMQ-related jars that would know how to use a CCDT?
_________________
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 |
|
|
| mchan |
| Posted: Fri Sep 30, 2011 2:25 am Post subject: |
|
|
Apprentice
Joined: 09 Sep 2011
Posts: 29
|
| Quote: |
- BUT it is required to have WMQ client installed. Why?
Would a 'vanilla' JMS client know how to use a CCDT? Do you not wonder what might be included within the WMQ-related jars that would know how to use a CCDT? |
I just wonder if it is possible to just include related MQ jar files in the classpath of the JMS client, without actually installed WMQ client software.
In this way, we can just bundle required MQ jar files in our package for client distribution.
Thanks![/quote] |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Sep 30, 2011 2:29 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mchan wrote: |
I just wonder if it is possible to just include related MQ jar files in the classpath of the JMS client, without actually installed WMQ client software.
In this way, we can just bundle required MQ jar files in our package for client distribution.
Thanks! |
Which a lot of people have done over the years, but what happens when those jars change? What happens when you go to the vendor for support when you hit a problem? Ask yourself, is it supported? How do you carry out maintenance across different client 'installations'?
_________________
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 |
|
|
|
|
