Saturday, May 5, 2012

How to configure the logging for the WebLogic console

Having notied that in the access.log of the admin I can't see anything related to /console (only /sbconsole is there), I do a little investigation. No logging configuration is possible via the WebLogic console itself.
Here they give more info on the console application (4th post):

"What the console is depends on which version of WebLogic Server you are running.

Before 7, the console was a Swing app.

In 7 and 8.1, the console was a webapp, and indeed used applets in several places, such as the nav tree and performance graphs. It never actually reads config.xml, but instead interacts with an mbean server to obtain the configuration and runtime structure.

In 9.0, the console became a JEE Portal application that contained multiple webapps, and no longer uses any applets in the base console. (Some extensions use applets.) It continues to interact with several MBean Servers to obtain domain structure and runtime statistics.

Assuming that you're using a recent release, you can find the deployed console application binaries in WL_HOME/server/lib/consoleapp, and can look at the descriptors, portal configuration files, style sheets, and other artifacts in there.

If there is anything particular that you are trying to accomplish, I'd be happy to work with you to share the relevant console algorithms and perhaps code snippets which could help.

Loren Konkus
Staff Software Engineer
BEA Systems, Inc."

cd /opt/oracle/fmw11_1_1_5_32bit/wlserver_10.3/server/lib/consoleapp
cat ./consolehelp/WEB-INF/classes/

# WLS Admin console log4j configuration file

# Create one appender, one called stdout
# and set default level to DEBUG
log4j.rootLogger=WARN, stdout

# Make Apache classes quiet by default = ERROR = INFO = ERROR = FATAL = ERROR = ERROR = ERROR = ERROR = INFO = ERROR = ERROR

# Configure the stdout appender to go to the ConsoleLogHandler
# This will delegate to a WLS Catalog Logger and end up in the admin server log

The consoleapp will be deployed to

but don't expect to find log4j there....

Finally, it's still a bit of a mystery...

No comments: