• VLV support
• Browser issues
• Running with Netscape LDAP Java SDK
• Problems with launching Browser
• Modifications of 'runnit' scripts

VLV support

The 2.8 version does not support VLV control at this point. To enable Virtual List View controls support on 2.7 VLV version of the LDAP Browser edit the browser.cfg file and add following lines:

usevlv=yes
vlvsize=20

The Browser will use the VLV control whenever it's connected to LDAP v3 server and the server supports this control.

Notes:

In some cases, you may need to bind as a non-anonymous user to actually use VLV. 

 
• LDIF Import/Export

The Browser only supports 'simplified' type of LDIF file format. It does not support 'changetypes' 

• Tree Copy/Rename (2.7 only)

This functionality is very tricky and might not work in some cases at all. During this operation, the Browser searches though each attribute of an entry for the old dn reference and replaces it with a new dn. The occurrence in the attribute must match exactly the old dn to be replaced, if not it will be ignored. e.g. "o=globus, c=us" vs. "o=globus,c=us" (Note the space between comma and 'c=us') In this case, even though the dns are the same the operation will fail. Alternatively, the same functionality can be achieved through the LDIF operations: export the dn tree to a file, modify the file and entries as needed and import it back.

• Fetch DN (in Connect Window)

This function automatically retrieves the DN context(s) from a ldap server with only host name and port number specified. This function only works with ldap v3 servers. 

This only applies to LDAP Browser/Editor version 2.7. To configure the browser to use Netscape LDAP libraries follow these steps:

1. Download the LDAP SDK from Netscape and put the jar files found in the 'packages' directory into the 'browser\lib' directory.
2. Modify the runnit script to include the extracted jar in the classpath.
3. Add or modify the line in the browser.config file to read  'libtype=netscape'
4. Run it.

 
• 'Can't find class Browser' error

If you get the following error message: Can't find class Browser
you can try two things to fix it. Try the first one first and if that does not work try to other one. 

Sol. 1: Unpack the Browser.jar file

Unpack: jar xvf Browser.jar 
Modify following line in the runnit script 

EXEC='Browser.jar Browser' 
to:
EXEC=' Browser'
      ^ 
      the space is important.

Sol. 2: Recompile the Browser

Download the source code and recompile it in your environment. 

• 'Out of environment space' error

That usually happens on Windows 95/98 machines. To fix this try following: go to Start -> MSDOS Prompt (Properties) -> Memory -> Initial enviornment and change this value from 'auto' to 4096. Try to run the browser again.

Edit runnit script and modify the following lines to reflect your Java settings. 

For Java 2, edit JAVA_HOME variable, e.g:

• Unix:

JAVA_HOME=/sandbox/jdk1.2

• Windows:

set JAVA_HOME=c:\jdk1.2