More about MQ Listener data instances
 

EAR versus WAR deployment

MQ listeners operations depend on whether PRPC is deployed as an Enterprise application (EAR file) or a Web application (WAR file). See PDN article Using MQ and JMS Services with Enterprise Application deployment, regarding EAR deployment and polling.

When and how MQ listeners run

Three settings affect how MQ listener requestors run. They control whether the listeners can run, when the listeners start, and where the listeners can run:

1. Whether — Controlled by the Blocked field on the Properties tab of this form.
2. When — Controlled by the initServices/initMQ entry in the prconfig.xml file or Dynamic System Settings. (enabled by default)
3. Where — Controlled by the node list on the Properties tab of this form.

Controlling whether listeners start

The Blocked checkbox on the Properties tab determines whether the listener requestors defined by this MQ Listener data instance start. If this box is cleared, these listeners start when PRPC starts (on eligible nodes). You can also stop and restart them using the Listener Management menu in the System Management application.

If the Blocked box is selected, they do not start when a PRPC node starts and you cannot start them in the System Management application until you clear the Blocked option and save the listener instance.

Controlling when listeners start

The prconfig.xml file or Dynamic System Settings control when MQ listeners start. To cause unblocked MQ listeners to start when PRPC starts, edit this file to add or update the initServices/initMQ setting:

<env name="initServices/initMQ" value="true"/>

As an alternative to the prconfig.xml file, you can use Dynamic System Settings to configure your application.
See How to create or update a prconfig setting.

If this entry is not present in the file, or the value is not set to "true","y" or "yes", you can start unblocked MQ listeners only from System Management application. LACOD 6/18/03

Controlling where listeners run

The options listed in the Start Option property on the on the Properties tab determine where the listener starts. The following options are available.

• Run on all nodes — The listener is run on all nodes — all servers in a cluster.
• Node based startup — The listener is started only on specified nodes.
• Host based startup — The listener is started on a specified number of nodes on specific servers within the cluster.

Remote logging

C-606 Use the remote logging feature to debug MQ listeners:

• On the Properties tab, identify a workstation that will receive logging output.
• Use the System Management application to start the listener.
• Optionally, use the System Management application to filter which console output messages are sent to the server.

	connector, listener, prconfig.xml file, remote logging, WebSphere MQ
	About the System Management application About Connect MQ rules About MQ Server data instances How to install and use remote logging

About MQ Listener data instances