Network Deployment (Distributed operating systems), v8.0 > Troubleshoot and support > Add logging and tracing to the application
Program with the JRas framework
Use the JRas extensions to incorporate message logging and diagnostic trace into WAS applications. The JRas framework described in this task and its sub-tasks is deprecated. However, you can achieve similar results using Java logging. The JRas extensions allow message logging and diagnostic trace to work with WAS applications. They are based on the stand-alone JRas logging toolkit.
With WAS v8 you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using $PROFILE/bin/LogViewer.sh. See the information about using HPEL to troubleshoot applications for more information on using HPEL.New feature:
Procedure
- Retrieve a reference to the JRas manager.
- Retrieve message and trace loggers by using methods on the returned manager.
- Call the appropriate methods on the returned message and trace loggers to create message and trace entries, as appropriate.
Related
JRas logging toolkit
JRas Extensions
JRas messages and trace event types
Instrumenting an application with JRas extensions