Tracing operations with the wsadmin tool
Overview
Perform the following steps to trace operations:
You can enable tracing with scripting and the wsadmin tool.
Before starting this task, the wsadmin tool must be running.
Procedure
Enable wsadmin client tracing with the following command:
- Use Jacl:
$AdminControl trace com.ibm.*=all=enabled
- Use Jython:
AdminControl.trace('com.ibm.*=all=enabled')where:
$ Jacl operator for substituting a variable name with its value AdminControl object that enables the manipulation of MBeans running in a WebSphere server process trace AdminControl command com.ibm.*=all=enabled indicates to turn on tracing The following command disables tracing:
- Use Jacl:
$AdminControl trace com.ibm.*=all=disabled
- Use Jython:
AdminControl.trace('com.ibm.*=all=disabled')where:
$ Jacl operator for substituting a variable name with its value AdminControl object that enables the manipulation of MBeans running in a WebSphere server process trace 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 console.
Set up profile scripts to make tracing easier using scripting
Dump threads in server processes using scripting
Use the AdminControl object for scripted administration
Related Reference
Commands for the AdminControl object