Author |
Message
|
LoveLess |
Posted: Mon Oct 01, 2007 2:22 am Post subject: MQSeries Trigger Monitor Service ! |
|
|
 Novice
Joined: 26 Jun 2007 Posts: 23
|
Hi,
We currently have set up all of the queues & processes for triggering on a Win2K machine with MQSeries 6.
If we run the trigger with runmqtrm in the DOS prompt... then the trigger works great with our executable. However, if we use setup the Trigger Monitor as a MQService, the trigger does not work.
This is the Service configuration
Service Name :TRIGGERMONITOR
Start Command : C:\Program Files\IBM\WebSphere MQ\bin\runmqtrm.exe
Start Args : -m NEW2 -q SYSTEM.DEFAULT.INITIATION.QUEUE
Service type : Command type
Our executable is a .bat file.
Has anyone else had this issue? How did you solve it? Do we need a fix? Is there something else we need to do?
Is there some way to have the trigger started when the queue manager starts other than an MQSeries Service?
Please write back if you Guys need more information.
Thanks in Advance
 _________________ Screw the Roses, Send Me the Thorns |
|
Back to top |
|
 |
Vitor |
Posted: Mon Oct 01, 2007 2:25 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Does the trigger monitor run as the same user id in both instances?
Are there any associated errors in the event log?
Are there any symptoms aside from the triggered application not starting? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
LoveLess |
Posted: Mon Oct 01, 2007 2:45 am Post subject: |
|
|
 Novice
Joined: 26 Jun 2007 Posts: 23
|
Hi ,
Thanks for your time.
There seems to be no error associated in the event logs and I haven't observed any other symptoms aside from the triggered application not starting.
How do I check if trigger monitor is running as the same user id in both instances ?
Thanks
 _________________ Screw the Roses, Send Me the Thorns |
|
Back to top |
|
 |
Vitor |
Posted: Mon Oct 01, 2007 2:48 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
LoveLess wrote: |
How do I check if trigger monitor is running as the same user id in both instances ?
|
What user id was used to run the monitor in foreground? What id is the service configured to use? Are these the same?
 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Oct 01, 2007 2:50 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Anything started as a Service in MQ will be started by either mqm or MUSR_MQADMIN.
You almost certainly don't want to run a trigger monitor as that user. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Oct 01, 2007 2:52 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
jefflowrey wrote: |
Anything started as a Service in MQ will be started by either mqm or MUSR_MQADMIN.
|
Ah - I thought we were talking Windows Service  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
LoveLess |
Posted: Mon Oct 01, 2007 2:58 am Post subject: |
|
|
 Novice
Joined: 26 Jun 2007 Posts: 23
|
jefflowrey wrote: |
Anything started as a Service in MQ will be started by either mqm or MUSR_MQADMIN.
|
Form the task manager i can see that the service (MQ Service ,not a Windows Service) is running under my User Id!.Is that odd? _________________ Screw the Roses, Send Me the Thorns |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Oct 01, 2007 3:10 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
LoveLess wrote: |
jefflowrey wrote: |
Anything started as a Service in MQ will be started by either mqm or MUSR_MQADMIN.
|
Form the task manager i can see that the service (MQ Service ,not a Windows Service) is running under my User Id!.Is that odd? |
Depends on how you started the trigger monitor.
My preference is to define it and use amqmdain to start it...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
LoveLess |
Posted: Mon Oct 01, 2007 4:37 am Post subject: |
|
|
 Novice
Joined: 26 Jun 2007 Posts: 23
|
Hi,
Thanks for all those reponses.
Here is my defintion of the Service
DEFINE SERVICE(TRIGGERMONITOR) +
CONTROL(QMGR) +
SERVTYPE(SERVER) +
STARTCMD('C:\Program Files\IBM\WebSphere MQ\bin\runmqtrm') +
STARTARG('-m +NEW2+ -q SYSTEM.DEFAULT.INITIATION.QUEUE')
and then I started the MQ Service with the MQ Explorer,it still runs with my User Id and the application doesn't get triggered .May be I should install the SupportPac MA7K so it runs as a regular Windows service.
Thanks
 _________________ Screw the Roses, Send Me the Thorns |
|
Back to top |
|
 |
