Add logging and tracing to your application

Designers and developers of applications that run with or under WAS, such as servlets, JSP files, enterprise beans, client applications, and their supporting classes, may find it useful to use the same facility for generating messages that WAS itself uses, JRas.

This approach has advantages over simply adding System.out.println() statements to your code:

• Your messages appear in the WAS standard message format with additional data, such as a date and time stamp, added automatically.
• You can more easily correlate problems and events in your own application to problems and events associated with WAS components.
• You can take advantage of the WAS log file management features.
• You can view your messages with the WAS user-friendly Log Analyzer tool.

See the following topics for more information about the JRas facility:

Programming model summary
This topic provides a summary of the JRas programming model and formalizes usage requirements and restrictions.

Overview of JRas
This topic describes message logging and diagnostic trace and explains some basic JRas concepts.

Program with the JRas framework
This topic describes how to use the JRas extensions to incorporate message logging and diagnostic trace into WAS applications.

Extending the JRas framework
This topic defines the various extension points have been defined to JRas extension classes.

JRas messages and trace event types
This topic describes JRas message and trace event types and their associated parameters.