Author |
Message
|
elblagga |
Posted: Fri Jul 30, 2010 5:43 am Post subject: Preferred Channels in Overlapping Clusters |
|
|
Newbie
Joined: 30 Jul 2010 Posts: 5
|
We are implementing SSL on a large WMQ Clustered environment on various platform's in V6. We are using overlapping clusters in this implementation. We are implementing in 2 phases, first create the cluster then enable SSL. I know our approach may not be best practice regarding implementation but it is enterprise driven. A requirement is for messages to go across the newly defined clssdr and/or clsrcvr channels. We need to ensure that those channels are utilized instead of the other cluster channels. We are using qmgr aliasing via remote queue defintions. In our testing, if the channels for the older cluster are down/stopped messages go across the preferred channel but when all of the channels are available (active/inactive) the messages are not going across the preferred cluster channels. I have set the new clssdr channels to a higher priority but it's not make these channels the preferred channels. Any thoughts on how we can achieve this requirement? Thanks |
|
Back to top |
|
 |
mvic |
Posted: Sat Jul 31, 2010 1:52 pm Post subject: Re: Preferred Channels in Overlapping Clusters |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
elblagga wrote: |
Any thoughts on how we can achieve this requirement? |
Perhaps remove the non-SSL channels, by setting their CLUSTER attribute to a blank string? This will leave only your SSL channels in place, if I understood your description correctly. |
|
Back to top |
|
 |
elblagga |
Posted: Mon Aug 02, 2010 4:27 am Post subject: |
|
|
Newbie
Joined: 30 Jul 2010 Posts: 5
|
Yes, we do have them set to blank. With the overlapping clusters, we utilize namelists.
Thanks, |
|
Back to top |
|
 |
mvic |
Posted: Mon Aug 02, 2010 4:49 am Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
elblagga wrote: |
Yes, we do have them set to blank. With the overlapping clusters, we utilize namelists.
Thanks, |
Please then clarify what you are asking us. |
|
Back to top |
|
 |
elblagga |
Posted: Mon Aug 02, 2010 10:06 am Post subject: |
|
|
Newbie
Joined: 30 Jul 2010 Posts: 5
|
How do we get messages to go across Higher Network Prioritized channels in an Overlapping SSL Enabled cluster? As part of our testing approach, we have chosen to create all the needed objects before enabling ssl. At this point, when we send messages in the overlapping clusters, the messages are going across lower prioritized channels not the higher prioritized channels which are the preferred channels. I hope that clarifies what I'm asking for assistance in. Outside of the previously suggested configuration is there any addtional configuration changes needed to meet this particular requirement?
Thanks, |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Aug 02, 2010 1:13 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
elblagga wrote: |
How do we get messages to go across Higher Network Prioritized channels in an Overlapping SSL Enabled cluster? As part of our testing approach, we have chosen to create all the needed objects before enabling ssl. At this point, when we send messages in the overlapping clusters, the messages are going across lower prioritized channels not the higher prioritized channels which are the preferred channels. I hope that clarifies what I'm asking for assistance in. Outside of the previously suggested configuration is there any addtional configuration changes needed to meet this particular requirement?
Thanks, |
Did you create a cluster/receiver for each cluster or are you using namelist?
You need to treat the overlapping clusters as separate clusters with separate channels. This way you can force the cluster on a message.
(define aliases for the base queue. Alias A with high priority in cluster A and alias B with low priority in cluster B.)
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Aug 02, 2010 2:52 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
In order to make this work, you really really need to understand the cluster workload balancing algorithm and really really understand a) what it uses to measure workload, b) how it decides which channels are available for balancing, c) how the interesection of CLWLWGHT, CLWLRANK, CLWLPRTY and NETPRTY gets calculated. d) how CLWLRANK and CLWLPRTY of the queues that are shared in the cluster get mingled in with all of this.
The best thing to do is create a small cluster with three qmgrs, two of which have a single queue that is shared in a single cluster with a single CLUSRCVR to each PR. Then run a bunch of load and measure how the workload gets distributed.
Then add a second CLUSRCVR to each PR and see how that changes the distribution.
Then adjust the parameters of the second CLUSRCVR and see how that changes the distribution.
Then, and only then, when you have a working knowledge, try to scale this up to multiple overlapped clusters with and without namelists. |
|
Back to top |
|
 |
