ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » MQ Trigger not working

Post new topic  Reply to topic Goto page 1, 2, 3  Next
 MQ Trigger not working « View previous topic :: View next topic » 
Author Message
ravi_sri24
PostPosted: Tue Jan 15, 2013 2:36 am    Post subject: MQ Trigger not working Reply with quote

Voyager

Joined: 11 May 2006
Posts: 83

Hi All,

I have setup MQ trigger with below details in Windows but it's not working to trigger the application.

below are configured on local queue :

trigger control : On
Trigger Type : First
initiation Queue : test
process name : Cal

Created Process Defination :

Process Name : Cal
ApplicationID : 'C:\WINDOWS\system32\calc.exe
Application Type : Windows


as per my understanding as soon as I placed a message on local queue qmgr should generate message and send it to initiation queue but I am not able to find that.

can you please help me if I am missing anything.

MQ verion is : 7.0.1.5
Back to top
View user's profile Send private message
ravi_sri24
PostPosted: Tue Jan 15, 2013 2:43 am    Post subject: Reply with quote

Voyager

Joined: 11 May 2006
Posts: 83

sorry Queue Manager sending the message to Initiation queue but after that it's not invoking application
Back to top
View user's profile Send private message
bruce2359
PostPosted: Tue Jan 15, 2013 5:09 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9415
Location: US: west coast, almost. Otherwise, enroute.

Do you have the supplied trigger-monitor application (runmqtrm) running? Does it name the initiation queue you've specified?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
ravi_sri24
PostPosted: Tue Jan 15, 2013 5:43 am    Post subject: Reply with quote

Voyager

Joined: 11 May 2006
Posts: 83

bruce2359 wrote:
Do you have the supplied trigger-monitor application (runmqtrm) running? Does it name the initiation queue you've specified?


thanks for your response

I am running trigger monitor by creating service but when I have started trigger monitor through command prompt it's working.

can I know how to run the trigger monitor as background process and how we know that trigger monitor is running or stopped?
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Jan 15, 2013 5:55 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

ravi_sri24 wrote:
bruce2359 wrote:
Do you have the supplied trigger-monitor application (runmqtrm) running? Does it name the initiation queue you've specified?


thanks for your response

I am running trigger monitor by creating service but when I have started trigger monitor through command prompt it's working.

can I know how to run the trigger monitor as background process and how we know that trigger monitor is running or stopped?


If you create it as a service, it runs in the background without necessarily being able to interact with the logged in user.

This is great, as long as the programs you are triggering do not expect to interact with the logged in user. I suspect you will find that calc.exe expects user input.

You should be able to a) see an instance of runmqtrm listed in the running processes, b) potentially see a number of calc.exe instances in the list of running processes.

If you create the trigger monitor as a qmgr service, and configure the service to be managed by the queue manager, you will be able to tell it's running because the status of the service shows as started.

You could also look at using supportPac MA7K. This is listed as a client trigger monitor, but it will happily run using a bindings connection to a local qmgr as well.
Back to top
View user's profile Send private message
exerk
PostPosted: Tue Jan 15, 2013 6:02 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

mqjeff wrote:
This is great, as long as the programs you are triggering do not expect to interact with the logged in user. I suspect you will find that calc.exe expects user input.

I think notepad.exe doesn't so might be a better one to use?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
ravi_sri24
PostPosted: Tue Jan 15, 2013 6:05 am    Post subject: Reply with quote

Voyager

Joined: 11 May 2006
Posts: 83

mqjeff wrote:
If you create it as a service, it runs in the background without necessarily being able to interact with the logged in user.

This is great, as long as the programs you are triggering do not expect to interact with the logged in user. I suspect you will find that calc.exe expects user input.

You should be able to a) see an instance of runmqtrm listed in the running processes, b) potentially see a number of calc.exe instances in the list of running processes.

If you create the trigger monitor as a qmgr service, and configure the service to be managed by the queue manager, you will be able to tell it's running because the status of the service shows as started.

You could also look at using supportPac MA7K. This is listed as a client trigger monitor, but it will happily run using a bindings connection to a local qmgr as well.


thanks Jeff

it's not working as expected when I have configured Trigger Monitor as a service, I can see message coming into Initiation queue but it's not invoking calc.exe.

but when I run the trigger monitor through command prompt it's working.
Back to top
View user's profile Send private message
exerk
PostPosted: Tue Jan 15, 2013 6:09 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

ravi_sri24 wrote:


it's not working as expected when I have configured Trigger Monitor as a service, I can see message coming into Initiation queue but it's not invoking calc.exe.

but when I run the trigger monitor through command prompt it's working.

Please paste the definitions of your queues and service objects, thank you.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
ravi_sri24
PostPosted: Tue Jan 15, 2013 6:26 am    Post subject: Reply with quote

Voyager

Joined: 11 May 2006
Posts: 83

exerk wrote:
ravi_sri24 wrote:


it's not working as expected when I have configured Trigger Monitor as a service, I can see message coming into Initiation queue but it's not invoking calc.exe.

but when I run the trigger monitor through command prompt it's working.

Please paste the definitions of your queues and service objects, thank you.



I have created all MQ objects through the MQ Explorer but below are details.

Define ql(trigger_enable) TRIGGER TRIGTYPE(FIRST) TRIGDPTH(1) INITQ(test) PROCESS(Cal)

define ql(test)

define process(Cal) APPLTYPE(WINDOWS) APPLICID(C:\WINDOWS\system32\calc.exe)

