Network Deployment (Distributed operating systems), v8.0 > Troubleshoot and support > Add logging and tracing to the application > Program with the JRas framework > Instrumenting an application with JRas extensions
Set up for integrated JRas operation
Use JRas operations in integrated mode to send trace events and logging messages to only WAS logs. The JRas framework described in this task and its sub-tasks is deprecated. However, you can achieve similar results using Java logging. In the integrated mode of operation, message and trace events are sent to WAS logs. This approach is the default mode of operation.
Procedure
- Import the requisite JRas extensions classes:
import com.ibm.ras.*; import com.ibm.websphere.ras.*;- Declare logger references:
private RASMessageLogger msgLogger = null; private RASTraceLogger trcLogger = null;- Obtain a reference to the Manager class and create the loggers. Because loggers are named singletons, you can do this activity in a variety of places. One logical candidate for enterprise beans is the ejbCreate method. For example, for the myTestBean enterprise bean, place the following code in the ejbCreate method:
com.ibm.websphere.ras.Manager mgr = com.ibm.websphere.ras.Manager.getManager(); msgLogger = mgr.createRASMessageLogger("Acme", "WidgetCounter", "RasTest", myTestBean.class.getName()); // Configure the message logger to use the message file that is created // for this application. msgLogger.setMessageFile("acme.widgets.DefaultMessages"); trcLogger = mgr.createRASTraceLogger("Acme", "Widgets", "RasTest", myTestBean.class.getName()); mgr.addLoggerToGroup(trcLogger, groupName);
JRas manager and logger instances
Set up for combined JRas operation
Set up for stand-alone JRas operation