| Author |
Message
|
| techno_freak |
 Posted: Tue Jan 04, 2011 3:34 am Post subject: Qalias vs cluster Q |
 |
|
Novice
Joined: 23 Nov 2010
Posts: 12
|
Hey Guys,
Looking for difference or advantage using alias Q over cluster Q.
With in cluster environment we can use qalias to put messages in Q cluster .
We can put messages in cluster Q directly from remote QM.
Which one is the best among both process and why. If you guys recommend any doc to know the advantages please let me know.
Thanks in advance. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Jan 04, 2011 3:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| A QAlias provides a security point that is distinct from the cluster transmit queue. |
|
| Back to top |
|
|
| techno_freak |
| Posted: Tue Jan 04, 2011 6:59 pm Post subject: |
|
|
Novice
Joined: 23 Nov 2010
Posts: 12
|
Hey Jeff if you could refer any doc to get knowledge about it that will be a help for me.
Or If you could explain that will be great. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jan 04, 2011 7:27 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If you create a qalias on the local qmgr to a qcluster, you can issue setmqaut on the local qmgr against the qalias. You can't issue setmqaut against qclusters.
Last edited by mqjeff on Wed Jan 05, 2011 2:59 am; edited 1 time in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 04, 2011 8:01 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Looking for difference or advantage using alias Q over cluster Q. |
Two entirely different things.
An alias queue definition provides another name for a real local queue.
A cluster queue is a real local queue with the CLUSTER() attribute set to the name of the cluster. There may be multiple instances of the same cluster queue is a cluster.
_________________
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 |
|
|
| techno_freak |
| Posted: Wed Jan 05, 2011 3:11 am Post subject: |
|
|
Novice
Joined: 23 Nov 2010
Posts: 12
|
[quote="bruce2359"]
| Quote: |
| Looking for difference or advantage using alias Q over cluster Q. |
Let me rephrase my question again.
I am looking for an advantage of qalias over putting msg directly to Cluster XMITQ..
As Jeff stated it allow us to use setmqaut to provide auhorization to qalias.
But app can directly put msg in xmitq and we can give authorization on Q cluster(using for workload sharig, exist same Q on 3 diff QMs in same cluster) and application can consume it from cluster Q.
Now Question is whats an advantage over to provide authorization to qalias v/s cluster who is using for workload sharing.
Thanks for your response. |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Wed Jan 05, 2011 5:07 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| techno_freak wrote: |
| But app can directly put msg in xmitq and we can give authorization on Q cluster(using for workload sharig, exist same Q on 3 diff QMs in same cluster) and application can consume it from cluster Q. |
An application, which is able to put messages directly to a XmitQ is able, to put a message to any queue which can be reached via this XmitQ.
An application, which is able to put messages directly to the Cluster-XmitQ is able, to put a message to any queue in the cluster.
If you use an AliasQ which points to a specific ClusterQ the application does not need the permission, to put directly to the Cluster-XmitQ. So this application now is only able to put to that specific ClusterQ - doesn't matter, if there are one or more instances of this Q in the cluster.
Hope this answers your question.
_________________
Regards
Hubert |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jan 05, 2011 6:06 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| HubertKleinmanns wrote: |
An application, which is able to put messages directly to a XmitQ is able, to put a message to any queue which can be reached via this XmitQ.
An application, which is able to put messages directly to the Cluster-XmitQ is able, to put a message to any queue in the cluster. |
caveat. It's only able to put to queues that are accessible to the MCAUSER on the receiving channel....  |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jan 05, 2011 7:13 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I am looking for an advantage of qalias over putting msg directly to Cluster XMITQ.. |
For clarity:
An application does an mqopen (or equivalent) to a q definition. This definition can be a QRemote, QAlias, QModel, or QLocal.
The mqopen process resolves the name of the queue to a real local queue. It is this resolved local queue name where the application puts a message.
Your apps should NOT be mqopen-ing the SCTQ directly.
An alias allows for different security rules. An alias allows for the the real local queue to be put/get enabled, while the alias is put/get inhibited.
_________________
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 |
|
|
|
|
