Installing the Listener Java API

The FileNet® System Manager Listener Java™ API is located on the FileNet System Manager media as a collection of class files provided in a standard Java Archive (JAR) file, Listener.jar. All of the objects defined by the Listener are in the com.filenet.pch package, and all of the entry points are thread-safe.

To use the Listener Java API, add the location of the Listener.jar file to the CLASSPATH variable and then instantiate a Listener object. When running on Microsoft® Windows®, the locations of the following libraries must also be specified in the search path for the application, as well as the files required by these libraries:

While the Listener is normally passive and silent, encountered problems (such as invalid values in the configuration file) are reported using log4j. Therefore, the location of the log4j package must also be specified in the CLASSPATH variable.

Windows Performance Monitoring

Systems running Microsoft Windows require that the WinPerfMon.DLL file be installed in the search path for the application (supplied with Listener.jar). This library file is used to integrate with Windows performance counters and requires that the PDH.DLL system file, as well as the DLLs that it depends on, also be installed.

If the WinPerfMon.DLL cannot be loaded, then the Listener will operate with reduced functionality: CPU, Disk, and Network statistics will be unavailable, and Duration timings will be done using the Java system clock, which is typically accurate to about 10 milliseconds.

Java Runtime Version

To obtain full System Manager operating functionality, the Java Runtime Environment (JRE) version 1.4 or higher is required. While runtime version 1.3 is also supported, this version results in reduced performance, including the loss of "environmental" data for the number of processors on the machine and the Java Virtual Machine (JVM) maximum memory size.