Question4Replies1990Views Gooner007 Member since 2010 15 posts Tata Consultancy Services Posted: 4 years agoLast activity: 4 years 2 months ago Closed Solved JMS MDB ListenerHi,We have set a Queue,Queue Connection Factories and activation Specs in our environment. Now We are trying to set up the listener and I have the below questions1. Under MDB Destination Properties , I am not able to see the JNDI Name which we used to set up the Queue . Why? Should I add the JNDI Name anywhere else 2.I gave the JNDI Name manually and tried "Test Connectivity". I am receiving the error "Object at JNDI node '<JNDI Name>' doesn't implement javax.jms.ConnectionFactory". Any idea why?3. Test Connectivity button is enabled only when we select "Message" or "Listener" in Reply to connection . If my listener is not using any reply is there a way to test connectivity ?Any help is greatly appreciated Data Integration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Accepted Solution Posted: 4 years agoranjr PEGA replied to Gooner007The process require lot of steps. I have recently set up the environment at my end. I used WAS 8.5 and PRPC 7.2. Coming to your point, have you made required changes in the ejb-jar.xml and ibm-binding.xml? Have you created service integration bus as well? To connect you need to have a jndi server. Are you able to connect from prpc via jndi server? If yes, are you able to use jndi browser to see your CF and queue? I have a document which is in a crude form but will give a idea on the setup. Let me know if that helps. If not, I will try to prepare a better formated document for you. Posted: 4 years agoGooner007 Tata Consultancy Services replied to ranjrHi Rajeev, Thank you for the explanation. And Yes i did all the steps which you mentioned. But Unfortunately there was a mistake in the Ejb-Jar.xml which caused the issue. Corrected and it worked fine. This document will definetly helpful for the new set up.! Posted: 4 years agoKevinZheng_GCS PEGA replied to Gooner007Arul, For Pega 7.1.8+, the MDB deployment has been greatly simplied without having to manipulating files yourself. Here is the link you should follow: https://pdn.pega.com/deploying-jms-message-driven-bean-mdb-represents-j… Kevin Posted: 4 years agopavankumart6226 Accenture replied to ranjrThanks for the document.