LoveLess |
Posted: Mon Oct 01, 2007 7:02 am Post subject: |
|
|
 Novice
Joined: 26 Jun 2007 Posts: 23
|
Its working Atlast..
The Application was already running in the background .
I could see it now in the task manager.
Thanks Vitor,jefflowrey,fjb_saper.
 _________________ Screw the Roses, Send Me the Thorns |
|
Back to top |
|
 |
werd |
Posted: Mon Oct 01, 2007 9:29 pm Post subject: |
|
|
Newbie
Joined: 13 Aug 2006 Posts: 4 Location: Sydney, Australia
|
I am getting an almost idnetical problem to yours ...
what did you do to make the trigger monitor work OK? |
|
Back to top |
|
 |
LoveLess |
Posted: Tue Oct 02, 2007 2:26 am Post subject: |
|
|
 Novice
Joined: 26 Jun 2007 Posts: 23
|
Sure.
Its a piece of cake!
Describe how you set up the envirenment ?
Are there any associated errors in the event log? _________________ Screw the Roses, Send Me the Thorns |
|
Back to top |
|
 |
werd |
Posted: Tue Oct 02, 2007 5:19 pm Post subject: |
|
|
Newbie
Joined: 13 Aug 2006 Posts: 4 Location: Sydney, Australia
|
here's the queue which receives the msgs:
DEFINE +
QLOCAL('PYMBLE_PROD.LAPA.AU.CMT.WINDOWS.RECV') +
PROCESS('MMMP.WINDOWS.RECV') +
TRIGGER +
INITQ('CMT.DPA.INITQ') +
USAGE(NORMAL) +
TRIGTYPE(FIRST) +
TRIGDPTH(1) +
TRIGMPRI(0) +
TRIGDATA(' ') +
REPLACE
here's the process:
DEFINE +
PROCESS('MMMP.WINDOWS.RECV') +
DESCR(' ') +
APPLTYPE(WINDOWS) +
APPLICID('D:\test\receive.cmd') +
USERDATA(' ') +
ENVRDATA(' ') +
REPLACE
here's the initq:
DEFINE QLOCAL('CMT.DPA.INITQ') +
NOTRIGGER +
INITQ(' ') +
USAGE(NORMAL) +
TRIGTYPE(NONE) +
TRIGDPTH(1) +
TRIGMPRI(0) +
TRIGDATA(' ') +
REPLACE
here's my trigger monitor:
DEFINE SERVICE(TRIGGER.MONITOR.2) +
CONTROL(QMGR) +
SERVTYPE(SERVER) +
STARTCMD('runmqtrm') +
STARTARG('-m PYMBLE_PROD -q CMT.DPA.INITQ') +
REPLACE
the msg goes to the deadqueue, with a reason of
'MQFB_APPL_CANNOT_BE_STARTED'
there are no error msgs in either the win event log or the MQ log
if I run the app (ie 'D:\test\receive.cmd') from a cmd window then it runs OK, this is obvously under my own userid
when the trigger mon tries to start the app then it is running under MUSR_MQADMIN ... correct?
Is this a problem with windows security? ... how did you setup MUSR_MQADMIN? what groups does it belong to? |
|
Back to top |
|
 |
LoveLess |
Posted: Wed Oct 03, 2007 8:05 am Post subject: |
|
|
 Novice
Joined: 26 Jun 2007 Posts: 23
|
Hi,
The environment you have set up is correct.It tried it out on my system and it works perfectly.
Are you sure the application is not running at all?.
Did you check the task manager?
What does your triggered application do?
If it displays any output on the screen(like opening note pad) am sure you will never see it because they run as background processes.
If its an application that writes into files or creates files am sure they will be present at the appropriate path which you have given.
I have configured MQ wizard to use my Id so all the process run at my own User Id, not MUSR_MQADMIN.
Try setting the trigger to Every and reset all the triggers,services and channels.
Hope it helps
Thanks
 _________________ Screw the Roses, Send Me the Thorns |
|
Back to top |
|
 |
Vitor |
Posted: Wed Oct 03, 2007 8:16 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
LoveLess wrote: |
Try setting the trigger to Every and reset all the triggers,services and channels.
|
Do not use this for anything other than diagnostic purposes.
A search of the forum will yield many discussion on why trigger Every is generally a bad idea design-wise. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|