| Author |
Message
|
| fde |
 Posted: Wed Nov 24, 2010 6:13 am Post subject: configuring local resolve before cluster resolve |
 |
|
Acolyte
Joined: 05 Jul 2007
Posts: 65
|
Hello,
in our mq cluster environment, there are multitple objects with the same name on different cluster queuemanagers.
There is a clusterqueue named XYZ and on another queuemanager there is a local alias queue named XYZ too.
Is it possible to change the resolving of mq objects for a queuemanager, so that he would find local objects before nonlocal objects?
Best Regards
_________________
Global warming is an unintentional side effect of SOA's hotness.
-- http://soafacts.com/
a business integration methodology |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Nov 24, 2010 6:15 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Yes. This is part and parcel of cluster workload balancing.
In MQ v5.3, for example, it always always always chose the local instance over any cluster instance.
In v6.0 and later, this is a cluster workload balancing property of each and every queue. |
|
| Back to top |
|
|
| fde |
| Posted: Wed Nov 24, 2010 6:17 am Post subject: |
|
|
Acolyte
Joined: 05 Jul 2007
Posts: 65
|
|
| Back to top |
|
|
| exerk |
| Posted: Wed Nov 24, 2010 6:19 am Post subject: Re: configuring local resolve before cluster resolve |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| fde wrote: |
| ...There is a clusterqueue named XYZ and on another queuemanager there is a local alias queue named XYZ too... |
Where does the QALIAS resolve to?
_________________
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 |
|
|
| fde |
| Posted: Wed Nov 24, 2010 7:03 am Post subject: |
|
|
Acolyte
Joined: 05 Jul 2007
Posts: 65
|
The QAlias resolves to the clusterqueue which has the same name.
This is, because I use OAM to restrict access to the clusterqueue.
Writing to the clusterqueue from another cluster queuemanager is rejected unless I give access to the transmissionqueue. If I give access to the transmission queue, the target OAM settings of the clusterqueue are ignored and a client could put on any clusterqueue over that transmission queue.
One solution was to create a local QAlias, where the put occurs and give appropriated access to the alias. The alias is than resolved to the target clusterqueue.
_________________
Global warming is an unintentional side effect of SOA's hotness.
-- http://soafacts.com/
a business integration methodology |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Nov 24, 2010 7:15 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| fde wrote: |
The QAlias resolves to the clusterqueue which has the same name...
...One solution was to create a local QAlias, where the put occurs and give appropriated access to the alias. The alias is than resolved to the target clusterqueue. |
10 out 10! 
My preferred method too. In which case, in your setup, the 'local' QALIAS needs always to be resolved first.
EDIT: The settings mqjeff was probably alluding to are the CLWLUSEQ and associated attributes.
_________________
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 |
|
|
| fde |
| Posted: Wed Nov 24, 2010 7:42 am Post subject: |
|
|
Acolyte
Joined: 05 Jul 2007
Posts: 65
|
|
| Back to top |
|
|
| exerk |
| Posted: Wed Nov 24, 2010 7:44 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
I would hazard that you do not need to make any changes to your current setup...
_________________
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 |
|
|
|
|
