Listeners

The deployment process (see The deployment utility) automatically creates wrapper scripts in the generated/server directory that set up and invoke the listener. Scripts are generated to start the listener as a WebSphere MQ service or by triggering. We can also start a listener manually.

The scripts to start listeners are named as follows:

startWMQJListener.sh

to start a Java listener under UNIX

startWMQJListener.cmd

to start a Java listener under Windows

startWMQNListener.cmd

to start a .NET listener under Windows

The scripts to define and start listeners as a WebSphere MQ service are named as follows:

defineWMQJListener.sh

to define and start a Java listener as a service under UNIX

defineWMQJListener.cmd

to define and start a Java listener as a service under Windows

defineWMQNListener.cmd

to define and start a .NET listener as a service under Windows

These invoke the start scripts described above

.

The deployment process also generates scripts to stop listeners, named as follows:

endWMQJListener.sh

to end a Java listener under UNIX

endWMQJListener.cmd

to end a Java listener under Windows

endWMQNListener.cmd

to end a .NET listener under Windows