| Author |
Message
|
| petmor |
 Posted: Tue Aug 20, 2002 12:36 pm Post subject: Browsing Queues and InhibitGet |
 |
|
Apprentice
Joined: 20 Jun 2002
Posts: 45
Location: Pasadena, CA
|
| Before I spend too much time digging through the docs, is there any way to browse the messages on a queue (really only the message at the head of the queue) when the inhibitGet attribute has been applied to the queue? |
|
| Back to top |
|
 |
| kolban |
| Posted: Tue Aug 20, 2002 1:57 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
| That should not be possible. Inhibit get means that no messages can be seen on the queue. Neither destrutively or browsed. |
|
| Back to top |
|
|
| bduncan |
| Posted: Tue Aug 20, 2002 4:48 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Kinda defeats the purpose of get inhibit in the first place... 
Of course, it might be nice to have a browse inhibit versus get inhibit - though I can't think of any reason why you'd want to have such granularity...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| nimconsult |
| Posted: Tue Aug 20, 2002 10:07 pm Post subject: |
|
|
Master
Joined: 22 May 2002
Posts: 268
Location: NIMCONSULT - Belgium
|
That's indeed not possible, but there may be a workaround solution if your objective is what I think.
Why not use queue aliases? On a local queue, define a queue alias for getting and one queue alias for browsing. You can then inhibit the queue alias instead of inhibiting the local queue itself.
I encountered the problem in an environment where they wanted to prevent applications from getting messages in the queue, but at the same time allow some manual interventions on the queue (browsing, editing, deleting, forwarding messages). The solution we selected was to configure all applications to access queue aliases only.
_________________
Nicolas Maréchal
Senior Architect - Partner
NIMCONSULT Software Architecture Services (Belgium)
http://www.nimconsult.be |
|
| Back to top |
|
|
| petmor |
| Posted: Wed Aug 21, 2002 8:49 am Post subject: Re: Browsing Queues and InhibitGet |
|
|
Apprentice
Joined: 20 Jun 2002
Posts: 45
Location: Pasadena, CA
|
| The objective is exactly as 'nimconsult' speculated - to allow data validation, etc, while disallowing access by applications. I'll investigate the queue local/queue alias workaround. Thanks everyone for your input! |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Aug 21, 2002 7:21 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You could also use setmqaut to only allow browsing on the queue for certain ids. The only problem with the alias queue idea is that you assume they will never find out what the real queue name is.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| nimconsult |
| Posted: Wed Aug 21, 2002 10:40 pm Post subject: |
|
|
Master
Joined: 22 May 2002
Posts: 268
Location: NIMCONSULT - Belgium
|
You can use setmqaut on queue aliases as well, and give no access to the local queue to prevent from bypassing the queue alias authority.
However, I think that the objective is not to protect against hackers but simply putting control on a production infrastructure (prevent accidental start-up of an application while doing interventions).
_________________
Nicolas Maréchal
Senior Architect - Partner
NIMCONSULT Software Architecture Services (Belgium)
http://www.nimconsult.be |
|
| Back to top |
|
|
|
|
