Sun Java System Directory Server Enterprise Edition 6.1 Developer's Guide

Configuring NameFinder to Access Your Directory

You can configure NameFinder to access your directory on Application Server or on Web Server.

ProcedureTo Configure Access When Using Application Server

After deploying the NameFinder application, Application Server creates a WEB-INF/ container directory that holds NameFinder files. The location of this directory depends on where you installed the Application Server instance.

You must specify in the WEB-INF/classes/NameFinder.properties file how to access the directory that holds the data to retrieve.

  1. If necessary, determine the path where you deployed the NameFinder application with the Application Server browser-based interface.

    The WEB-INF/classes/NameFinder.properties file is located in that directory.

  2. Become a user, such as superuser, with access to edit the file.

  3. Adjust properties in the WEB-INF/classes/NameFinder.properties file to allow the application to access the directory, and then save your changes.

    The NameFinder.properties file is a Java properties file. Everything in the file is case sensitive. Adjust at least the following lines:

    NameFinder.ldapBase=baseDN
    NameFinder.ldapServers=serverList
    NameFinder.ldapVersion=3
    NameFinder.ldapPort=ldapPort
    NameFinder.ldapUser=bindDN
    NameFinder.ldapPasswd=bindPassword
    
    • baseDN is the base DN for people's entries in your organization, such as ou=people,dc=example,dc=com.

    • serverList is a | separated list of directory servers, such as directory|backup-directory|ext-directory.example.com.

    • ldapPort is the port number on which the servers listen for LDAP requests, by default 389.

    • bindDN is the DN used to authenticate.

      Do not enclose the bind DN in quotes.

    • bindPassword is the password used to authenticate.

    For hints regarding what you can adjust, read the comments in the WEB-INF/classes/sample.properties file.

  4. In the Application Server browser-based interface, apply changes on the server instance by pressing the Apply Changes button.

    After applying changes, you can begin using the NameFinder application to look up contact and organizational information.

  5. Verify that the NameFinder application works by searching for a known user, such as yourself, using the browser-based interface.

    After you are satisfied that the NameFinder application works, you can choose to customize the application for your organization.

ProcedureTo Configure Access When Using Web Server

After deploying the NameFinder application, Web Server creates a WEB-INF/ container directory that holds NameFinder files. The location of this directory depends on where you installed the Web Server instance.

You must specify in the WEB-INF/classes/NameFinder.properties file how to access the directory that holds the data to retrieve.

  1. If necessary, determine the path where you deployed the NameFinder application with the Web Server browser-based interface.

    The WEB-INF/classes/NameFinder.properties file is located in that directory.

  2. Become a user, such as superuser, with access to edit the file.

  3. Adjust properties in the WEB-INF/classes/NameFinder.properties file to allow the application to access the directory, and then save your changes.

    The NameFinder.properties file is a Java properties file. Everything in the file is case sensitive. Adjust at least the following lines:

    NameFinder.ldapBase=baseDN
    NameFinder.ldapServers=serverList
    NameFinder.ldapVersion=3
    NameFinder.ldapPort=ldapPort
    NameFinder.ldapUser=bindDN
    NameFinder.ldapPasswd=bindPassword
    
    • baseDN is the base DN for people's entries in your organization, such as ou=people,dc=example,dc=com.

    • serverList is a | separated list of directory servers, such as directory|backup-directory|ext-directory.example.com.

    • ldapPort is the port number on which the servers listen for LDAP requests, by default 389.

    • bindDN is the DN used to authenticate.

      Do not enclose the bind DN in quotes.

    • bindPassword is the password used to authenticate.

    For hints regarding what you can adjust, read the comments in the WEB-INF/classes/sample.properties file.

    You must restart Web Server for the changes to take effect.

  4. Return to the Server Manager page in the Web Server browser-based interface to turn the server off, then on again.

    At this point, you can begin using the NameFinder application to look up contact and organizational information.

  5. Verify that the NameFinder application works by searching for a known user, such as yourself, using the browser-based interface.

    After you are satisfied that the NameFinder application works, you can choose to customize the application for your organization.