| Author |
Message
|
| kolban |
 Posted: Fri Apr 12, 2002 10:17 am Post subject: |
 |
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
Folks,
See the following for details of the MQDisable plugin node for WMQI 2.1. This node disables an input queue. Useful if an error has been encoutered in the flow which requires that you suspend further processing.
For those working in Java developing plugin nodes, source is also supplied which may be used as an illustration of how it works.
Feedback and comments requested ... please append to this thread.
Download from:
http://www.kolban.com/mq/wmqi/wmqi_mqdisable_node.htm
[ This Message was edited by: kolban on 2002-04-12 13:21 ] |
|
| Back to top |
|
 |
| kirani |
| Posted: Fri Apr 12, 2002 10:27 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Where to download this node from?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| kolban |
| Posted: Fri Apr 12, 2002 12:21 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
|
| Back to top |
|
|
| simon.starkie |
| Posted: Fri Apr 12, 2002 12:51 pm Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
Sounds like a winner.
You put the flow to sleep by setting the GET INHIBIT attribute for the MQ Queue that trigger the MQSI flow.
But...who is going to know this happened? Maybe a SendMail is a good idea (JMHO).
And not to create a broohaha, but didn't Kolban recently say:
"From a design perspective, having a message flow sleep goes against all that WMQI was designed for. If the flow sleeps, all the resources associate with that flow are locked up and held waiting. Would you put an EJB to sleep?".
[ This Message was edited by: simon.starkie on 2002-04-12 14:28 ] |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Apr 12, 2002 1:06 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Neil,
I just installed the plug-in on our server. The XML interface definition file and WDP files are missing. Do I have to create these files using SmartGuide? If so, I think this information should be added to the PDF document with attribute names (and class name).
Is there going to be a C version of this plug-in?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| kolban |
| Posted: Fri Apr 12, 2002 1:52 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
Simon,
Disabling a queue does not cause the message flow to block. It prevents that message flow from starting again. If there are other message flows associated with the execution group associated with other queues ... they will function perfectly and no resources will be held up.
Kirani,
I blew it  New refresh will be psoted within the hour with the additional definition required for Control Center definition.
[ This Message was edited by: kolban on 2002-04-12 15:00 ] |
|
| Back to top |
|
|
| kolban |
| Posted: Fri Apr 12, 2002 1:59 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
| Refresh uploaded ... now includes MQDisable.xml definition and documentation. |
|
| Back to top |
|
|
| simon.starkie |
| Posted: Fri Apr 12, 2002 2:29 pm Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
Neil,
Thanks. Yes, you are right, stopping the flow by disabling the get for the queue means that no new message threads will start. This is preferable, I think, to sleeping in the middle of a message flow which could, as you pointed out, result in locked resources until the sleep interval expires.
But I am still concerned that disabling the get attribute may go unnoticed (I know you indicated an exception is thrown afterwards, but...). Notifying someone (i.e. SendMail) would be a good thing to do. Somebody needs to manually re-enable the get attribute for the queue before the related message flow can start processing again. Come to think of it, just exactly how would MQSI programatically re-enable the get attribute for the queue once it's been disabled? Another custom plugin to enable get? And even if we had this, how would a flow containing the enable custom node get triggered?.
By the way, while playing with this, I had to install the MQSI Java PlugIn and I noticed that I was unable to get the IA76.exe self-extracting program to run when I had the latest JDSK 1.3 installed (it complained that it could not find/verify the JVM). This was resolved by falling back to the latest JDSK 1.2. Just thought you may be interested...
:smile:imon
[ This Message was edited by: simon.starkie on 2002-04-12 15:34 ] |
|
| Back to top |
|
|
| kolban |
| Posted: Sat Apr 13, 2002 7:39 am Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
This node has been developed and tested under WMQI 2.1. This release saw the support of Java plugins natively as part of the product. There is no need for the IA76 support pac which pre-dates WMQI 2.1. No testing has been done on WMQI 2.0.x.
The IA07 Support Pac provides an SMTP client capability to send an email message. This could be included post the MQDisable node to alert and admin. |
|
| Back to top |
|
|
| amigupta1978 |
| Posted: Tue Apr 16, 2002 10:46 pm Post subject: |
|
|
Centurion
Joined: 22 Jan 2002
Posts: 132
Location: India
|
Hi Neil,
Its quite a nice plugin since this featuere is always required i.e on error somehow we have to stop the message flow from processing.
But there is one suggestion. Can you make the queuename for making get disable dynamic i.e it should pick up the queuename at run time say the same way like in LocalEnvironment structure or any other structure.
Since the problem which I face is that I use same Error handling flow for many flows and the input queue name I always get from the MQMD.SourceQuename, so I actually donot know at buildtime which queue to disable.
Regards,
Amit
[ This Message was edited by: amigupta1978 on 2002-04-17 00:05 ] |
|
| Back to top |
|
|
| kolban |
| Posted: Wed Apr 17, 2002 6:57 am Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
| Thank you ... a fantastic idea. I will look into this ASAP. Nice one. |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Apr 17, 2002 8:22 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
There is another way to do this. If you are going to use MQDisable node in a sub-flow, you can promote Queue Name property of the node and then in main message flow use ESQL to assign appropriate queue name to it.
But not all people will use this node in a subflow, so providing facility to read queue name from some Tree would be very helpful!
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Coz |
| Posted: Tue May 21, 2002 12:13 am Post subject: |
|
|
Apprentice
Joined: 20 Feb 2002
Posts: 44
Location: Basel CH
|
Hey Kolban no source 
Any chance of it 'cause need to see how you do the GET INHIBITED to see if it's compatible with OS390.
Be interesting to see if it works as well cos my MQBrowse node works great on NT but doesnt on OS390. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed May 22, 2002 2:17 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Could it not automatically determine the input queue name of the message being processed? |
|
| Back to top |
|
|
| unilog |
| Posted: Mon Jul 15, 2002 5:34 am Post subject: MQDisable install on AIX ? |
|
|
Novice
Joined: 29 Apr 2002
Posts: 17
Location: Paris, France
|
Hi,
I use the MQDisable on NT Broker and that's work great, thanks !
But i try to use it on AIX, i put the mqdisable.jar on my <wmqi>/jplugin directory, restart the AIX broker ... and when i try to deploy my flow i have an error message (BIP2241E) that's say that there is no Lib to work with the MQDisableNode on the LIL path !?!
Did i forgot something ?
(i already use my own Java Plugin on AIX, and i have no trouble, but i use the context menu "Create an extension Node" to set them in the Control Center)
Thanks for your help
Marc studer (France) |
|
| Back to top |
|
|
|
|
