####################################################################################### # In H4Apps environment we should have atleast one log turned on # to make sure all logs above warn should get into the # # FILE = # LEVEL = # WARN > APP > DEBUG > # # FORMAT= # APPS, TOOLS, TOOLS_THREAD # MAXFILESIZE = # MAXBACKUPINDEX = # COMPONENTS= # # # COMPONENTS: # # ALL|LIB|NET|KERNEL|JDBC|RUNTIME|SAW|JAS|JASBASE|XML|OWHTML|OWPORTAL|REDIRECTOR| # INTEROP|SERVICES|THREADPOOL|TE|BPM|AUTOPILOT|SUPPORTASSISTANT|MAF|PERFMON|JDBJ| # METADATA|PSFT|BASE|APPLOGIC|BIZLOGIC|CODEGEN|E1MENU|EVENTPROCESSOR|JAVATOKEN| # OET|PIMSYNC|PPM|TEXTSEARCH|WEBGUI ####################################################################################### #=========================================================================== # DEGUG #=========================================================================== #The section name should be E1LOG. This logs all the log messages above WARN [E1LOG] FILE=/tmp/jdelog/jderoot.log LEVEL=WARN FORMAT=APPS MAXFILESIZE=10MB MAXBACKUPINDEX=20 COMPONENT=ALL APPEND=TRUE #Logging runtime and JAS above APP level will be helpful for application developers. #Application developers should use this log as a substitute to analyze the flow of events #in the webclient. [LOG1] FILE=/tmp/jdelog/jas.log LEVEL=WARN FORMAT=APPS MAXFILESIZE=10MB MAXBACKUPINDEX=20 COMPONENT=RUNTIME|JAS APPEND=TRUE #Logging runtime and JAS at DEBUG level will be helpful for tools developers. #Tool developers should use this log ato debug tool level issues [LOG2] FILE=/tmp/jdelog/jasdebug.log LEVEL=DEBUG FORMAT=APPS MAXFILESIZE=10MB MAXBACKUPINDEX=20 COMPONENT=ALL APPEND=TRUE