Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin) > Troubleshoot with scripting
Trace operations using wsadmin.sh
We can enable and disable tracing with scripting and the wsadmin tool.
See the topic about starting wsadmin.sh.
Use a trace command to trace operations.
Procedure
- Enable wsadmin client tracing.
### Jacl
$AdminControl trace com.ibm.*=all### Jython
AdminControl.trace('com.ibm.*=all')
where:
Disable wsadmin client tracing.
### Jacl
$AdminControl trace com.ibm.*=info### Jython
AdminControl.trace('com.ibm.*=info')
where:
Results
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.
The property com.ibm.ws.scripting.traceString can also be passed in as a javaoption through the command line. Passing the property through the command line changes the trace setting for the current session.
Enable Tracing wsadmin.sh -javaoption -Dcom.ibm.ws.scripting.traceString=com.ibm.*=all=enabledA 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.sh 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.
Start the wsadmin scripting client using wsadmin.sh
Enable trace on a running server
Turning traces on and off in servers processes using scripting
Configure traces using scripting
Set up profile scripts to make tracing easier using wsadmin.sh
Dumping threads in server processes using scripting
Use the wsadmin scripting AdminControl object for scripted administration
Related
Trace and logging configuration
Commands for the AdminControl object using wsadmin.sh