weblogic and JNDI configuration?

Posted on 2008-10-26
Medium Priority
Last Modified: 2013-12-10
Hello experts,
Can weblogic server runs without JNDI properties configured? Assume it is in a single server environment. What about in a clustered one then? When I deploy a war, does weblogic server automatically register the war as a object in JNDI tree managed by JMX? what would happen if I have a websphere server running on the same box and I deploy the same war to it?
Do I configure the JNDI name or the system would do that avoiding name conflict?

any response would be highly appreciated.
Question by:DW258
LVL 10

Accepted Solution

rajesh_bala earned 750 total points
ID: 22827430

When you start weblogic, it internally starts its own JNDI service. You dont need to manually create anything there.

When you deploy the war or ear, depending on the requirement JNDI is contacted and registered. For instance, if it is an EJB, it is registered with JNDI. This happens when the application is started from weblogic console (i.e, when you deploy the war/ear, weblogic puts it in prepared state. You can choose to start this application and then it gets changed to "running" state).

You can have websphere running on the same box. But it would be running on a different port than weblogic. So ideally your weblogic LDAP wont be affected. You can have more than one JNDI in the same box since the port numbers of weblogic and websphere would be different.

Hope this helps.


Expert Comment

ID: 22977025
The jndi.properties is actually required by the JNDI clients to bind to the jndi tree. This properties file contains the provider details - url, factory etc. This would be a typical single node configuration.

If you need a cluster, you would choose a different strategy for deploying your naming service depending upon your cluster type. If its a heterogenous cluster (different applications on seperate nodes), you would be better off running one global jndi service with a master-slave failover configuration. If you have a homogenous cluster (same stateless application on seperate nodes), you may choose to use the normal jndi service, as you don't care, which node services the request.

When you have a Websphere and Weblogic running on the same system, and if you choose to use their own jndi services, it would depend upon your client whom it wants to connect to (depending upon the provider url and factory specified ).

If you want to make a call from a client in weblogic to websphere, you would be better off, running a single jndi service (either wls's or websphere's) - This configuration may get a bit involved.
What do you want to achieve?

Author Closing Comment

ID: 31510126
thanks for the answer. I split the points to both of the contributors.

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip is around source server preparation. No migration is an easy migration, there is a…
Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
The viewer will learn how to implement Singleton Design Pattern in Java.
This tutorial covers a practical example of lazy loading technique and early loading technique in a Singleton Design Pattern.

616 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question