| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Client Channel Definition Table (CCDT) for QMgr Group |
« View previous topic :: View next topic » |
| Author |
Message
|
| HARIVERA |
 Posted: Mon Dec 30, 2013 11:51 am Post subject: Client Channel Definition Table (CCDT) for QMgr Group |
 |
|
Newbie
Joined: 20 Aug 2013
Posts: 5
|
I need a little help in defining the proper CLNTWGHT & AFFINITY values on the CCDT files for multiple projects.
For starters, we are using WAS servers, and in some cases multiple JVM’s per WAS server; the idea is to both provide load-balancing and fail-over capability.
So what I have done is to created multiple CCDT files one each from affected QMgrs each containing all CLNTCONN entries. So each QMgr (i.e. three) is defined with one SVRCONN channel and three CLNTCONN channel, each CCDT file therefore contains all three CLNTCONN definitions.
So that WAS1 using CCDT1 connected primary to QM1, and WAS2 using CCDT2 connects to QM2, and so on. In the event of one QMgr failure, the three WAS server will connect to the surviving QMgrs. Simple, Yes?
The problem is how to correctly define the two parameters (CLNTWGHT & AFFINITY) so that WAS1 will only use QM1 as its primary connection and WAS2 use QM2 as its primary connection. Since by default, (CLNTWGHT=0 & AFFINITY=PERFERRED) will force all three WAS to connect to QM1 first!
So what I have determined, with limited tested, is the following setting:
QM1 (CCDT1):
QM1.CLNT.CHL
QMNAME(QMGROUP)
CLNTWGHT(99) & AFFINITY(NONE)
QM2.CLNT.CHL
QMNAME(QMGROUP)
CLNTWGHT(1) & AFFINITY(NONE)
QM3.CLNT.CHL
QMNAME(QMGROUP)
CLNTWGHT(1) & AFFINITY(NONE)
QM2 (CCDT2):
QM1.CLNT.CHL
QMNAME(QMGROUP)
CLNTWGHT(1) & AFFINITY(NONE)
QM2.CLNT.CHL
QMNAME(QMGROUP)
CLNTWGHT(99) & AFFINITY(PERFERRED)
QM3.CLNT.CHL
QMNAME(QMGROUP)
CLNTWGHT(1) & AFFINITY(NONE)
QM3 (CCDT3):
QM1.CLNT.CHL
QMNAME(QMGROUP)
CLNTWGHT(1) & AFFINITY(NONE)
QM2.CLNT.CHL
QMNAME(QMGROUP)
CLNTWGHT(1) & AFFINITY(NONE)
QM3.CLNT.CHL
QMNAME(QMGROUP)
CLNTWGHT(99) & AFFINITY(PERFERRED)
Again, the premise being that WAS will control via Group Manager (*QMGROUP) QCF setup and pointing to the associated CCDT file (i.e. WAS1 using CCDT1) will always connect to the primary QMgr (i.e. QM1).
I hope that helps…. |
|
| Back to top |
|
 |
| brianb |
| Posted: Mon Dec 30, 2013 2:43 pm Post subject: CCDT |
|
|
Voyager
Joined: 12 May 2010
Posts: 85
|
|
| 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
|
|
|
|
