The Java agent

The search form

Testing your application

Related links:
Building real-time access to an LDAP directory server from your Notes application sidebar

Agent FAQ

JNDI Web site

JNDI Tutorial

Get the PDF:
(269 KB)

• Lotus Domino 5.0.9a and later on Windows 2000
• Lotus Domino Designer 5.0.9a and later on Windows 2000
• Lotus Notes client 5.0.9a and later on Windows 2000
• Directory Server: OS/400 V5R1 Directory Services (option 32)

• Jndi.jar
• Ldap.jar
• Providerutil.jar (Note that this JAR file exists in more than one zip file, so it doesn’t matter where you get the JAR file from.)

1. Copy the JAR files to your Domino server. If you have Windows 2000, copy the three JAR files to the Java directory on your server. If you have an iSeries (OS/400) server, copy these JAR files to an iSeries IFS directory using FTP with the binary option or mapping a local drive on your PC to the Domino\data directory on your iSeries server. Change the ownership of these files to QNOTES, and update the authority for these objects by adding QSYS with *RWX access.
2. Update your Domino server Notes.ini file by adding the JavaUserClasses parameter and its value (see example for Domino Designer). On the iSeries, use a colon as a separator between the jar files, for example:
   
   JavaUserClasses=/home/myjarfiles/lib/jndi.jar:/home/myjarfiles/lib/ldap.jar:
   /home/myjarfiles/lib/providerutil.jar
   
3. Restart your Domino server. You should see the completion message:
   
   JVM: Java Virtual Machine initialized

1. You perform a search using the LDAP Search form. This form has several fields in it. First, you choose Person or Group. If you choose Person, you type the name, select an attribute from the list, and click the Search LDAP button. If you choose Group, you type the group name and exit the field.
2. The Search LDAP button or the Exiting event saves the form to a back-end document and calls the Java agent, LDAPSearchWithFilter, by passing the doc.NoteID value as a parameter.
3. The agent connects to the LDAP server and performs the search.
4. The agent updates the back-end document with the search results (actual data or error messages). For simplicity, the assumption used in the code is that only one entry is returned at a time. However, each entry can have more than one attribute value.
5. The LDAP Search form reopens the back-end document by its doc.NoteID value and performs the necessary string manipulations before displaying the results.

• When should this agent run: Manually from actions menu
• Which document(s) should it act on: Run once (@Commands may be used)
• Type: Java

public void NotesMain() {
try {
Database _db;
Document _doc;
Session session = getSession();
AgentContext agentContext = session.getAgentContext();

_db = agentContext.getCurrentDatabase();

Agent ag1 = agentContext.getCurrentAgent();
String paramid = ag1.getParameterDocID();
Document doc = _db.getDocumentByID(paramid);

String searchCN = doc.getItemValueString("SearchCN");
String searchAttr = doc.getItemValueString("SearchAttr");

Hashtable env = new Hashtable(11);
env.put(Context.INITIAL_CONTEXT_FACTORY, com.sun.jndi.ldap.LdapCtxFactory");
env.put(Context.PROVIDER_URL, "ldap://myldap.mycompany.com:389/ou=myou, o=myorg, c=us");
If your Directory server requires authentication, add the following lines in your code (check with your Directory server administrator for the correct ID and password):
env.put(Context.SECURITY_PRINCIPAL, “cn=Administrator”);
env.put(Context.SECURITY_CREDENTIALS, “thepassword”);

DirContext ctx = new InitialDirContext(env);

String[] attrIDs = {searchAttr};
SearchControls ctls = new SearchControls();
ctls.setReturningAttributes(attrIDs);

// Specify the search filter
String filter = "(|(cn="+searchCN+")(uid="+searchCN+"))";

// Search for objects using the above filter
NamingEnumeration answer = ctx.search("", filter, ctls);

try {
if (enum.hasMore()) {
while (enum.hasMore()) {
SearchResult sr = (SearchResult)enum.next();
findAttrs(sr.getAttributes(), doc);
}
} else {
Item item = doc.getFirstItem("HiddenSearchResults");
doc.replaceItemValue("HiddenSearchResults", "CN not found");
doc.save(true);
}
} catch (NamingException e) {
e.printStackTrace();
} catch (Exception e) {
e.printStackTrace();
}

try {
Item item = doc.getFirstItem("HiddenSearchResults");
Vector v = new Vector();
String result;

if (attrs.size() == 0) {
v.addElement("Name found but attribute is blank or not found. Try again …”);
} else {
/* Get each attribute */
try {
for (NamingEnumeration ae = attrs.getAll(); ae.hasMore();) {
Attribute attr = (Attribute)ae.next();
/* Get each value */
for (NamingEnumeration e = attr.getAll(); e.hasMore();) {
result = (String)e.next();
v.addElement(result);
}
}
} catch (NamingException e) {
e.printStackTrace();
}
} // end if
doc.replaceItemValue("HiddenSearchResults", v);
doc.save(true);
} catch (Exception e) {
e.printStackTrace();
}

• An attribute that belongs to a person; SearchType = “Person”
  The user types the name and selects an attribute from the list. The Search LDAP button calls the LDAPSearchWithFilter agent and presents the result. For an individual attribute search, the result is displayed using the SearchResults field, whose value is retrieved from the HiddenSearchResults field.
• Members in a group; SearchType = “Group”
  The user types the name of the group, and upon exiting the field, the LDAPSearchWithFilter agent is called. You use the results to populate the SearchResultsGroup field. If the search does not return any results, the Group not found message is displayed in this field.

pos1 = Instr(Cstr(values), "=")
pos2 = Instr(Cstr(values), ",")
stringValue =Mid(Cstr(values), pos1+1, pos2-pos1)
Call uidoc.FieldAppendText("HiddenSearchResults", stringValue)