Top of GEN

Index

Table of Contents

Feedback

GENW0050 - Maintain Logging Configuration - New for Release 15.0

Overview

For more detailed information relating to this page, refer to td_jsf_configuration.pdf which is included in the Callista Release Documentation.

Logging levels are a standard Java concept used to adjust the amount of logging information written to a log. When problems are encountered in the application then it is useful to raise the level of detail written to the log in order to help diagnose the problem, however this can come at the cost of performance.

The levels used in Callista software are, in order of most detail to least detail (or least severity to highest severity):
TRACE -> DEBUG -> INFO -> WARN -> ERROR.

When a particular logging level is set, it will log all messages at that level plus all messages at a higher severity level. In GENW0050, the logging level can be set for various parts of the JSF software, as well as various logging configuration options.

For further information about Logging Configuration see td_jsf_configuration.pdf (included in the Callista Release Technical documentation).

After altering the logging configuration optionson this page and clicking Save, the logging can be tested by clicking the Test Logging button in GENW0050. This will write messages to the log.
To view the log, go to GENW0060. If the logging level is set to INFO for all three parts of the system, then information similar to the following should be visible in GENW0060.

<####<Apr 5, 2012 4:04:07 PM EST> <Info> <au.com.callista.sms.task.genw0050.view.managed.LoggingConfigurationBean> <crux.callista.com.au> <WLS_JSF_sisacpt> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> < angy> <> <18ee6f1587d6f2fd:-bf91909:1367edb3ac9:-7f0e-000000000000604a> <1333605847395> <BEA-000000> <Info test message from GENW0050.>
####<Apr 5, 2012 4:04:07 PM EST> <Notice> <StdErr> <crux.callista.com.au> <WLS_JSF_sisacpt> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1333605847396> <BEA-000000> <Apr 5, 2012 4:04:07 PM au.com.callista.sms.task.genw0050.view.managed.LoggingConfigurationBean testLogging
INFO: Info test message from GENW0050.>
####<Apr 5, 2012 4:04:07 PM EST> <Warning> <au.com.callista.sms.task.genw0050.view.managed.LoggingConfigurationBean> <crux.callista.com.au> <WLS_JSF_sisacpt> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> < angy> <> <18ee6f1587d6f2fd:-bf91909:1367edb3ac9:-7f0e-000000000000604a> <1333605847402> <BEA-000000> <Warn test message from GENW0050.>
####<Apr 5, 2012 4:04:07 PM EST> <Notice> <StdErr> <crux.callista.com.au> <WLS_JSF_sisacpt> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1333605847404> <BEA-000000> <Apr 5, 2012 4:04:07 PM au.com.callista.sms.task.genw0050.view.managed.LoggingConfigurationBean testLogging
WARNING: Warn test message from GENW0050.>
####<Apr 5, 2012 4:04:07 PM EST> <Error> <au.com.callista.sms.task.genw0050.view.managed.LoggingConfigurationBean> <crux.callista.com.au> <WLS_JSF_sisacpt> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> < angy> <> <18ee6f1587d6f2fd:-bf91909:1367edb3ac9:-7f0e-000000000000604a> <1333605847410> <BEA-000000> <Error test message from GENW0050.>
####<Apr 5, 2012 4:04:07 PM EST> <Notice> <StdErr> <crux.callista.com.au> <WLS_JSF_sisacpt> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1333605847410> <BEA-000000> <Apr 5, 2012 4:04:07 PM au.com.callista.sms.task.genw0050.view.managed.LoggingConfigurationBean testLogging
SEVERE: Error test message from GENW0050.>

Return to Top

Page Navigation

This page is reached directly from the menu.

Return to Top

Field Descriptions

Field: Description:
System-wide Logging Level

The logging-level for all classes in the system – ADF framework and Callista Software
Note: Setting this value to DEBUG or TRACE can cause the application to slow down considerably and the log file to fill up quickly.
Default value: INFO.

Oracle Business Components Logging Level Substitution Tag description

The logging-level for Oracle Business Components in the system
This is useful if there are model-level issues (the part of the application responsible for database operations). Set this to TRACE to see any appropriate logging information.
Note: this can also cause the application to slow down and the log file to fill up quickly.
Default value: INFO.
Callista Software Logging Level The logging level for Callista software
If there is a problem in the application and more logging information is required, then this logging level should be increased before System-wide and Oracle Business Components Logging.
Default value: INFO.
Weblogic Server Log File Detected This is a read only indicator which indicates if the application has detected the Weblogic Server Log. Generally this should display a tick.
Weblogic Server Log File Location This is a read only field which displays the location of the Weblogic Server log on the application server.
Send Application Log Output to Web Logic Server Log File Set this to 'Y' if you want Callista Logging Information written to the Weblogic Server Log.
Generally this should be set to 'Y' unless you have set up an external log file set up (see below) and you specifically do not want application-related log messages written to the server log.
Send Application Log Output to External Log File Callista also offers the option of sending application log output to a separate log file. This offers the benefit of having better control of where the log file gets written and additionally the log information is presented in an easier to read format and is not cluttered with server-related log messages. Set this to 'Y' if you want this option (you will also need to specify a log file location – see below).
External Log File Location If electing to send application log output to an external log file, then the location of that log file must be entered here. It must be a valid path on the application server machine.
e.g. /opt/css/test/new/jsf/logs/CallistaSMS.log
Server Log Handlers This is a read only field that displays which handlers are attached to the server log. A handler is a java object responsible for doing something with log output.
e.g. Writing it to a file or displaying it in a console. It is for information purposes only.
Application Log Handlers This is a read only field that displays which handlers are attached to the application log. A handler is a java object responsible for doing something with log output.
e.g. Writing it to a file or displaying it in a console. It is for information purposes only.
Return to Top

Related Pages

CORW0400 CORW0500 CORW0600 The Log can be viewed in GENW0060.

 

Return to Top

Last modified on 31 May, 2012 1:01 PM

History Information

Release Version Project Change to Document
15.0 1722 - 11g Upgrade New Help page