> Overview of Using JNDI With Third-Party Naming/Directory Services
> TIBCO Enterprise Message Service supports the storage (binding) and retrieval (look-up) of ConnectionFactories and Destinations in third-party naming or directory services. Examples of such services are an LDAP server, the RMI registry, or the file system.

> | Third-party naming or directory servers are separate products that must be installed and set up independently of TIBCO Enterprise Message Service. This is usually done by a system administrator.

> To use a third-party directory service, you must have a JNDI provider for that specific type of service. A JNDI provider presents a common API to the service regardless of the service type or service vendor, much like a JDBC driver presents a common API on top of various vendors’ databases.
> The Java 2 SDK, contains JNDI providers for LDAP and RMI registry, among others. A JNDI provider for the file system can be downloaded from the JNDI home page at java.sun.com.
> From a client perspective, looking up administered objects is accomplished in virtually the same way regardless of whether the object is in a third-party naming/directory service or in the TIBCO Enterprise Message Service server. For third-party services, the only prerequisite is that the objects must have previously been stored there. That is, the object must be bound to a name in the context of that service. This is usually a task performed by a system administrator.

> | There is no automatic synchronization of administered objects between the TIBCO Enterprise Message Service server and any foreign naming/directory service. Keeping the two synchronized is the responsibility of the system administrator.

Copyright © TIBCO Software Inc. All Rights Reserved.