The JDBC channel allows the logging server to output filtered events to any JDBC-enabled data store.
WARNING:The JDBC channel does not work on NetWare 5.x. The JDBC channel requires JVM 1.4.2, which is not compatible with NetWare 5.x. Attempting to run the JDBC channel on NetWare 5.x abends the server.
Novell Audit installs its Java drivers to the following Novell Audit classpath directories:
Table 6-6 Novell 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 JDBC driver, lgdjava, looks in the Novell Audit Java classpath for the JDBC Class designated in the JDBC Channel object configuration. It then attempts to launch the JDBC Class. If it is successful, that instance of the Class remains active until the JDBC Channel object is disabled or the Secure Logging Server is shut down.
If it cannot launch the JDBC Class, the JDBC driver refuses to load. This safeguard ensures that no events are lost because of misconfiguration.
NOTE:The JDBC driver does not buffer events that are undeliverable because of misconfiguration or a server failure.
The configuration requirements to use the JDBC channel with a JDBC-enabled data store are as follows:
The JDBC drivers are available at the following sites:
Table 6-7 JDBC Driver Sites
NetWare: sys:\tomcat\4\common\lib
Linux and Solaris: /var/opt/novell/tomcat4/common/lib
Windows: \program files\novell\tomcat\common\lib
export LD_LIBRARY_PATH=/usr/lib/java/jre/lib/i386/server:/usr/lib/java/jre/lib/i386/
Replace /usr/lib/java with the full path to the Java runtime environment, for example, /usr/lib/SunJava2-1.4.1.
For additional information on configuring the JDBC channel, see Section F.0, Using JDBC Data Stores with Novell Audit.
The JDBC Channel object stores the information the JDBC driver needs to write events to a JDBC-enabled data store.
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 H.3, Secure Logging Server Startup Commands
Table 6-8 JDBC Channel Object Attributes
Attribute |
Description |
---|---|
Configuration |
|
|
Package and name of the Java Class providing JDBC connectivity. The following are Java class examples for the most common JDBC drivers:
|
|
Valid JDBC URL for the target data store, including the table name. The following are JDBC URLs for the most common JDBC drivers:
|
|
The username the JDBC driver requires to log in to the data store. |
|
The password the JDBC driver requires to log in to the data store. |
|
Name of the table used to log Novell Audit events. |
|
If the table specified in the JDBC Table parameter does not exist, use SQL commands to create the table. |
|
The maximum size (in bytes) of information that can be written at one time to the data store. |
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 Object Attributes . If you select the 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 .For information on unloading the logging server, see Section H.3, Secure Logging Server Startup Commands. |