Set up profile scripts to make tracing easier using scripting

 

Step for this task

Set up a profile script to make tracing easier. The following profile script example turns tracing on and off for server1:

• Start wsadmin

• 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 the wsadmin tool with this profile script, 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 the Starting the wsadmin scripting client article.

---

 

See Also

AdminControl object for scripted administration

 

See Also

Commands for the AdminControl object

 

---