Question
Accenture
IN
Last activity: 23 Jan 2017 3:01 EST
How to connect to JMS Provider on webMethods Universal Messaging?
We are on Pega 7.2.1 on JBoss app server.
We are integrating with an application which is on webMethods (webMethods - Wikipedia) .
The idea is Pega (acting as JMS client) to read the queues hosted on remote JMS queue using Service-JMS. webMethods team hosts a queue on a JMS Provider.
JMS Provider: webMethods Universal Messaging
Initial Context Factory: javax.jms.ConnectionFactory
Other details of JNDI Details, Queue Name, Connection factory are also shared.
- How to connect to this JMS Provider?
- What are the settings for JNDI server configuration?
- Any other actions to be taken care in our application server?
I didn't find any documentation on the settings of JNDI Server if the JMS provider is other than JBoss, IBM Webspher, Oracle WebLogic.
We tried to provide the initial context factory into JNDI Server and try the simple way. Attached is the error thrown during test connection.
Is this "only" due to missing class (i.e. initial context factory) in pega 7 class path?
Accepted Solution
Accenture
IN
Issue is solved. Couple of changes done.
1. Initial context factory is changed to com.pcbsys.nirvana.nSpace.NiravanaContextFactory
2. webMethods specific JCA resource adaptor is to be created in JBoss application server level. This resource adaptor needs properties specific like connection factory jndi name, JNDI Properties(pointing to right initial context factory), provider url to the target system.
This is basically for prpc to understand the initial context factory class mentioned and locate it appropriately. All the app server level changes can easily be done through JBoss admin console.
At PRPC, initial context factory and provider url are used in JNDI Server rule instance.
JPMorgan Chase & Company
US
Hi Thrinath,
Please check below pdn link, I hope it might helpful
Accenture
IN
Hi, this article you posted is more about the steps to configure MDB listener i.e. generating deployment descriptors & modifying it to app specific needs.
My issue is during the "set up" of JNDI server i.e. the 1st step of over config.
Thank you.
Virtusa IT Consulting
AE
Have you gone through the logs? Check the logs for the timestamp when it was reproduced, you will find the root cause there for this exception.
J P Morgan
IN
You will have to create a JMS Bridge between your application server and webmethods.
You can refer the documentation of the respective application server wrt. the bridge configuration.
Once they bridge is configured correctly, then you can use the queue/topic.
Please let us know if you face issues during the configuration.
Regards,
Faisal
Pegasystems Inc.
IN
Hi,
Please use the initial context factory as
com.webmethods.jms.naming.WmJmsNamingCtxFactory
and provide the provoder url and test connectivity from jndi server instance and let us know if you face any issue.
Thanks,
Accenture
IN
Hi, tried with "com.webmethods.jms.naming.WmJmsNamingCtxFactory" initial context factory. Now, i face a different error.
There is a SA around this error, but its specific to jboss as the JMS provider.
SA-21971@ https://pdn.pega.com/support-articles/test-connectivity-fails-jndi-server-instance
Attached is the error. Are there any jars to be provided by JMS provider & deployed in our app server to get this working?
Thanks
Accepted Solution
Accenture
IN
Issue is solved. Couple of changes done.
1. Initial context factory is changed to com.pcbsys.nirvana.nSpace.NiravanaContextFactory
2. webMethods specific JCA resource adaptor is to be created in JBoss application server level. This resource adaptor needs properties specific like connection factory jndi name, JNDI Properties(pointing to right initial context factory), provider url to the target system.
This is basically for prpc to understand the initial context factory class mentioned and locate it appropriately. All the app server level changes can easily be done through JBoss admin console.
At PRPC, initial context factory and provider url are used in JNDI Server rule instance.
Pegasystems Inc.
IN
Hi Thrinath,
Thank you for taking time to update the thread with the resolution steps. Its a very helpful practice to share the resolution with the community for all the users who might enounter the same question in future.
~Vidyaranjan A V | Community Moderator | PegaProductSupport | Pegasystems Inc.