Discussion

JNDI-Server lookup doesn't work

Hi together, I'd like to use the Connector Accelerator to create necessary rules for a remote EJB. As prerequisite, a JNDI-Server needs to be created. So far, Initial Context Factory and Provider URL are set up correctly, since the Provider URL works fine in my Java-IDE. When starting the Connector Accelerator, setting the according values and selecting the created JNDI-Server, it doesn't find any EJBs. How can I really test / debug, if Pega really connects to the Provider URL. I already made some dummy tests and found out, that Pega doesn't connect to the Provider when clicking on "Test Connectivity" of the JDNI-Server. We are using PRPC 4.2SP6 on Websphere 5.1 running on Solaris. Thanks for help, best regards, Michael Mey

***Updated by moderator: Marissa to close post***

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

April 28, 2008 - 12:48pm

Any stack trace from catalina.log would be helpful to analyze the cause.

April 28, 2008 - 2:12pm

I would confirm that PRPC is able to interrogate the JNDI tree using the "Rule-Connect-EJB.getContextList" Activity. This Activity excepts a parameter of JNDI Server (Data-Admin-Connect-JNDIServer). The result of this activity displays the contents of a String Buffer that should contain the results of the EJB Bindings.