Starting listeners by triggering

We can cause SOAP/WebSphere MQ listeners to start automatically by using triggering. This is done by setting the -tmq option and supplying a trigger queue name when you run the deployment utility. We can also specify a trigger monitor program by setting the -tmp option.

For example:

amqwdeployWMQService -f javaDemos/service/StockQuoteAxis.java -tmq trigger.monitor.queue 
-tmp trigmon

When SOAP/WebSphere MQ listeners are activated by the trigger monitor process, they normally run under the user ID that invokes the trigger monitor. However, if the trigger monitor is activated on UNIX systems with a setuid trigger monitor, such as the supplied runmqtrm utility, the listeners execute under the mqm user id. Where security is an issue, ensure that the listeners are started under appropriate user IDs

Triggering is described in WebSphere MQ Application Programming Guide and WebSphere MQ Intercommunication. The deployment utility is described in Deployment.