After deploying the
Web Server creates a WEB-INF/ container directory that
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.
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.
Become a user, such as superuser, with access to edit the file.
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.
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
to look up contact and organizational information.
Verify that the
works by searching for a known user, such as yourself, using the browser-based
After you are satisfied that the
works, you can choose to customize the application for your organization.