Skip to Main Content

Security Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Weblogic Logs

705246Jul 17 2009 — edited Jul 20 2009
Can anybody tell me how to activate proper "DEBUG" level logging in weblogic application server to log OIM 9.1.0.1 details in Windows environment ?
I have modified the log.properties file and have uncommmented the necessary commands (Please see below). But still its not logging anything in oim.log even if I run any GTC or scheduled tasks.
Any hints ?

Thanks.

////////////////////////////////////////////////////////////////////////////////////////////
#
# This file is to configure the logs that xellerate produces via log4j.
# this file is used by Websphere and Weblogic. If JBoss is used
# to host Xellerate, the file that needs to be modified is jboss-log4j.xml under
# the JBoss directory: <jboss_home>/server/default/conf. Since
# this file is used for the whole JBoss log configuration, a Xellerate
# tag is used to define the level to log:
#
# <category name="XELLERATE">
# <priority value="WARN"/>
# </category>
#
# That is equivalent to the line below:
# log4j.logger.XELLERATE=WARN
#
# If specific categories need to be logged as in the case of the commented
# categories below, a new category can be added after the "XELLERATE" category
# in the jboss-log4j.xml file for JBoss. For instance "XELLERATE.ACCOUNTMANAGEMENT"
# as below, would be like the following in jboss-log4j.xml:
#
# <category name="XELLERATE.ACCOUNTMANAGEMENT">
# <priority value="DEBUG"/>
# </category>
#
# In the case of Weblogic or Weblogic, uncommenting the category below would
# be enough.
# Any changes to the log configuration need to be follow by a restart of the
# Application Server.
#
# For more information about log4j, please refer to http://logging.apache.org/log4j/docs/

#
# The below configuration sets the output of the log to be to the
# standard output. In the case of JBoss it is to the console and
# for Websphere and Weblogic to the log file.
# Commentted below is "logfile" in addition to stdout. If you want
# the output to be sent to a specific file un-comment the line below
# and comment the one without the "logfile" entry.
log4j.rootLogger=WARN,stdout,logfile
#log4j.rootLogger=WARN,stdout

#
# Console Appender
# The configuration below is to configure the way the log will be formatted
# when it is output to the console.
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%5p,%d{dd MMM yyyy HH:mm:ss,SSS},[%c],%m%n

#
# File Appender
# Uncomment if you want to output to a file and change the file name and path
#
log4j.appender.logfile=org.apache.log4j.DailyRollingFileAppender
log4j.appender.logfile.DatePattern='.'yyyy-MM-dd
log4j.appender.logfile.File=D:\oim\oimserver\xellerate\logs\OIM.log
#log4j.appender.logfile.MaxBackupIndex=20
log4j.appender.logfile.layout=org.apache.log4j.PatternLayout
log4j.appender.logfile.layout.ConversionPattern=%p %t %c - %m%n


#
# Below are the different categories supported by Xellerate
# commented out. The Root Category, .XELLERATE, is not commented
# out and it's set to WARN. This means that every category is set
# to WARN level unless specifically changed. Each category can be
# uncommented and the level can be changed individually while
# the root is still on WARN (for all other categories with log level
# not defined).
# The following are the accepted levels:
#
# DEBUG - The DEBUG Level designates fine-grained informational events
# that are most useful to debug an application.
# INFO - The INFO level designates informational messages that highlight
# the progress of the application at coarse-grained level.
# WARN - The WARN level designates potentially harmful situations.
# ERROR - The ERROR level designates error events that might still allow
# the application to continue running.
# FATAL - The FATAL level designates very severe error events that will
# presumably lead the application to abort.
# Special Levels:
# ALL - The ALL Level has the lowest possible rank and is intended to turn on all logging.
# OFF - The OFF Level has the highest possible rank and is intended to turn off logging.

#################################
# XELLERATE #
#################################
log4j.logger.XELLERATE=DEBUG
# We would like to have DDM operations at the DEBUG level
# as we may not have a second chance to perform the same
# operation if something fails
log4j.logger.XELLERATE.DDM=DEBUG
#log4j.logger.XELLERATE.ACCOUNTMANAGEMENT=DEBUG
#log4j.logger.XELLERATE.SERVER=DEBUG
#log4j.logger.XELLERATE.RESOURCEMANAGEMENT=DEBUG
#log4j.logger.XELLERATE.REQUESTS=DEBUG
#log4j.logger.XELLERATE.WORKFLOW=DEBUG
log4j.logger.XELLERATE.WEBAPP=DEBUG
log4j.logger.XELLERATE.SCHEDULER=DEBUG
log4j.logger.XELLERATE.SCHEDULER.Task=DEBUG
log4j.logger.XELLERATE.ADAPTERS=DEBUG
#log4j.logger.XELLERATE.JAVACLIENT=DEBUG
#log4j.logger.XELLERATE.POLICIES=DEBUG
#log4j.logger.XELLERATE.RULES=DEBUG
#log4j.logger.XELLERATE.DATABASE=DEBUG
#log4j.logger.XELLERATE.APIS=DEBUG
#log4j.logger.XELLERATE.OBJECTMANAGEMENT=DEBUG
#log4j.logger.XELLERATE.JMS=DEBUG
#log4j.logger.XELLERATE.REMOTEMANAGER=DEBUG
#log4j.logger.XELLERATE.CACHEMANAGEMENT=DEBUG
#log4j.logger.XELLERATE.ATTESTATION=DEBUG
#log4j.logger.XELLERATE.AUDITOR=DEBUG
#log4j.logger.XELLERATE.PERFORMANCE=DEBUG


#################################
# SPML Webservice #
#################################

log4j.logger.SPMLWS=WARN
log4j.logger.SPMLWS.OIMEvent=DEBUG

#################################
# Nexaweb #
#################################

log4j.logger.com.nexaweb.server=WARN

#################################
# OSCache #
#################################
log4j.logger.com.opensymphony.oscache=ERROR


//////////////////////////////////////////////////////////////////////

Comments

Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Aug 17 2009
Added on Jul 17 2009
2 comments
1,342 views