|
JNDI overview, Part 4: the Doc-u-Matic, a JNDI application
You've read each lesson and learned the material -- now it's time to play. In order to demonstrate clearly the strength of JNDI, Todd Sundsted takes you on a tour of Doc-u-Matic, a JNDI-enabled document publication and distribution infrastructure. You'll see how a naming and directory service, combined with JNDI's ability to store Java objects, leads to simpler -- yet more powerful -- distributed applications
|
|
LDAP and JNDI: Together forever
In this article Sameer Tyagi takes a look at the Java Naming and Directory Interface (JNDI), explaining how you can manipulate Java objects on an LDAP server. He'll show you examples that demonstrate how you can store objects, search for objects, see event handling in LDAP, and much more
|
|
|
JAVA NAMING AND DIRECTORY INTERFACETM (JNDI)
The Java Naming and Directory InterfaceTM (JNDI) is a standard extension to the JavaTM platform, providing Java technology-enabled applications with a unified interface to multiple naming and directory services in the enterprise. As part of the Java Enterprise API set, JNDI enables seamless connectivity to heterogeneous enterprise naming and directory services. Developers can now build powerful and portable directory-enabled applications using this industry standard.
|
|
JAVA NAMING AND DIRECTORY INTERFACETM (JNDI)
The Java Naming and Directory InterfaceTM (JNDI) is a standard extension to the JavaTM platform, providing Java technology-enabled applications with a unified interface to multiple naming and directory services in the enterprise. As part of the Java Enterprise API set, JNDI enables seamless connectivity to heterogeneous enterprise naming and directory services. Developers can now build powerful and portable directory-enabled applications using this industry standard.
|
|
The JNDI Tutorial
The Java Naming and Directory InterfaceTM (JNDI) is an application programming interface (API) that provides naming and directory functionality to applications written using the JavaTM 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 overview, Part 1: An introduction to naming services
The Java Naming and Directory InterfaceTM (JNDI) is a standard extension to the JavaTM platform, providing Java technology-enabled applications with a unified interface to multiple naming and directory services in the enterprise. As part of the Java Enterprise API set, JNDI enables seamless connectivity to heterogeneous enterprise naming and directory services. Developers can now build powerful and portable directory-enabled applications using this industry standard.
|
|
Use JNDI to share objects between different virtual machines
Imagine the following: Process A on machine B puts an object into a Hashtable. Now, a separate process C on a different machine D can access that object from its own local copy of the Hashtable -- even after process A terminates and the virtual machine unloads! Now imagine all this is achieved without the use of RMI, and without involving an ORB, CORBA, EJB, or a database. What's the secret? The Java Naming and Directory Interface (JNDI). This month's tool is the JNDIHashtable -- which, as its name reveals, uses JNDI to do its thing
|
|
Java Naming and Directory Interface (JNDI) FAQ
The Java Naming and Directory Interface (JNDI) is an application programming interface (API) for accessing different kinds of naming and directory services. JNDI is not specific to a particular naming or directory service, it can be used to access many different kinds of systems including file systems; distributed objects systems like CORBA, Java RMI, and EJB; and directory services like LDAP, Novell NetWare, and NIS+.
|
|
Using WebLogic JNDI
In the enterprise, naming and directory services -- the ability of your application to locate an object or service that may be anywhere on the network -- play an important part in building a distributed application. Particularly in a clustered environment, where clients may connect arbitrarily to any machine, the environment must have a naming service that can be depended upon to locate any service object requested no matter its physical location.
|
|
JNDI overview, Part 2: An introduction to directory services
As applications become more distributed, the efficient management and distribution of the information upon which they depend becomes more and more of a problem. Directory services such as LDAP (the Lightweight Directory Access Protocol) address this problem. For Java applications, the Java Naming and Directory Interface (JNDI) provides a generic interface to LDAP and other directory services. This month, Todd Sundsted introduces you to JNDI directory services.
|
|
Making Enterprise Connections with JNDI and LDAP
One of the advents in the enterprise technology space in the last few years has been the introduction of Lightweight Directory Access Protocol (LDAP) directory servers. Directory servers are designed to provide a standardized mechanism for storing, retrieving, and searching for information about entities in the enterprise: people, departments, organizations, etc. It is, in other words, a specialized type of database.
|
|
Using the JNDI Service Provider
The Java Naming and Directory Interface (JNDI) allows Java applications to use a single set of methods to access multiple naming and directory services such as LDAP and NIS. JNDI was developed by the JavaSoft division of Sun Microsystems along with several industry partners, including Netscape.
|
|
Understanding JNDI
One of the advents in the enterprise technology space in the last few years has been the introduction of Lightweight Directory Access Protocol (LDAP) directory servers. Directory servers are designed to provide a standardized mechanism for storing, retrieving, and searching for information about entities in the enterprise: people, departments, organizations, etc. It is, in other words, a specialized type of database.
|
|
JNDI FREQUENTLY ASKED QUESTIONS
Any JavaTM application that needs to access information about users, machines, networks, and services. User information includes security credentials, phone numbers, electronic and postal mail addresses, and application preferences. Machine information includes network addresses, machine configurations, etc. In addition, any Java application that needs to either export objects or access objects exported by other applications and services. Examples include printers, calendars, and networked file systems.
|
|
COS Naming Service Provider for the
Java Naming and Directory InterfaceTM (JNDI)
The Common Object Services (COS) Name Server is the name server for storing Common Object Request Broker Architecture (CORBA) object references. It can be accessed from CORBA applications by using the COS Naming package (org.omg.CORBA.CosNaming).
|
|
The Use of JNDI in Enterprise Java APIs
One of the advents in the enterprise technology space in the last few years has been the introduction of Lightweight Directory Access Protocol (LDAP) directory servers. Directory servers are designed to provide a standardized mechanism for storing, retrieving, and searching for information about entities in the enterprise: people, departments, organizations, etc. It is, in other words, a specialized type of database.
|
|
JNDI DOCUMENTATION
The Java Naming and Directory InterfaceTM (JNDI) 1.2 is a major new upgrade release that adds new functionality to the basic naming and directory support offered in the 1.1.x releases. New features include event notification, and LDAPv3 extensions and controls. This release contains valuable contributions from the following companies: Netscape, Novell, SCO, Sun, BEA.
|
|
Archives of JNDI-INTEREST@JAVA.SUN.COM
A mailing list for discussing Java Naming and Directory Interface (JNDI)
|
|
JNDI 1.2 Specification: Package javax.naming.spi
Provides the means for dynamically plugging in support for accessing naming and directory services through the javax.naming and related packages.
|
|
List archives at JAVA.SUN.COM
|
|
The Java Naming and Directory Interface (JNDI)
The Java Naming and Directory InterfaceTM (JNDI) 1.2 is a major new upgrade release that adds new functionality to the basic naming and directory support offered in the 1.1.x releases. New features include event notification, and LDAPv3 extensions and controls. This release contains valuable contributions from the following companies: Netscape, Novell, SCO, Sun, BEA.
|
|
LDAP and JNDI: Together forever
In this article Sameer Tyagi takes a look at the Java Naming and Directory Interface (JNDI), explaining how you can manipulate Java objects on an LDAP server. He'll show you examples that demonstrate how you can store objects, search for objects, see event handling in LDAP, and much more
|
|
Java Naming and Directory InterfaceTM
The Java Naming and Directory InterfaceTM (JNDI) provides naming and directory functionality to applications written in the JavaTM programming language. It is designed to be independent of any specific naming or directory service implementation. Thus a variety of services--new, emerging, and already deployed ones--can be accessed in a common way.
|
|
JNDI overview, Part 3: Advanced JNDI
A JNDI service can be much more than a computerized card catalog. JNDI's object-storage capabilities allow it to play the role of resource administrator in your distributed applications and to provide simple, manageable object persistence. In recognition of its potential, the architects of key Java technologies such as JDBC and EJB built JNDI into their specifications. This month Todd Sundsted shows you how to store objects in a JNDI service
|