| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ5.3 Windows Triggering |
« View previous topic :: View next topic » |
| Author |
Message
|
| Hassan |
 Posted: Thu Apr 01, 2004 10:04 am Post subject: MQ5.3 Windows Triggering |
 |
|
Voyager
Joined: 01 Apr 2004
Posts: 81
Location: Toronto, Canada
|
Hi! I have the following setup,
1. Local Queue with Triggering setup for Every message and Initq defined.
2. Initq
3. Process with a batch file to be run on every trigger (START FILE.BAT)
Here's my problem,
when I start RUNMQTRM -m QMgrName -q INITQ from the command prompt all works as expected.
but when I setup a trigger monitor from the MQ Series Console GUI nothing works. I do see a cmd.exe against the user MUSR_MQADMIN in the task manger (services) but the batch file does not execute.
I have read somewhat similar posts here so I made MUSR_MQADMIN part of the local Administrators group alongwith MQM group .... this is exactly the same as the logon Id. I have used but still no success.
The batch file I have simply stops one sender channel, alters the transmission queue and starts another sender channel.
Please any help would be highly appreciated as I am close to throwing my keyboard against the wall  |
|
| Back to top |
|
 |
| offshore |
| Posted: Thu Apr 01, 2004 11:05 am Post subject: |
|
|
Master
Joined: 20 Jun 2002
Posts: 222
|
Hassan,
I'm going to attempt to offer some help here. I've used the Windows Trigger Monitor and have had a similar problem.
Alot of this is from memory, so bear with me....
1) Assuming this a Windows NT box, rename the .BAT to .CMD. Things seem to work much better for me when I did that.
2) If you don't think the application is "working" check the event log, the INITQ or DEADQ (can't remember). If you look in message properties through the MMC gui..it should give and error/reason code why it didn't start.
Also, we run most of trigger process with the /B. I believe this lets it run on background and lets other process's get triggered.
Finally, in the process definition log whats happening <or not happening> to a file. This can be done by altering the process definition like so:
"C:\MQTriggers\File.CMD >> C:\MQTriggers\FileLog.txt /B"
Hope this is some help. Most of this is from things that happened a year ago. |
|
| Back to top |
|
|
| JasonE |
| Posted: Thu Apr 01, 2004 11:24 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Make sure musr_mqadmin has read priviledges on both the root of the drive containing the app, and the root of the drive containing windows. Also ensure musr_mqadmin has read privs on winnt\system32.
The app launched cannot interact with the desktop so dont run anything GUI related.
If you still have problems, try filemon from www.sysinternals.com and watch for cmd.exe then the things it tries to access - look for access denied.
If it works from the command line and fails from the gui it is always either security (normally what I have described) or environmental - MUSR_MQADMIN does not have the same path, env vars etc as the signed on user, so ensure anything required by the triggered app is available system wide. |
|
| Back to top |
|
|
| Hassan |
| Posted: Fri Apr 02, 2004 8:49 am Post subject: |
|
|
Voyager
Joined: 01 Apr 2004
Posts: 81
Location: Toronto, Canada
|
Thanks Jason & offshore .....
filemon did the trick, security it seems, was not an issue since I already had the MUSR_MQADMIN as part of the Administrators group.
It was the "PATH" all along  , now I am setting the required path as a first setp in by .bat file and giving explicit path whenever accessing any file.
Without filemon I'd still be banging my head against the keyboard
Thanks again & cheers  |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
