| Author |
Message
|
| passthebeer |
 Posted: Wed Mar 26, 2003 1:03 pm Post subject: Trigger question |
 |
|
Newbie
Joined: 26 Mar 2003
Posts: 2
|
Just starting to work with MQSeries...
We currently have some local queues which have their own trigger queues and process definitions associated with each one of them. If we create seperate trigger monitors (via MQServices) for the trigger queues, all is well and we get the results we are looking for.
However, my boss was wondering if we need to keep maintaining seperate trigger queues and trigger monitors, or if we could just use one trigger queue and one trigger monitor? My testing I did so far doesn't seem to like this solution. I am missing something?  |
|
| Back to top |
|
 |
| Keka |
| Posted: Wed Mar 26, 2003 1:46 pm Post subject: |
|
|
Voyager
Joined: 28 Dec 2002
Posts: 96
|
You can have one initiation queue and one triget monitor.. Specify the same initiation queues for all those queues that you want to trigger and it will work. There will be a disadvantage though, If one of the applications on one of those queues is slow then it will slow down all the other triggered applications as the triggerMonitor will not trigger another application until the last application finished processing..
Hope this helps..
keka
_________________
Keka |
|
| Back to top |
|
|
| clindsey |
| Posted: Wed Mar 26, 2003 2:05 pm Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
Just to add a litte more to what Keka said.....
Each queue that gets triggered also has a process definition. If your application that gets launched via this process definition reads the TMC structure, it can determine which queue to go process. In this case, you
can also share the same process definition. Otherwise you need a process definition for each queue so you can pass the queue name in the process definition.
Hope this helps,
Charlie |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 26, 2003 2:16 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Also, Keka's concern about one process sharing an initiation queue slowing down the other processes is only true if you are not starting each process as a separate task (either by using the '&' on unix or 'start' on Windows, or appropriate function on your OS). In this case, the trigger monitor only waits until the process has started, rather than waiting until it has finished.
However, a slightly different face on the same issue is how many things are impacted if the triggering system breaks? If you have multiple trigger monitors running, and processing multiple initiation queues, then each one can only impact a small set of things. If you have one trigger monitor, using one initation queue, and it shuts down for some reason, everything is halted. You may want multiple trigger monitors/queues for different systems or applications or task priority levels. |
|
| Back to top |
|
|
| passthebeer |
| Posted: Fri Mar 28, 2003 7:23 am Post subject: |
|
|
Newbie
Joined: 26 Mar 2003
Posts: 2
|
Thanks for the advice and information.
Its certainly sounds like we can use only one trigger monitor and one init queue if we so desire, but it is nice to hear what the possible impacts and trade offs are if we choose this direction. |
|
| Back to top |
|
|
| ping master |
| Posted: Fri Apr 04, 2003 7:01 am Post subject: |
|
|
Centurion
Joined: 20 Sep 2002
Posts: 116
Location: USA
|
| has anyone ever set up trigger monitors to kick off an external program? |
|
| Back to top |
|
|
| bduncan |
| Posted: Fri Apr 04, 2003 11:40 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
What exactly do you mean by an "external" program?
On a different machine than the trigger monitor?
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| jlamond |
| Posted: Wed May 07, 2003 6:32 pm Post subject: |
|
|
Voyager
Joined: 28 May 2002
Posts: 94
Location: Paris
|
Don't forget that you can start multiple instance of the trigger monitor over the same initq. This is a better then detaching process like the use of & on unix or start on NT. runmqtrm does send trigger message to the dead letter queue when the lunched process ended with a none zero return code.
_________________
Jean-Marc |
|
| Back to top |
|
|
|
|
