| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSeries Triggers and Windows Applications |
« View previous topic :: View next topic » |
| Author |
Message
|
| rivast_2001 |
 Posted: Mon Jul 19, 2004 11:10 am Post subject: MQSeries Triggers and Windows Applications |
 |
|
Novice
Joined: 14 Jul 2004
Posts: 15
Location: Mansfield, MA
|
We are trying to setup a process where a message will be posted to a queue in the iSeries and at the same time we need to setup a trigger that excutes a program on a Windows machine when this message arrives to the queue. How can I setup the trigger to execute the Windows application from the iSeries machine?
Thanks in advance, |
|
| Back to top |
|
 |
| kirani |
| Posted: Mon Jul 19, 2004 11:27 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Please take a look at Triggering in the client environment topic (Chapter 12) in MQSeries Clients manual.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jul 19, 2004 11:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You will need to install an MQ Client and a trigger monitor program on the Windows machine. There's a support pack that supplies an MQ Client Trigger Monitor Service for Windows.
Then you configure a process definition on the iSeries queue manager that is a Windows process type and includes the path ON THE WINDOWS MACHINE to the program you want to run. Set up an initiation queue, and assign it and the process definition to the queue you want triggered. Then enable triggering on the queue.
Then configure the Trigger Monitor service so it knows how to connect to your iSeries queue manager, and point it at the initiation queue you created. Once you see that the initiation queue has an Open Input Count, then you know that the trigger monitor is running and connected.
There will also need to be some security authorizations done.
Trust me when I say that this is easier than the other approach - which is to write an iSeries application that makes a network connection to a Windows program which then starts your real Windows program.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
