| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Getting a Handle on the Trigger Message |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vin |
 Posted: Fri Jun 21, 2002 10:24 am Post subject: Getting a Handle on the Trigger Message |
 |
|
Master
Joined: 25 Mar 2002
Posts: 212
Location: India
|
| I've set up an application queue for trrigerring and my Question Is how do I get this message from the Queue. The application which starts up when the message arrives on the queue set up for triggering has to get the trigger message and process it. Thanks very much. |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Fri Jun 21, 2002 10:56 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Hmmm... Think this is the continuation of your problem from the other thread.
You need to have the following to get your app triggered and retrive message off the queue.
1) Local queue which is set for triggering.
2) Initiation queue.
3) Process definition, which holds the name of the app to be triggerred.
4) Trigger monitor, which actually triggers the application mentioned in your process definition.
5) Most importantly, all the rules for app triggerring need to be met for this whole thing to happen. Check out triggerring manual for more info on this.
The app which is triggerred need to retrieve the message off the queue. This is what should go in the code of the triggered app.
Hope this helps.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| bduncan |
| Posted: Fri Jun 21, 2002 12:39 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Vin,
I think you are confusing the trigger message and the message that causes the trigger to occur. Remember, when your message lands on a queue, and the arrival of this message satisfies ALL trigger conditions for that queue, a new message will be created. This message is called the trigger message, and is completely independent of your message. This message is placed on whatever initiation queue you specified, which the trigger monitor is watching. The trigger monitor will retrieve the trigger message which contains the information to trigger your application. The trigger monitor will start your application, and now it is up to your application to open the triggered queue and retrieve YOUR message (the one that caused the trigger to occur). Note that the trigger message is consumed by the trigger monitor. Your application will never have access to the actual trigger message.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| 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
|
|
|
|
