| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| triggering MQ Client applications |
« View previous topic :: View next topic » |
| Author |
Message
|
| RNStanich |
 Posted: Mon Jun 10, 2002 3:53 am Post subject: triggering MQ Client applications |
 |
|
Acolyte
Joined: 23 Apr 2002
Posts: 64
|
Hi all, hopefully a fairly straight forward question.
Is it possible to trigger a client application running on a different server than a MQSeries installation?
So, some application puts a message onto a queue on SVR1. A trigger monitor on SVR1 starts an application running on SVR2. That application then connects to SVR1, via MQ Client to retrieve the message.
Both SVR1 and SVR2 are probably Windows 2000, MQ is V5.2.1 or V5.3
Doable?
Thank you...
_________________
Regards, Bob |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Mon Jun 10, 2002 5:21 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
Nope. A trigger monitor must run on the same machine as the application it must start.
So in this case, you would install the client trigger monitor on SVR2. It would make a client connection to SVR1 to watch the init queue. When the QM generates a trigger message to the init queue on SVR1, the client trigger monitor on SVR2 would see this and then start the app on SVR2.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| RNStanich |
| Posted: Mon Jun 10, 2002 7:44 am Post subject: |
|
|
Acolyte
Joined: 23 Apr 2002
Posts: 64
|
Thank you Peter.
How about an opinion...? I would assume that the client trigger monitor is doing a get with an unlimited wait on the initiation queue across the network. Is there any advantage to having runmqtmc performing this wait versus an application waiting on a message, bypassing the triggering mechanism? Would runmqtmc be more stable?
_________________
Regards, Bob |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jun 10, 2002 8:07 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
In the end, both methods accomplish the same thing; when a message lands, your app handles it. However, does your design allow your application to just sit there and do nothing else all day long except wait?
The trigger monitor has nothing else to do, so who cares if it waits forever?
If you are going to trigger on first, then it makes no diff. But if you need to trigger multiple instances of your app (Trigger Every) or if you only want to start processing when x amount of messages are available (Depth), then runmqtmc will give you what you need out of the box.
fyi, If you use support pac MA7K, you can have the trigger monitor run as a Windows service, making it more robust.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| RNStanich |
| Posted: Mon Jun 10, 2002 9:21 am Post subject: |
|
|
Acolyte
Joined: 23 Apr 2002
Posts: 64
|
Thank you again Peter. You read my mind on the support pacs. That was my next move.
_________________
Regards, Bob |
|
| 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
|
|
|
|