define service(trig) STARTCMD(C:\"Program Files"\IBM\"WebSphere MQ"\bin\runmqtrm.exe) STARTARG(-m WMS -q test) SERVTYPE(SERVER) CONTROL(QMGR)
Back to top
View user's profile Send private message
exerk
PostPosted: Tue Jan 15, 2013 6:29 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

ravi_sri24 wrote:
define service(trig) STARTCMD(C:\"Program Files"\IBM\"WebSphere MQ"\bin\runmqtrm.exe) STARTARG(-m WMS -q test) SERVTYPE(SERVER) CONTROL(QMGR)

This looks a bit iffy to me. What's wrong with STARTCMD("C:\Program Files\IBM\WebSphere MQ\bin\"runmqtrm.exe) ?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Jan 15, 2013 6:30 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

exerk wrote:
ravi_sri24 wrote:
define service(trig) STARTCMD(C:\"Program Files"\IBM\"WebSphere MQ"\bin\runmqtrm.exe) STARTARG(-m WMS -q test) SERVTYPE(SERVER) CONTROL(QMGR)

This looks a bit iffy to me. What's wrong with STARTCMD("C:\Program Files\IBM\WebSphere MQ\bin\"runmqtrm.exe) ?


It would be helpful as well to add something to the start args to redirect the standard out to a file, or otherwise instruct runmqtrm to write to a file rather than standard out.
Back to top
View user's profile Send private message
ravi_sri24
PostPosted: Tue Jan 15, 2013 6:45 am    Post subject: Reply with quote

Voyager

Joined: 11 May 2006
Posts: 83

mqjeff wrote:
exerk wrote:
ravi_sri24 wrote:
define service(trig) STARTCMD(C:\"Program Files"\IBM\"WebSphere MQ"\bin\runmqtrm.exe) STARTARG(-m WMS -q test) SERVTYPE(SERVER) CONTROL(QMGR)

This looks a bit iffy to me. What's wrong with STARTCMD("C:\Program Files\IBM\WebSphere MQ\bin\"runmqtrm.exe) ?


It would be helpful as well to add something to the start args to redirect the standard out to a file, or otherwise instruct runmqtrm to write to a file rather than standard out.


can you provide some example to write to file.
Back to top
View user's profile Send private message
exerk
PostPosted: Tue Jan 15, 2013 6:56 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

ravi_sri24 wrote:
mqjeff wrote:
exerk wrote:
ravi_sri24 wrote:
define service(trig) STARTCMD(C:\"Program Files"\IBM\"WebSphere MQ"\bin\runmqtrm.exe) STARTARG(-m WMS -q test) SERVTYPE(SERVER) CONTROL(QMGR)

This looks a bit iffy to me. What's wrong with STARTCMD("C:\Program Files\IBM\WebSphere MQ\bin\"runmqtrm.exe) ?


It would be helpful as well to add something to the start args to redirect the standard out to a file, or otherwise instruct runmqtrm to write to a file rather than standard out.


can you provide some example to write to file.

Something along the lines of:

STDOUT('C:\Temp\+QMNAME+_trigger_stdout.txt') +
STDERR('C:\Temp\+QMNAME+_trigger_stderr.txt') +

A freebie - I'm in a generous mood today
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
ravi_sri24
PostPosted: Tue Jan 15, 2013 7:26 am    Post subject: Reply with quote

Voyager

Joined: 11 May 2006
Posts: 83

exerk wrote:
ravi_sri24 wrote:
mqjeff wrote:
exerk wrote:
ravi_sri24 wrote:
define service(trig) STARTCMD(C:\"Program Files"\IBM\"WebSphere MQ"\bin\runmqtrm.exe) STARTARG(-m WMS -q test) SERVTYPE(SERVER) CONTROL(QMGR)

This looks a bit iffy to me. What's wrong with STARTCMD("C:\Program Files\IBM\WebSphere MQ\bin\"runmqtrm.exe) ?


It would be helpful as well to add something to the start args to redirect the standard out to a file, or otherwise instruct runmqtrm to write to a file rather than standard out.


can you provide some example to write to file.

Something along the lines of:

STDOUT('C:\Temp\+QMNAME+_trigger_stdout.txt') +
STDERR('C:\Temp\+QMNAME+_trigger_stderr.txt') +

A freebie - I'm in a generous mood today



even through it's defined to generate log files it's not generating any files.
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Jan 15, 2013 7:27 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

ravi_sri24 wrote:
exerk wrote:
ravi_sri24 wrote:
mqjeff wrote:
exerk wrote:
ravi_sri24 wrote:
define service(trig) STARTCMD(C:\"Program Files"\IBM\"WebSphere MQ"\bin\runmqtrm.exe) STARTARG(-m WMS -q test) SERVTYPE(SERVER) CONTROL(QMGR)

This looks a bit iffy to me. What's wrong with STARTCMD("C:\Program Files\IBM\WebSphere MQ\bin\"runmqtrm.exe) ?


It would be helpful as well to add something to the start args to redirect the standard out to a file, or otherwise instruct runmqtrm to write to a file rather than standard out.


can you provide some example to write to file.

Something along the lines of:

STDOUT('C:\Temp\+QMNAME+_trigger_stdout.txt') +
STDERR('C:\Temp\+QMNAME+_trigger_stderr.txt') +

A freebie - I'm in a generous mood today



even through it's defined to generate log files it's not generating any files.


So something's wrong then....
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2, 3  Next Page 1 of 3

MQSeries.net Forum Index » General IBM MQ Support » MQ Trigger not working
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.