7.6 Java

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.

WARNING:The Java channel does not work on NetWare 5.x. The Java channel requires JVM* 1.4.2 which is not compatible with NetWare 5.x. Attempting to run the Java channel on NetWare 5.x abends the server.

7.6.1 Java Channel Driver

Nsure Audit installs its Java drivers to the following Nsure Audit classpath directories:

Table 7-4 Nsure Audit Java Classpath

Platform

Java Classpath

NetWare

sys:\system\naudit\

Windows

\program files\novell\nsure audit\java\logdriver\

Linux

/opt/novell/naudit/java/logdriver/

Solaris

/opt/NOVLnaudit/java/logdriver/

At startup, the Java driver, lgdjava, looks in the Nsure Audit Java 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.

Configuration Requirements

To configure the Java channel, you must perform the following tasks:

  • Copy the .jar files required for additional Java channels you are using with Nsure Audit to the Nsure Audit Java classpath or a subdirectory thereof.
  • If you are using the Java Channel on a Windows machine, you must add the jvm.dll directory path to the Path system variable. For example, c:\j2sdk1.4.2_09\jre\bin\server\. You must reboot the machine for the changes to take effect
  • On Linux/Solaris, the LD_LIBRARY_PATH variable needs to point to the paths for libverify.so, and libjvm.so. You must reboot the machine for the changes to take effect.

For information on how to hook your Java Class into the Java channel driver, refer to the Java channel API in the Nsure Audit SDK.

7.6.2 Java Channel Object

The Java Channel object stores the information the Java driver needs to launch a Java Class.

The following table provides a description of each Channel object attribute.

IMPORTANT:You must restart the logging server to effect any changes in Channel object configuration. For more information, see Section G.3, Secure Logging Server Startup Commands

Table 7-5 Java Channel Object Attributes

Attribute

Description

Configuration

Contains configuration information for the Java Channel object.

Java Driver Class

The name of the Java Class the Java driver launches.

Max Data Size

The maximum size (in bytes) of information that can be written at one time to the Java application.

Status

Allows you to enable or disable the Channel object. By default, all Channel objects are enabled. This means that the logging server loads the Channel object’s configuration in memory at startup.

The Channel object must be located in a supported Channel container for the logging server to use it. For more information on the logging server’s Channel Container property, see Logging Server Objects .

If you select the Disabled option, you must restart the Secure Logging Server for the setting to become effective. Thereafter, the logging server cannot load the object’s configuration until you select Enabled.

For information on unloading the logging server, see Section G.3, Secure Logging Server Startup Commands.