You can set a service to run in the
foreground. Under services\Log On you need to set it up running under
the local system account and select allow service to interact with the
desktop. I havent personally tried with MQSeries, but it may be
worth a try. It also may have unexpected and unwanted side-effects.
Regards,
___
Chris Howarth
CommerceQuest
UK Ltd
-Original Message-
From: Benjamin Zhou
[mailto:[EMAIL PROTECTED]
Sent: 07 July 2003 13:41
To: [EMAIL PROTECTED]
Subject: Re: Weird triggering
problem
... and I am no novice.
well, you seem to be a novice with
starting applications in the fore- or background.
Just kidding ..., sorry.
if you want to launch a GUI application,
it must be run in the foreground. If you start it with a service, you'll have
it running in the background. Of course you can't seethem on your
screen,they are all in the background,
spawnedfromthe runmqtrm service.
This is not just for NT, try typing this
command in UNIX:vi , can you see the editor window?
So if you want to start your GUI in the
foreground, let it be triggered by a trigger monitor running in the foreground
- command line.
cheers,
Benjamin Zhou
State Street Corp.
-Original
Message-
From: Roger Lacroix [mailto:[EMAIL PROTECTED]
Sent: Friday, July 04, 2003 6:55
PM
To: [EMAIL PROTECTED]
Subject: Weird triggering problem
All,
I am having a problem with triggering from the Trigger Monitor as a
Service. I need to launch a GUI Windows program on a Windows 2000
box using WMQ v5.3 CSD3.
No matter what I do, I cannot trigger my GUI Windows application (and I am no
novice). So I thought I would do a basic test and launch notepad.
In the process definition, I set the AppID to start C:\WinNT\notepad.exe
I created the Trigger Monitor service and used a blank as the initiation queue
name (this defaults to SYSTEM.DEFAULT.INITIATION.QUEUE).
So put a message on the triggering queue nothing happens. I cleared the
queue and tried it several times - nothing.
So I stopped the Trigger Monitor service, open a Command Prompt and typed runmqtrm.exe (no parameters specified!!). I put a message on the triggering queue
(same queue) and viola, notepad appeared. (I did not change any of the
queue or process definitions).
So, I stopped runmqtrm at the Command Prompt (closed notepad), started the
Service Trigger Monitor and put a message on the triggering queue - nothing
again
After using IBM's name in vain, I checked the Windows Task Manager. Under the
Applications tab, it was normal looking but under the
Processes tab it showed that I had 5 notepad programs running. I
also noticed several copies of my missing program that I did not think was
started.
So I looked at my Taskbar and also pressed Alt-Tab, there were no notepad
programs (or my GUI appl.). If I try to kill them, I get Access
denied. The only way to get rid of them is by rebooting.
I looked in the manuals but I don't see any restrictions about launching GUI
applications from the Service Trigger Monitor.
Obviously the simple solution is to run the trigger monitor from the Command
Prompt but WHY. Why can't Trigger Monitor as a Service successfully start
a Windows GUI application? (i.e. AppID set to start
C:\WinNT\notepad.exe)
Anybody got any ideas?
later
Roger...
