| Author |
Message
|
| njpmr |
 Posted: Thu Jan 18, 2007 8:50 am Post subject: Triggers |
 |
|
Novice
Joined: 18 Jan 2007
Posts: 10
|
New to MQ. OS is Windows 2000. MQ 5.3 fp 12 Set up application queue, turned trigger on, depth 1, trigger monitor running in q manager, trigger priority 0 so on and so forth... checked ALL requirements for trigger.
Never see trigger getting written to init Queue. Any suggestions on what else to check? Using local queues. Are there any particuliar options required for oen of the init queue? Thanks for any suggestions |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Jan 18, 2007 9:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If you don't have a trigger monitor on the init q, the queue manager doesn't generate the message. Hence you won't see it sitting on the queue.
If it is open, check the target queue isn't already open - likewise.
In short, go through the list of 14 (?) conditions listed for an init message to be raised. Most likely scenario is that one of them isn't met; the one that catches most people (including me) is the open queue.
Tip - run the trigger monitor as a foreground task until you get it working. This way you'll see the message (or not) in the window as it goes past.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| njpmr |
| Posted: Thu Jan 18, 2007 9:42 am Post subject: |
|
|
Novice
Joined: 18 Jan 2007
Posts: 10
|
Vitor,
Thanks for the tips. Question. When defining the trigger monitor I would assume you need to specify the init queue in the parameter tab. Hovever doing this seems to set the open input count to 1 for the queue which seems to contradict the manual that open input copunt must be 0. Could you shed any light on this? Also in the monitor what options should I use to open the init queue? Any help is appreciated. |
|
| Back to top |
|
|
| njpmr |
| Posted: Thu Jan 18, 2007 9:44 am Post subject: |
|
|
Novice
Joined: 18 Jan 2007
Posts: 10
|
| Vitor, Sorry after I reread it says the app queue must not have open input count of 1... |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 18, 2007 9:54 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| njpmr wrote: |
| Also in the monitor what options should I use to open the init queue? |
Use the standard trigger monitor (runmqtri ???? ) for all your trigger monitorings needs. Anything else is reinventing the wheel.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 18, 2007 10:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
runmqtrm
runmqtmc
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| njpmr |
| Posted: Thu Jan 18, 2007 11:20 am Post subject: |
|
|
Novice
Joined: 18 Jan 2007
Posts: 10
|
OK, please forgive my ignorance, but now I am a little confused. I thought the trigger monitor was more or less a service that needed to be running in the queue manager to cause a trigger to be written to the initiation queue. I thought I would then need another program to poll the init queue and take appropriate action when the message showed up.
If this is not the case I am not seeing where I link the trigger monitor and the app i want to start. Can you clear this up for me? Thanks in advance. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 18, 2007 11:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
well, there's a fairly good chapter on the whole business of triggering in the Application Programming Guide...
The gist is - the trigger monitor is what reads the Initiation Queue and starts your program.
The association between your program and the Application Queue is made on your application queue, in the "Process Name" field.
The message that goes on the initiation queue is built from the Process Definition that is referred to in the Process Name field.
The trigger monitor launches whatever program is specified in the initiation message.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| njpmr |
| Posted: Thu Jan 18, 2007 11:32 am Post subject: |
|
|
Novice
Joined: 18 Jan 2007
Posts: 10
|
| OK that clears things up for me. Thanks for all the help, much appreciated. |
|
| Back to top |
|
|
| njpmr |
| Posted: Thu Jan 18, 2007 2:29 pm Post subject: |
|
|
Novice
Joined: 18 Jan 2007
Posts: 10
|
I'm back.... Ok pouring through the posts I get that if I want to start a java app I need to name a cmd file in my process definition. Using the windows mq explorer, it does not seem to let me specify any path to this.
Says no ":" no" \" etc...
Ive tried placing the bat file where mq is installed but doesnt seem to be getting launched.
Any suggestions? Thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 18, 2007 3:24 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Create a new process definition, name it whatever you want.
Set the application Id in the process definition to the path to wherever you want your cmd file installed. This should be relative to the machine that will be running the trigger monitor!
Change your application queue to indicate the NAME of the PROCESS DEFINITION.
Go read the Application Programming Guide section on Triggering again, please.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jan 18, 2007 4:05 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
|
| Back to top |
|
|
|
|
