Jarek Gawors Browser

Posted on February 19, 2012 by Admin
Jarek Gawors Browser

Jarek Gawors Browser


Jarek Gawor's LDAP Browser-Editor has been one of the most popular LDAP tools in use by directory admins for at least 7 years. Never mind that the last release of the software was v2.8.2b2 (that's Beta 2) in 2001, it remains top on my list because, warts and all (not the least of which is that it was programmed using Java Swing), it is still the best at what it does.

Installing and configuring it on Linux has never been hard, unless you want to make it play nice in a multi-user environment. If you don't want to force each user to install their own personal copy, you're going to have to make some changes to the shipping shell script used to launch the app and make a dot directory in your user's home.

My standard setup puts the unarchived app code into a directory called /opt/ldapbrowser, which I normally create by simply copying Browser282b2.tar.gz to /opt and doing a tar czf on it right there.

Next, I backup the shipping lbe.sh and replace it with my own:

#!/bin/sh
JAVA_HOME=/usr/java/jdk1.5.0_11
LBE_ROOT=/opt/ldapbrowser

cd ~/.lbe

${JAVA_HOME}/bin/java -jar ${LBE_ROOT}/lbe.jar $1 $2 $3 $4 $5 $6 $7 $8 $9

Then I run a symlink from the new lbe.sh to /usr/bin/lbe:
ln -s /opt/ldapbrowser/lbe.sh /usr/bin/lbe

Finally, I go and create an .lbe directory in my user's home and copy attributes.config from /opt/ldapbrowser into it. I also run symlinks from /opt/ldapbrowser/help and /opt/ldapbrowser/templates into .lbe, so the resources in those directories will display properly.

Feedback is welcome. Click Add Comment at the bottom of the page.

This explains how to enable tutorial HQ to monitor Sun/OpenJDK 1.5 or 1.6 Java Virtual Machines (JVM), and how to troubleshoot the monitoring setup if you have problems.

This tutorial supplements the metric documentation and configuration instructions here: http://support.hyperic.com/display/hypcomm/Sun+JVM

Despite its name and description, the HQ Java JVM 1.5 Plugin is compatible with both Java 1.5 and Java 1.6. You must manually deploy the Java JVM 1.5 plugin and configure monitoring - autodiscovery is not enabled by default.

Enable Remote JMX Monitoring

Remote JMX monitoring must be enabled for your Virtual Machine. You must configure an unprivileged, unused port higher than 1024 for remote JMX connection.

You can verify port availability using netstat. The command below checks to see whether port 16969 is in use.