The JNDI Service Provider
A common best practice for J2EE application development is using the Java Naming and Directory Interface (JNDI) to serve as an abstraction layer on top of naming and directory services. This allows you to write your business logic and use JNDI to serve as a proxy for naming and directory operations, which a JNDI LDAP service provider then passes on to the LDAP server.
The Netscape Directory Server SDK ships with a JNDI LDAP service provider. You can generate the JNDI LDAP Service Provider JAR (ldapsp.jar) from source using the ant target
dist-jndi. For more information about the API and how to use it, read Chapter 15 of the “Netscape Directory SDK for Java Programmer’s Guide”.
Great LDAP Servers Never Die…
The Netscape Directory Server is a great LDAP server that, although no longer in production, is reliable enough for many large enterprises to use. If you find yourself needing to access this server programmatically via Java, you will likely need to build the SDK from source. This article has shown you the steps involved in building the SDK in a cross-platform way, as well as provided some tips on using the SDK’s API to access the server.
I encourage you to download and study the source code and make use of the many resources I identified in the Related Resources section. Enjoy!