Tracing operations with wsadmin
We can enable tracing with scripting and wsadmin.
Before starting this task, wsadmin must be running. See the Start wsadmin article for more information.
Perform the following steps to trace operations:
Enable wsadmin client tracing with the following command:
where:
Table 1. Syntax explanation
$ 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 indicates to turn on tracing
The following command disables tracing:
where:
Table 2. Syntax explanation
$ 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.*=info indicates to turn off tracing
The trace command changes the trace settings for the current session. We can change this setting persistently by editing 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 wsadmin with a value set for this property. It is possible to run without this property set, where all logging and tracing goes to the admin console.
Related tasks
Enable trace on a running server
Turning traces on and off in servers processes using scripting
Set traces using scripting
Set up profile scripts to make tracing easier using scripting
Dumping threads in server processes using scripting
Use AdminControl for scripted administration
Related
Tracing and logging configuration
Commands for AdminControl