BEA WebLogic User Manual page 205

log4j.properties You must configure log4j with appropriate settings based on the desired
format of the captured logs.
An example log4j.properties file that will log WebLogic Mobility Server
messages as Log4J messages to both the console and a file in a specified
format is shown below:
log4j.rootLogger=DEBUG, A1
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1=org.apache.log4j.RollingFileAppender
log4j.appender.A1.File=d:\\test.log
log4j.appender.A1.layout.ConversionPattern=%d [%t] %-5p %c -
%m%n
log4j.logger.com.mobileaware.diagnostics.GenericLogMonitor
=INFO
GenericLogMonitor Implementation Class
It is necessary to include a class that implements the GenericLogMonitor interface – see the
following interface description.
This class is responsible for intercepting the specified disgnostics in the mis.properties file.
This class must also be specified in the
diagnostics.startup.subscriptions.misLog.classname
This class must be placed in the com.mobility.diagnostics package under the
<install_directory>\WEB-INF\classes directory of the web application.
property in the mis.properties file.
BEA WebLogic Mobility Server User Guide - 201
Part VIII Appendixes