| Author |
Message
|
| ChrisBUK |
 Posted: Wed May 12, 2010 7:23 am Post subject: MQ Triggers license? |
 |
|
Newbie
Joined: 25 Mar 2008
Posts: 8
|
Hi,
Ive setup a MQ trigger as part of a WMB flow, the message has some WMB process on it, gets put on the Trigger Q, which triggers a Java App for some more processing, then back into WMB.
Ive asked about setting up the Trigger monitors in our other environments and have been told about "license restrictions" meaning we are unable to use MQ triggering on a broker QM.
I would have thought Triggering is just a standard feature of MQ and would be available for use when required.
Has anyone else heard of this license requirement before?
TIA,
Chris |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed May 12, 2010 7:39 am Post subject: Re: MQ Triggers license? |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ChrisBUK wrote: |
| I would have thought Triggering is just a standard feature of MQ and would be available for use when required. |
Well it is but...
| ChrisBUK wrote: |
| Has anyone else heard of this license requirement before? |
...license requirements and restrictions are what your site and IBM have agreed individually. For example (and this is a purely theoretical example) perhaps the license under which the broker's queue manager is being used restricts it to only be used for WMB. Hence the license prevents it's use with triggered non-WMB applications.
All license questions can only be answered by your IBM sales rep, who has the definitive view on what your license does & does not cover.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ChrisBUK |
| Posted: Wed May 12, 2010 7:44 am Post subject: |
|
|
Newbie
Joined: 25 Mar 2008
Posts: 8
|
Hmmm, ok thanks for the info.
I think i will seek more info on this setup then 
Thanks again |
|
| Back to top |
|
|
| fatherjack |
| Posted: Wed May 12, 2010 7:47 am Post subject: Re: MQ Triggers license? |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| Vitor wrote: |
| ChrisBUK wrote: |
| I would have thought Triggering is just a standard feature of MQ and would be available for use when required. |
Well it is but...
| ChrisBUK wrote: |
| Has anyone else heard of this license requirement before? |
...license requirements and restrictions are what your site and IBM have agreed individually. For example (and this is a purely theoretical example) perhaps the license under which the broker's queue manager is being used restricts it to only be used for WMB. Hence the license prevents it's use with triggered non-WMB applications.
All license questions can only be answered by your IBM sales rep, who has the definitive view on what your license does & does not cover. |
Presumably you have paid for the MQ license 
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed May 12, 2010 7:57 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
WMB itself acts like a trigger monitor in many ways so you should be able to find a way to use a message flow to start the application.
However any non-WMB use of MQ may fall outside the WMB/MQ license, but a MQ license is not expensive. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed May 12, 2010 8:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It seems odd to run the java app on the broker machine.
Why not ship the message out to a qmgr on another machine, do the triggering there, and move the messages back to broker. |
|
| Back to top |
|
|
| murdeep |
| Posted: Wed May 12, 2010 8:44 am Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
So triggering can't be used on a broker qmgr? That seems ridiculous.
In my env we have some flows where we don't wire the MQInput catch terminal and the message goes to the DLQ. We then trigger runmqdlq to move the message to a WMB_Exception queue.
Does this mean I am in violation of the WMQ licensing agreement?
Or how about triggering channels when moving messages say from the configmgr to the broker when they don't share a common qmgr?
I thought when you purchase WMB you get a fully functional WMQ license. For what they charge for WMB I'd hope so. |
|
| Back to top |
|
|
| murdeep |
| Posted: Wed May 12, 2010 8:46 am Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
| mqjeff wrote: |
It seems odd to run the java app on the broker machine.
Why not ship the message out to a qmgr on another machine, do the triggering there, and move the messages back to broker. |
LOL. Sorry Jeff can't do that since they're not allowed to use triggering to start the channel to move the message. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed May 12, 2010 8:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| murdeep wrote: |
| mqjeff wrote: |
It seems odd to run the java app on the broker machine.
Why not ship the message out to a qmgr on another machine, do the triggering there, and move the messages back to broker. |
LOL. Sorry Jeff can't do that since they're not allowed to use triggering to start the channel to move the message. |
That's patently false. Triggering channels can not possibly be a violation of the WMQ license that comes with broker. Using standard features of WMQ to allow broker to actually perform it's duty as an integration product CAN NOT be a violation. Triggering channels is using MQ in support of the functions you have purchased Broker to provide.
Using the WMQ license as a full production environment for something other than broker itself is *feasibly* a violation. So using standard triggering to run an entirely separate application under the same WMQ entitlement on the broker machine is potentially a license violation.
But configuring channels to start automatically to move messages to and from the Broker's queue manager can not be a violation.
Contact your IBM sales representative, tell them that the license is being misinterpreted and request intervention. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 12, 2010 9:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| murdeep wrote: |
| I thought when you purchase WMB you get a fully functional WMQ license. For what they charge for WMB I'd hope so. |
That's my point - you purchased WMB and under the terms of the license got a fully functional WMQ license. Maybe this site paid a little less and didn't. Only the IBM rep can say.
Terms and conditions vary on a site by site basis.
It's also possible whoever told the OP that triggering wasn't allowed under the license was blowing smoke.
Or doesn't like the idea of triggered apps running on the same qmgr as the broker & has come up with an ingenious reason to refuse it. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed May 12, 2010 9:08 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I always understood that MQ and DB2 came with WMB for use only with WMB.
However (a) MQ is cheap and (b) IBM probably won't lose sleep over triggering.
It's not actually the triggering that might be seen as a license violation but the use of a non-WMQ MQ application.
But as Jeff said, it's better to keep WMB and non-WMB applications apart. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed May 12, 2010 9:23 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| murdeep wrote: |
In my env we have some flows where we don't wire the MQInput catch terminal and the message goes to the DLQ. We then trigger runmqdlq to move the message to a WMB_Exception queue.
|
It would be INSANE if you were in violation of any license agreement simply triggering runmqdlq.
My advice is just do it and worry about more pressing matters. Then again, my legal counsel is worth exactly what you paid for it.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed May 12, 2010 11:13 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Hi ya Chris!
Sounds to me that your MQ admin is a bit overzealous. Maybe s/he doesn't understand that trigger process by default is inactive and s/he thinks if s/he creates the started task s/he violates some license.
If it were me, I would stand on her desk and look her in her baby blues till s/he created a trigger monitor for my use. Then again, my Cromaggeron features are very intimidating.
At the very least, hairpulling should do the trick. So easy, a caveman can do it.
Lance
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| murdeep |
| Posted: Wed May 12, 2010 11:19 am Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
| lancelotlinc wrote: |
Then again, my Cromaggeron features are very intimidating.
|
cro magnon?
google...so easy a caveman can do it |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed May 12, 2010 11:24 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| murdeep wrote: |
| lancelotlinc wrote: |
Then again, my Cromaggeron features are very intimidating.
|
cro magnon?
google...so easy a caveman can do it |
 |
|
| Back to top |
|
|
|
|
