The LDAPmonitor application is implemented as a servlet designed to be run within a servlet context. The LDAPMonitor application has only been tested with Apache Tomcat version 5.x, however, barring servlet deployment issues that vary with the various servlet engines, the application should run in any 2.x servlet context.
The LDAPmonitor.war file contains all the files for this application. The jar file maybe auto-deployed when using Tomcat 5.x The easiest method perform deployment with Tomcat is by using the Tomcat Manager. The Tomcat Manager information be found at: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/manager-howto.html .
Config Files#The LDAPMonitor program is dependent on various property files for operation.
What needs done to the LDAPMonitor for moves, adds or changes if there are changes to the LDAP environement.
As the LDAPmonitor application requires a Java Virtual Machine, Standard Edition (J2SE) of at least 1.5 or higher.
Servlet Container. Reccomend that Apache Tomcat 5.9 or higher be used.
The application is designed to use four (40) to eight (128) megabytes of memory depending on the number of processors and server configuration.
- Install a Java 2 Platform, Standard Edition (J2SE) of at least 1.5 or higher.
- Install Apache Tomcat 4.1.30 or higher and make sure it is working.
NOTE: As LDAPmonitor is run inside the corporation, we assume any server we make a conenction to is "safe" and so no SSL certificates are verified.
Using the TomCat Manager, use the "Upload a WAR file to install" and install the application. Note: This may take several minutes. When it is finished, you will need to "STOP" LDAPMonitor using the Tomcat manager. Then perform the following:
Go to <tomcathome>/webapps/LDAPMonitor/WEB-INF/classes. Edit the ndsperf.properties file, after making a copy of the original. See the configurations section for what is needed in this file.
Edit the ldapperflogger.properties file , after making a copy of the original. See the configurations section for what is needed in this file.
Make the Server auto-load Tomcat when Started. As this is platform dependent, we will not elaborate on the exact method for each platform. For Linux, place a file that supports the 'chkconfig' format in /etc/init.d. Usually this file is provided without an extension. A samle ldamon script for this use is provided, but you will need ot edit the file to provide the correct location of tomcat.