By default, oracle weblogic server logging service uses an implementation, based on the Java Logging APIs by using the LogMBean.isLog4jLoggingEnabled attribute. With a few effort you can use log4j with weblogic logging service. In the Administration Console, you can specify Log4j or keep the default Java Logging implementation. In this blog i will describe how to configure log4j with weblogic logging service and writes all the logs messages to database table.
Most of all cases it's sufficient to writes log on files, however it's better to get all the logs on table to query on it. In our case we have 3 different web logic servers in our project and our consumer need to get all the logs in one central place to diagnose if something goes wrong.
First of all we will create a simple table on our oracle database schema and next configure all other parts.
Here we go:
1)
2) Now we will create a log4j.properties file with following contents and save it %DOMAIN_HOME%
3) Copy log4j-1.2.9.jar & wllog4j.jar and ojdbc14.jar under domain_root/lib folder.
4) edit setDomainEnv.sh with following JAVA_OPTION parameter
set JAVA_OPTIONS=-Dweblogic.log.Log4jLoggingEnabled=true
which will active log4j for logging service
5) Most critical tips, add following parameter after JAVA_OPTIONS
set LOG4J_CONFIG_FILE=%DOMAIN_HOME%/log4j.properties
which will force weblogic server to read the log4j configure file from the specified location.
6) Restart the server and you should find all the log messages on database table.
You may also use custom connection pool mechanism with a little effort with JDBCAppender.
Most of all cases it's sufficient to writes log on files, however it's better to get all the logs on table to query on it. In our case we have 3 different web logic servers in our project and our consumer need to get all the logs in one central place to diagnose if something goes wrong.
First of all we will create a simple table on our oracle database schema and next configure all other parts.
Here we go:
1)
CREATE TABLE LOGS (USER_ID VARCHAR2(20), DOMAIN varchar2(50), DATED DATE NOT NULL, LOGGER VARCHAR2(500) NOT NULL, LEVEL VARCHAR2(50) NOT NULL, MESSAGE VARCHAR2(4000) NOT NULL );
2) Now we will create a log4j.properties file with following contents and save it %DOMAIN_HOME%
log4j.rootLogger=INFO, DB
log4j.logger.com.bea.weblogic.*=INFO, DB
log4j.appender.DB=org.apache.log4j.jdbc.JDBCAppender
# Set JDBC URL
log4j.appender.DB.URL=jdbc:oracle:thin:@mercury.blu.com:1521:FTSDB
# Set Database Driver
log4j.appender.DB.driver=oracle.jdbc.OracleDriver
# Set database user name and password
log4j.appender.DB.user=xyz
log4j.appender.DB.password=xyz
# Set the SQL statement to be executed.
log4j.appender.DB.sql=INSERT INTO EXT_LOGS VALUES('%x','OSB_DOMAIN',sysdate,'%C','%p','%m')
log4j.appender.DB.layout=org.apache.log4j.PatternLayout
#log4j.appender.DB.layout.ConversionPattern=%d{dd.mm.yyyy HH:mm:ss.SSS} - %m%n
3) Copy log4j-1.2.9.jar & wllog4j.jar and ojdbc14.jar under domain_root/lib folder.
4) edit setDomainEnv.sh with following JAVA_OPTION parameter
set JAVA_OPTIONS=-Dweblogic.log.Log4jLoggingEnabled=true
which will active log4j for logging service
5) Most critical tips, add following parameter after JAVA_OPTIONS
set LOG4J_CONFIG_FILE=%DOMAIN_HOME%/log4j.properties
which will force weblogic server to read the log4j configure file from the specified location.
6) Restart the server and you should find all the log messages on database table.
You may also use custom connection pool mechanism with a little effort with JDBCAppender.
Comments