WAS v8.5 > Troubleshoot

Add logging and tracing to the application

Developers of applications that run with or under WAS, such as servlets, JSP files, enterprise beans, client applications, and their supporting classes, might find it useful to use Using Java logging to generate their application logging has advantages over adding System.out.println statements to the code:

• Messages are displayed in the WAS standard log files, using a standard message format with additional data, such as a date and time stamp that are added automatically.
• Problems and events can be correlated and and associated with WAS components.
• Java logging leverates WAS log file management features.
• Use the Log and Trace Analyzer tool to view messages.

1. To configure logging...
   • Configure Java logging
   • Configure applications to use Jakarta Commons Logging

2. Customize the properties to meet the logging needs. For example, enable or disable a particular log, specify the number of logs to be kept, and specify a format for log output.
   • Configure Java logging

3. If we do not want log and trace from Jakarta Commons Logging to use the WebSphere log and trace infrastructure, reconfigure the Jakarta Commons Logging.
   • Configure applications to use Jakarta Commons Logging

   Best practice: Use the WebSphere log and trace infrastructure for all of the log content to make problem source identification simpler.

4. Restart the application server after making static configuration changes.

Example

The sample security policy that follows grants access to the file system and runtime classes. Include this security policy, with the entry permission java.util.logging.LoggingPermission "control", in the META-INF directory of the application if you want the applications to programmatically alter controlled properties of loggers and handlers. The META-INF file is located in the following locations for the different module types:

Project name	Location
EJB projects	ejbModule/META-INF/MANIFEST.MF
Application client projects	appClientModule/META-INF/MANIFEST.MF
Dynamic web projects	WebContent/META-INF/MANIFEST.MF
Connector projects	connectorModule/META-INF/MANIFEST.MF

Below is a sample security policy that grants permission to modify logging properties:

//////////////////////////////////////////////////
//
// WAS Security Policy //
//////////////////////////////////////////////////

////////////////////////////////////////////////////////////////////////
// Allow all access to the file system and runtime classes ////////////////////////////////////////////////////////////////////////
grant codeBase "file:${application}" {
   permission java.util.logging.LoggingPermission "control";};

Subtopics

• Use Java logging in an application
  This topic describes how to use Java logging within an application.
• Configure applications to use Jakarta Commons Logging
  Jakarta Commons Logging provides a simple logging interface and thin wrappers for several logging systems. WAS supports Jakarta Commons Logging by providing a logger. The support does not change interfaces defined by Jakarta Commons Logging.
• Use Java logging in an application
  This topic describes how to use Java logging within an application.
• Configure applications to use Jakarta Commons Logging
  Jakarta Commons Logging provides a simple logging interface and thin wrappers for several logging systems. WAS supports Jakarta Commons Logging by providing a logger. The support does not change interfaces defined by Jakarta Commons Logging.
• Programming with the JRas framework
  Use the JRas extensions to incorporate message logging and diagnostic trace into WAS applications.
• Logging Common Base Events in WAS
  WAS uses Common Base Events within its basic logging framework. Common Base Events can be created explicitly and then logged through the Java logging API, or can be created implicitly using the Java logging API directly.

Related

Configure Java logging

+

Search Tips   |   Advanced Search