MQSeries.net :: View topic

jsware · Posted: Mon Feb 21, 2005 11:15 am Post subject:

I am at a cross-roads attempting to get JMS pub/sub working in a "production worthy" manner.

If I configure JMS to send messages to my WBIMB broker, I can control the security of topics on which the JMS app can publish. However, if the channel between the JMS app's qmgr is down, or WBIMB is unavailable, the JMS app errors waiting for a response from WBIMB as too the success/failure of the publication. This appears to be a report option I cannot control.

This increases the coupling and dependancy between the JMS app and WBIMB which I don't want.

I then proceeded to setup base MQ pub/sub (MA0C support pac - now included as part of CSD08). This worked fine. I set the JMS app's queue manager to run an mq broker, set that broker's parent to my WBIMB broker and was able to make publications, even if WBIMB was unavailable (when WBIMB was available again the publication was processed and copied to all subscribers). My mq broker sent report option based responses when it forwarded the publication to its parent WBIMB broker.

This stops the JMS app being dependant on WBIMB (I'm happy with a dependancy on the local qmgr and local mq broker). However, I've now lost my security. Messages forwarded from my mq broker upto WBIMB have a user identifier of 'mqm' rather than the JMS app's user id. I now can't stop the JMS app from publishing to any topic he chooses.

How can I have my cake and eat it? I want to decouple my JMS app from WBIMB, but maintain a level of security so the JMS app can only publish on topics I authorise him to.
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price.