Tracing operations with the wsadmin tool

Overview

1. Invoke the AdminControl object commands interactively, in a script, or use the wsadmin -c command from an operating system command prompt.

2. Enable tracing with the following command:

   Using Jacl:

   $AdminControl trace com.ibm.*=all=enabled

   Using Jython:

   AdminControl.trace('com.ibm.*=all=enabled')

   where:

   $	is a Jacl operator for substituting a variable name with its value
   AdminControl	is an object that enables the manipulation of MBeans running in a WebSphere server process
   trace	is an AdminControl command
   com.ibm.*=all=enabled	indicates to turn on tracing

   
   
   The following command disables tracing:

   Using Jacl:

   $AdminControl trace com.ibm.*=all=disabled

   Using Jython:

   AdminControl.trace('com.ibm.*=all=disabled')

   where:

   $	is a Jacl operator for substituting a variable name with its value
   AdminControl	is an object that enables the manipulation of MBeans running in a WebSphere server process
   trace	is an AdminControl command
   com.ibm.*=all=disabled	indicates to turn off tracing

   
   
   The trace command changes the trace settings for the current session. You can change this setting persistently by editting the wsadmin.properties file. The property com.ibm.ws.scripting.traceString is read by the launcher during initialization. If it has a value, the value is used to set the trace.

   A related property, com.ibm.ws.scripting.traceFile, designates a file to receive all trace and logging information. The wsadmin.properties file contains a value for this property. Run the wsadmin tool with a value set for this property. It is possible to run without this property set, where all logging and tracing goes to the administrative console.

---

Example: Setting up profiles to make tracing easier when scripting
Example: Dumping threads in a server process
    

 

---