Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin) > Troubleshoot with scripting
Set up profile scripts to make tracing easier using wsadmin scripting
We can use scripting and wsadmin.sh to set up profile scripts to facilitate tracing.
See Start the wsadmin scripting client using wsadmin.sh for more information.
Procedure
Set up a profile script to make tracing easier. The following profile script example turns tracing on and off for server1:
### Jacl
proc ton {} { global AdminControl set ts [$AdminControl queryNames type=TraceService,node=mynode,process=server1,*] $AdminControl setAttribute $ts traceSpecification com.ibm.=all=enabled proc toff {} { global AdminControl set ts [$AdminControl queryNames type=TraceService,node=mynode,process=server1,*] $AdminControl setAttribute $ts traceSpecification com.ibm.*=all=disabled proc dt {} { global AdminControl set jvm [$AdminControl queryNames type=JVM,node=mynode,process=server1,*] $AdminControl invoke $jvm dumpThreads### Jython
def ton(): global lineSeparator ts = AdminControl.queryNames('type=TraceService,node=mynode,process=server1,*') AdminControl.setAttribute(ts, 'traceSpecification', 'com.ibm.=all=enabled') def toff(): global lineSeparator ts = AdminControl.queryNames('type=TraceService,node=mynode,process=server1,*') AdminControl.setAttribute(ts, 'traceSpecification', 'com.ibm.*=all=disabled') def dt(): global lineSeparator jvm = AdminControl.queryNames('type=JVM,node=mynode,process=server1,*') AdminControl.invoke(jvm, 'dumpThreads')
If you start wsadmin.sh with this profile script, you can use the ton command to turn on tracing in the server, the toff command to turn off tracing, and the dt command to dump the Java threads. For more information about running scripting commands in a profile script, see Start the wsadmin scripting client using wsadmin.sh.
Use the wsadmin scripting AdminControl object for scripted administration
Related
Commands for the AdminControl object using wsadmin.sh