The Java* channel allows the logging server to output filtered events to a Java application. Typically, the Java Class is a custom application that provides a response to specific types of events. For example, if a user login is disabled, the Java channel driver can launch a Java Class that automatically resets the user account.
At startup, the Java driver, lgdjava, looks in the classpath for the Java Class designated in the Java Channel object configuration. It then attempts to launch the Java Class. If it is successful, that instance of the Class remains active until the Java Channel object is disabled or the Secure Logging Server is shut down.
If it cannot launch the Java Class, the Java driver refuses to load. This safeguard ensures that no events are lost because of misconfiguration.
NOTE: The Java driver does not buffer events that are undeliverable because of misconfiguration or a server failure.
At startup, Novell® Audit defines the Java classpath as follows:
Novell_Audit_install_directory\java\logdriver\
Novell Audit installs its default Java drivers to this directory. Any .jar files required for additional Java channels you are using with Novell Audit must be copied to this directory or a subdirectory.
For information on how to hook a Java class into the Java channel driver, refer to the Java channel API in the Novell Audit SDK.
NOTE: If you are using the Java channel on a Windows* machine, you need to the add the jvm.dll directory path to the Path system variable. For example, c:\j2sdk1.4.2_09\jre\bin\server\. Reboot the machine for the changes to take effect.
A trademark symbol (®, , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For information on trademarks, see Legal Notices.