sumit |
Posted: Tue Aug 03, 2010 2:30 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006 Posts: 398
|
Another way of doing this is by using CLWLEXIT. I must inform you that writing a good exit is a highly complex task yet it will do what you are looking for.
I'd still recommend to follow mqjeff's advise and tweak your cluster configuration. Plan for the exit as your last resort.
Edit: this may be helpful. _________________ Regards
Sumit |
|
Back to top |
|
 |
elblagga |
Posted: Tue Aug 03, 2010 10:19 am Post subject: |
|
|
Newbie
Joined: 30 Jul 2010 Posts: 5
|
fjb_saper wrote: |
elblagga wrote: |
How do we get messages to go across Higher Network Prioritized channels in an Overlapping SSL Enabled cluster? As part of our testing approach, we have chosen to create all the needed objects before enabling ssl. At this point, when we send messages in the overlapping clusters, the messages are going across lower prioritized channels not the higher prioritized channels which are the preferred channels. I hope that clarifies what I'm asking for assistance in. Outside of the previously suggested configuration is there any addtional configuration changes needed to meet this particular requirement?
Thanks, |
Did you create a cluster/receiver for each cluster or are you using namelist?
You need to treat the overlapping clusters as separate clusters with separate channels. This way you can force the cluster on a message.
(define aliases for the base queue. Alias A with high priority in cluster A and alias B with low priority in cluster B.)
Have fun  |
We have created clusrcvr & clussdr for each cluster and we are using namelists. Hence, my inquiry. |
|
Back to top |
|
 |
elblagga |
Posted: Tue Aug 03, 2010 10:22 am Post subject: |
|
|
Newbie
Joined: 30 Jul 2010 Posts: 5
|
mqjeff wrote: |
In order to make this work, you really really need to understand the cluster workload balancing algorithm and really really understand a) what it uses to measure workload, b) how it decides which channels are available for balancing, c) how the interesection of CLWLWGHT, CLWLRANK, CLWLPRTY and NETPRTY gets calculated. d) how CLWLRANK and CLWLPRTY of the queues that are shared in the cluster get mingled in with all of this.
The best thing to do is create a small cluster with three qmgrs, two of which have a single queue that is shared in a single cluster with a single CLUSRCVR to each PR. Then run a bunch of load and measure how the workload gets distributed.
Then add a second CLUSRCVR to each PR and see how that changes the distribution.
Then adjust the parameters of the second CLUSRCVR and see how that changes the distribution.
Then, and only then, when you have a working knowledge, try to scale this up to multiple overlapped clusters with and without namelists. |
Ok, thanks for the feedback. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Sat Aug 07, 2010 11:25 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
elblagga wrote: |
fjb_saper wrote: |
elblagga wrote: |
How do we get messages to go across Higher Network Prioritized channels in an Overlapping SSL Enabled cluster? As part of our testing approach, we have chosen to create all the needed objects before enabling ssl. At this point, when we send messages in the overlapping clusters, the messages are going across lower prioritized channels not the higher prioritized channels which are the preferred channels. I hope that clarifies what I'm asking for assistance in. Outside of the previously suggested configuration is there any addtional configuration changes needed to meet this particular requirement?
Thanks, |
Did you create a cluster/receiver for each cluster or are you using namelist?
You need to treat the overlapping clusters as separate clusters with separate channels. This way you can force the cluster on a message.
(define aliases for the base queue. Alias A with high priority in cluster A and alias B with low priority in cluster B.)
Have fun  |
We have created clusrcvr & clussdr for each cluster and we are using namelists. Hence, my inquiry. |
If you have distinct channels for each cluster, what exactly are you using the namelists for? Nothing channel related I hope. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
PeterPotkay |
Posted: Sat Aug 07, 2010 11:27 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
In addition to what jeff said, you are also going to have to get crafty with QM Aliases and ReplyTo Queue Aliases if you want complete control of which cluster channels reply messages go over if they are going back to a specific Reply To Queue on a specific clustered QM. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
fjb_saper |
Posted: Sat Aug 07, 2010 2:24 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
PeterPotkay wrote: |
If you have distinct channels for each cluster, what exactly are you using the namelists for? Nothing channel related I hope. |
Nothing queue related either I hope! How is the qmgr to know which cluster to use if the queue is defined in both? This is why an alias defined by cluster for each base queue allows you to control which cluster you want to use for routing the message to the destination. (non clustered base queue-> alias a in cluster A and alias b in cluster B).
Be mindful however that you may still get processing interference if the messages set over one cluster need significant more time to process than the messages sent over the other cluster and your processing app cannot keep up with the speed. (i.e. messages piling up in the processing app input queue)...
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|