Configuring ODM Logging in Oracle Weblogic

• The first method requires you to modify the EAR file, WAR file and JAR file deployed in order to modify the configuration file within, it is complex and error-prone.
• The preferred method is to reference the configuration file as a runtime system property. IBM's documentation about logging says to use a -Djava.util.logging.config.file=<file path> statement. The trick for Weblogic is to know where to put it.

• Place it in the root of the ODM domain
• The configuration file creates 2 loggers: one to stdout and one to a file
• It will put the logging file in the domain directory
• Choose the appropriate filters and LEVEL for what you are troubleshooting
  handlers= java.util.logging.ConsoleHandler, java.util.logging.FileHandler
  java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
  java.util.logging.ConsoleHandler.level = INFO
  java.util.logging.FileHandler.pattern=team-server-%u.log
  java.util.logging.FileHandler.level = FINEST
  java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter.level:INFO
• Use the trace string(s) provided by the ODM support team. For example, if the support team requested traces with the com.ibm.rules.decisioncenter.deployment trace string, at the FINE level, then use:
  com.ibm.rules.decisioncenter.deployment:FINE
  Valid trace levels are SEVERE, WARNING, INFO, CONFIG, FINE, FINER and FINEST

• In the <domain root>/bin/startWebLogic.sh file
• add the following just after the section that describes the different variables:

• # See "Managing Server Startup and Shutdown for Oracle WebLogic Server"
  # *************************************************************************

  JAVA_OPTIONS="${JAVA_OPTIONS} -Djava.util.logging.config.file=logging.properties"
  umask 027
  # Call setDomainEnv here.

• with ALL logging information being sent to it,
• and INFO-level logging info being sent to STDOUT.
• You can set WebLogic to log STDOUT messages to the WebLogic configuration by going to the WebLogic Console and clicking on the Environment -> Servers -> <the Decision Center Server> -> Logging, expanding the Advanced section, and checking ‘Redirect stdout logging enabled’

http://docs.oracle.com/middleware/1221/wls/WLLOG/logging_services.htm#WLLOG116