You can add logging and tracing to applications to help analyze performance and diagnose problems in WebSphere® Application Server.
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.
Set up a security policy to allow your applications to modify logging and handler properties.
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:
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:
////////////////////////////////////////////////// // // 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"; };
In this information ...Subtopics
Related tasks
| IBM Redbooks, demos, education, and more(Index) |