Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What is the purpose of listener in WebSphere MQ?

When I go to my WebSphere MQ explorer, and connect to a remote queue manager and go to --> Advanced --> Listeners, I do not see any listeners defined. But I am able to create a remote JMS client, connect to this queue manager by using a channel connection and publish a message to a topic.

So what is the purpose of listeners? In my case, things are working fine without listeners.

like image 368
Victor Avatar asked Aug 01 '12 17:08

Victor


People also ask

What does MQ listener do?

A listener is an IBM® MQ process that listens for connections to the queue manager. Each listener object in MQ Explorer represents a listener process; however, if you start a listener process from the command line, the listener is not represented by a listener object in MQ Explorer.

What is queue listener?

A queue listener is an application that reads and processes these queued messages. Because the Service Bus messages are stored in a queue, a listener doesn't have to be actively listening for messages to be received in the queue.

How do I know if MQ listener is running?

The START LISTENER command starts the listener. You also have STOP LISTENER MQSC command to stop the listener. Once you create and start the listener, you can then issue DISPLAY LSSTATUS command to display the listener status.

How do I start a listener in MQ?

The Start MQ Listener (STRMQMLSR) command starts an MQ TCP/IP listener. This command is valid for TCP/IP transmission protocols only. You can specify either a listener object or specific listener attributes.


1 Answers

WebSphere MQ listeners are what accepts remote connections and start inbound channels. Modern queue managers will almost always have listeners defined but it is also possible to specify a default port for the QMgr to listen on without actually defining a listener. This is unusual, though. For older versions of MQ it was common to use inetd to start channels. This method doesn't use a listener.

So rest assured that something on your QMgr is listening for connections. Since you are not seeing it there are three likely possibilities:

  • The listener name starts with SYSTEM. and your Explorer view is set to filter SYSTEM objects.
  • The default port has been specified in the qm.ini file
  • You have a really old QMgr using inetd

By the way, go get a new version of WMQ Explorer. Since you have an Advanced --> Listeners you must have an old version. Download from SupportPac MS0T.

like image 196
T.Rob Avatar answered Nov 09 '22 02:11

T.Rob