JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Directory Server Enterprise Edition Developer's Guide 11 g Release 1 (
search filter icon
search icon

Document Information


Part I Directory Server Plug-In API Guide

1.  Before You Start Writing Plug-Ins

2.  Changes to the Plug-In API Since Directory Server 5.2

3.  Getting Started With Directory Server Plug-Ins

4.  Working With Entries Using Plug-Ins

5.  Extending Client Request Handling Using Plug-Ins

6.  Handling Authentication Using Plug-Ins

7.  Performing Internal Operations With Plug-Ins

8.  Writing Entry Store and Entry Fetch Plug-Ins

9.  Writing Extended Operation Plug-Ins

10.  Writing Matching Rule Plug-Ins

11.  Writing Password Storage Scheme Plug-Ins

12.  Writing Password Quality Check Plug-Ins

13.  Writing Computed Attribute Plug-Ins

Part II Directory Server Plug-In API Reference

14.  Data Type and Structure Reference

15.  Function Reference, Part I

16.  Function Reference, Part II

17.  Parameter Block Reference

A.  NameFinder Application

Prerequisite Software

Deploying NameFinder

To Deploy on Application Server

To Deploy on Web Server

Configuring NameFinder to Access Your Directory

To Configure Access When Using Application Server

To Configure Access When Using Web Server

Customizing NameFinder

Connection Properties

Search Attribute Properties

Other Properties


To 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/ 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/ 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/ file to allow the application to access the directory, and then save your changes.

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

    • 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|

    • 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/ 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.