WAS v8.5 > Script the application serving environment (wsadmin)Troubleshooting with scripting
Use these topics to learn more about troubleshooting with scripting. This topic contains the following tasks:
- Tracing operations using wsadmin.sh
- Configure traces using scripting
- Turning traces on and off in servers processes using scripting
- Dumping threads in server processes using scripting
- Set up profile scripts to make tracing easier using wsadmin.sh
- Enable the Runtime Performance Advisor tool using scripting
Example
We can set the trace string using either of the following supported formats. For example:
$AdminControl trace com.ibm.*=all=enabled
or$AdminControl trace com.ibm.*=all
For more instructions, see the tracing and logging information. To set the log level, see the log level settings information.
Subtopics
- Tracing operations using wsadmin.sh
We can enable and disable tracing with scripting and wsadmin.- Extracting properties files to troubleshoot the environment using wsadmin.sh
Use this topic to create a properties file that displays configuration information for a node, application server, application, or other resource. We can use this file to troubleshoot a problem in the environment.- Configure traces using scripting
Use wsadmin and scripting to configure traces for a configured server.- Turning traces on and off in servers processes using scripting
We can use scripting to turn traces on or off in server processes.- Dumping threads in server processes using scripting
Use the AdminControl object to produce a Java core dump, which includes the Java threads of a running server.- Set up profile scripts to make tracing easier using wsadmin.sh
We can use scripting and wsadmin to set up profile scripts to facilitate tracing.- Enable the Runtime Performance Advisor tool using scripting
We can configure the Runtime Performance Advisor (RPA) using wsadmin or the dmgr console.- AdministrationReports command group for AdminTask using wsadmin.sh
We can use the Jython or Jacl scripting languages to troubleshoot your configuration with wsadmin. The commands in the AdministrationReports group can be used to create a report of inconsistencies in the system configuration or a report that describes the port usage in the system.- Tracing operations using wsadmin.sh
We can enable and disable tracing with scripting and wsadmin.- Extracting properties files to troubleshoot the environment using wsadmin.sh
Use this topic to create a properties file that displays configuration information for a node, application server, application, or other resource. We can use this file to troubleshoot a problem in the environment.- Configure traces using scripting
Use wsadmin and scripting to configure traces for a configured server.- Turning traces on and off in servers processes using scripting
We can use scripting to turn traces on or off in server processes.- Dumping threads in server processes using scripting
Use the AdminControl object to produce a Java core dump, which includes the Java threads of a running server.- Set up profile scripts to make tracing easier using wsadmin.sh
We can use scripting and wsadmin to set up profile scripts to facilitate tracing.- Enable the Runtime Performance Advisor tool using scripting
We can configure the Runtime Performance Advisor (RPA) using wsadmin or the dmgr console.- AdministrationReports command group for AdminTask using wsadmin.sh
We can use the Jython or Jacl scripting languages to troubleshoot your configuration with wsadmin. The commands in the AdministrationReports group can be used to create a report of inconsistencies in the system configuration or a report that describes the port usage in the system.- Configure HPEL with wsadmin scripting
We can configure the High Performance Extensible Logging (HPEL) log and trace framework using wsadmin.sh. Use the examples in this topic as a guide to build our own wsadmin scripts.
Related
Use wsadmin scripting
Get started with wsadmin scripting
Reference:
Log level settings