Adding logging and tracing to your application
You can add logging and tracing to applications to help analyze performance and diagnose problems in WebSphere® Application Server.
About this task
Deprecation: The JRas framework that is described in this information center is deprecated. However, you can achieve the same results using Java™ logging.
Designers and developers of applications that run with or under WebSphere Application Server, such as servlets, JavaServer Pages (JSP) files, enterprise beans, client applications, and their supporting classes, might find it useful to use Java logging for generating their application logging.
- Your messages are displayed in the WebSphere Application Server standard log files, using a standard message format with additional data, such as a date and time stamp that are added automatically.
- You can more easily correlate problems and events in your own application to problems and events that are associated with WebSphere Application Server components.
- You can take advantage of the WebSphere Application Server log file management features.
You can view your messages with the Log and Trace Analyzer tool.

Procedure
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 your application if you want your 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 |
Here is a sample security policy that grants permission to modify logging properties:
//////////////////////////////////////////////////
//
// WebSphere Application Server Security Policy
//
//////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
// Allow all access to the file system and runtime classes
////////////////////////////////////////////////////////////////////////
grant codeBase "file:${application}" {
permission java.util.logging.LoggingPermission "control";
};