Starting WebSphere MQ applications using triggers

 

Some WebSphere MQ applications that serve queues run continuously, so they are always available to retrieve messages that arrive on the queues. However,you might not want this when the number of messages arriving on the queues is unpredictable. In this case, applications could be consuming system resources even when there are no messages to retrieve.

WebSphere MQ provides a facility that enables an application to be started automatically when there are messages available to retrieve. This facility is known as triggering.

For information about triggering channels see WebSphere MQ Intercommunications.

This chapter introduces triggering, under these headings:

• What is triggering?

• Prerequisites for triggering

• Conditions for a trigger event

• Controlling trigger events

• Designing an application that uses triggered queues

• Trigger monitors

• Properties of trigger messages

• When triggering does not work

• What is triggering?
  

• Prerequisites for triggering
  

• Conditions for a trigger event
  

• Controlling trigger events
  

• Designing an application that uses triggered queues
  

• Trigger monitors
  

• Properties of trigger messages
  

• When triggering does not work
  

 

Parent topic:

Application Programming Guide

fg13830_