The sample use cases need the following components:

The sample data referenced can be found in <varoot>/samples/ldap/exampleData.ldif where varoot is the root directory of the product installation. (See Installation Guide for further information).

The LDAP implementation is found in the LDAP Support feature. The Smalltalk sample use cases are in a separate configuration map named ENVY/Image LDAP Examples. The EsLdapExamples class implements the sample use cases.

To set up the example

That’s it. You are ready to run the LDAP samples.

Open a hierarchy browser on EsLdapExamples and look at the class methods. Many sample use cases of LDAP are in these Example methods. The pattern in each use case is to create an LdapSession and bind it to the server before accessing the data provided by the server and then to unbind the session from the server at the end of the example.

Data, in the form of LdapEntry instances, may be accessed as part of a search or from retrieving child entries from their parent LdapEntry (or parent LdapEntry from its child). New data in the expressed as LdapEntry instances can be presented to the session for incorporation into the LDAP directory of information. Likewise, entries can be modified or entirely deleted from the server's data.

All these use cases are represented in the EsLdapExamples.

The VAST LDAP code has been tested with both the Window LDAP dll (wldap32) and on Linux with the dll from openLdap.org (libldap). The logical name LDAP_LIB must reference one of these dlls must be in the abt.ini file under the [PlatformLibrary Name Mappings] stanza. For instance, here is the setting for Windows:

The abt.ini file also contains the stanza [ldap]. Depending on how the LDAP server is set up, hostName and portNumber may need to change for a VAST application using the LDAP feature and making requests to a server on a different machine or over a different port. Here are the hostName and portNumber set appropriately for the example.