| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Help! Can't get Trigger working on W2K |
« View previous topic :: View next topic » |
| Author |
Message
|
| d-richard |
 Posted: Fri Oct 12, 2001 4:43 pm Post subject: |
 |
|
Newbie
Joined: 11 Oct 2001
Posts: 3
|
HELP! Please...
I think that I've set up my trigger monitor correctly; but, when I drop a
message in the triggered Q nothing happens.
Heres what I've done on our W2K server:
1) Created local Q - TEST.QL -
- trigger is 'ON' 'Every';
- init Q is SYSTEM.DEFAULT.INITIATION.QUEUE;
- process is 'BatchTest';
2) Created process - 'BatchTest'
- type: Windows NT;
- app ID: d:scriptsgothere.vbs;
- the app is a simple vbscript that opens a text file & writes one
record - works fine from the command line.
3) Created & started a Trigger Monitor
- q-name: SYSTEM.DEFAULT.INITIATION.QUEUE
4) Gave IUSR_MQADMIN read/write/execute access to d:scripts
Nothing shows up anywhere - no dead letters; nothing in
SYSTEM.DEFAULT.INITIATION.QUEUE; no alerts; no event messages - Nothing!
What do I do? Where do I look?
|
|
| Back to top |
|
 |
| kolban |
| Posted: Sun Oct 14, 2001 12:03 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
I would look in the error files on the file system of the local queue manager. In addition, start the trigger monitor from a DOS command prompt and look at the messages it sends to the console. When it processes a trigger message, it logs some information to the screen.
You might also want to post the runmqsc dumped versions of the queue, process and other definitions and we can look for errors. Also, the VBS script, not sure if that is "directly executable". Try something simpler like a CMD or BAT file ... just to start with. |
|
| Back to top |
|
|
| d-richard |
| Posted: Mon Oct 15, 2001 8:19 am Post subject: |
|
|
Newbie
Joined: 11 Oct 2001
Posts: 3
|
When I started the trigger monitor from the command line, all of the events that were stacked up in 'SYSTEM.DEFAULT.INITIALIZATION.QUEUE' fired off and ran to successful completion. This seems to indicate that the trigger monitor that MQSeries is starting doesn't work correctly. Why would that be?
There are no messages in the error log for the Q manager that are associated with any of the objects in this process. Nothing shows up in the NT event logs.
[ This Message was edited by: d-richard on 2001-10-15 09:22 ] |
|
| Back to top |
|
|
| sjackson |
| Posted: Thu Oct 18, 2001 11:31 am Post subject: |
|
|
Apprentice
Joined: 28 Jun 2001
Posts: 26
Location: Milwaukee
|
| I had the same problem. Starting the trigger monitor via the MQ Services GUI didn't work, but starting it with "runmqtrm" from the command line worked fine. Is this a known bug in the NT Services? |
|
| Back to top |
|
|
| d-richard |
| Posted: Fri Oct 26, 2001 10:42 am Post subject: |
|
|
Newbie
Joined: 11 Oct 2001
Posts: 3
|
I finally got my process to work. Looks like I may have had a couple of problems.
For some reason, the vbscript interpreter won't run from the triggered process. If I just use batch commands or run executables in my process, it seems to work fine.
Also, it seems that resource access must be specifically granted to MUSR_MQADMIN for all resources that the process touches. Very picky.
Thanks all for your help. |
|
| 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
|
|
|
|
