MQ Listeners are available only when PRPC is deployed as an Web Application. If it is deployed as Enterprise application then listener is managed by the containers. As per my knowledge you have to operate it thought application server console. We are using Pega 7.1.9 on websphere and all our listener end points are managed through WasAdmin portal.
Usage of Listener ports is obsolete when we have activation spec configured.
I believe you have used the Thunder script to do the Activation Spec configurations.
Activation spec does have PAUSE/RESUME options to administer the listeners.
Problem statements :
1) As per the information that I have obtained so far,JMS MDB listeners can only be managed using the Activation Spec (via PAUSE/RESUME options).Could you please suggest if you are aware of any other options.
2) Although we are able to process the message successfully using JMS MDB listeners,we could find the listeners listed out in the SMA but couldnt get any listeners information from them.
1) I believe Pause/Resume of Act.Spec from WASAdmin is the only option to manage the MDB listener status.
2)What do you mean by common scenario ? We were able to find the listeners listed out in the SMA for one listener and could get listeners information from them.But after configuring two additional listeners,we couldnt find listeners information for any of the listeners listed out in the SMA.
I have recently created a MDB listener and I can see it in SMA listener dropdown. But I had to restart the nodes with a cleared cache to see them. By theory it should appear if the JMS MDB Listener instance is present in Pega application and listener is configured properly.
Common Scenario - > I mean to say it is a known fact that MDB listener is having problem to operate through SMA.