InitialContext information for lookup

Hi,
Where the InitialContext information about EJB/Servlet be stored for JNDI Services. I am using DB2 databases. But i could not find it.
Is it a hidden value pairs. I have used Websphere as well as weblogic servers.
Thanks & Regards,
M.S. Raman

Hi, WebLogic puts the JNDI tree in memory, and replicate it on a cluster environment, I can�t tell about websphere.

Oh! I forgot to mention:
To view the objects in the WebLogic Server JNDI tree for a specific server, do the following:
Right-click the server node in the left pane. This displays a pop-up menu.
Select JNDI Tree. The JNDI tree for this server displays in the right pane.

You can also use the admin command:
$\>java weblogic.Admin LIST -password password -username username

Hi,
Thanks Marcos Maia. Is there any relationships with JNDI and Database(As you said it be stored in the memory).
Because in my case i am using two different databases for Websphere TestEnvironment Control Centre for persistence Manager(In Visual Age, which starts the naming server in the visual age). Here in my case i am using two databases(x,y of DB2 seperately i.e in case 1 i am usign x and case 2 i am using y, but it contains only the values that are created during the corresponding period). Both JNDI values are different. So i have a doubt that it may be stored in the memory but having certain relationship with the database. Please clarify my doubts.
Regards,
M.S.Raman.

Originally posted by Marcos Maia:
Oh! I forgot to mention:
To view the objects in the WebLogic Server JNDI tree for a specific server, do the following:
Right-click the server node in the left pane. This displays a pop-up menu.
Select JNDI Tree. The JNDI tree for this server displays in the right pane.

Hi,
I think I didn�t get exactly what you wanna know!!!
So I�ll try to talk a little about JNDI.
The Java Naming and Directory Interface (JNDI) is an application programming interface (API) that provides naming and directory functionality to applications written using the Java programming language. It is defined to be independent of any specific directory service implementation. Thus a variety of directories--new, emerging, and already deployed--can be accessed in a common way.
JNDI is an API wich provides naming
and directory services and as this, it just provides a simpler way to locate services on machines/network, so what happens is that when you create the DataSource you provide a JNDI name who references this service and than you can "lookup" this service using this name, in weblogic when you create a service like this it gets registered in the config.xml file under: %WL_HOME%\config\%DOMAIN_NAME% there you will find the registered JNDI name for the service, than when you start the server it reads the config.xml file and stores the jndi name in memory to get a better performance, some other servers may work different, as this is a WebLogic implementation.
[ March 08, 2002: Message edited by: Marcos Maia ]
[ March 08, 2002: Message edited by: Marcos Maia ]