WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Enabling logging and tracing for your Equinox or Eclipse launch configuration

This topic describes how to enable logging and tracing at the agent level or at the system level.

Logging and tracing is controlled by setting properties on the Alert agent.

System-level logging and tracing

By default, logging is set to DEBUG at the system level. When the Alert agent starts, it uses the configuration of the org.eclipse.soda.sat.core.util.logLevel and org.eclipse.soda.sat.core.util.trace properties for system-level logging and tracing.

Table 1. Alert agent logging and tracing properties
Property Description
org.eclipse.soda.sat.core.util.logLevel Indicates which level of logging to enable for the Service Activation Toolkit. This level should be the same level as specified for the edge.log.threshold property.
org.eclipse.soda.sat.core.util.trace Displays system level trace output. Values can be true or false.

The Alert agent is also responsible for forwarding log messages to the WebSphere® Premises Server. To change the level of messages that are forwarded, change the threshold property in Alert agent. The alert threshold can be set to INFO, WARNING, or ERROR.

Agent-level tracing and logging

Every agent has a tracing property. To enable tracing on an agent, the system trace level, org.eclipse.soda.sat.core.util.trace, must be set to true. Also, set the system log level to DEBUG or no trace will be displayed.

To modify the tracing property for all agents, you can enter something similar to the following example. This configuration disables tracing for all P1/E1 configurations.

<?xml version="1.0"?>
<configurationAdmin>
 <requests>
  <request type="update">
   <configurations>
    <configuration filter="(|(portal.id=P1)(edge.id=E1))">
     <properties>
      <property key="tracing" value="false"/>
     </properties>
    </configuration>
   </configurations>
  </request>
 </requests>
</configurationAdmin>

Many agents also have a log.level property. Setting this property allows you to control logging each agent. See the Agent details for more information on the properties available for each agent.

In addition, the following Console Log agent properties can be used to configure the level of messages displayed to the OSGi console without modifying the system log level:

Table 2. Console log agent properties and descriptions
Property Description
errorLogThreshold Minimum level of messages that are written to stderr. Valid values are none, error, warning, info, or debug.
logThreshold Minimum level of messages that are written to stdout. Valid values are none, error, warning, info, or debug. If the value is empty then the system log level is used.

Viewing messages and collecting logs

Install the com.ibm.rfid.console.log bundle into your runtime environment and start it to enable log messages from the agents to be seen on the OSGi console. When collecting a log to send with a problem report, be sure to retrieve the system properties by issuing the setprop command at the OSGI prompt. Also retrieve the list of installed bundles by issuing the ss command at the OSGI prompt.


Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.