Programming with the JRas framework

Use the JRas extensions to incorporate message logging and diagnostic trace into WebSphere® Application Server applications.

Before you begin

Deprecated feature Deprecated feature: The JRas framework that is described in this task and its sub-tasks is deprecated. However, you can achieve similar results using Java™ logging.depfeat

About this task

The JRas extensions allow message logging and diagnostic trace to work with WebSphere Application Server applications. They are based on the stand-alone JRas logging toolkit.
Note: This topic references one or more of the application server log files. As a recommended alternative, 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 on distributed and IBM® i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

Procedure

  1. Retrieve a reference to the JRas manager.
  2. Retrieve message and trace loggers by using methods on the returned manager.
  3. Call the appropriate methods on the returned message and trace loggers to create message and trace entries, as appropriate.

Icon that indicates the type of topic Task topic



Timestamp icon Last updated: March 5, 2017 17:29
File name: ttrb_jras.html