|
Problem |
How to use the DrAdmin tracing feature that comes with WAS
4.0.x |
|
Solution |
Location:
- Windows: %WAS_ROOT%\bin\DrAadmin.bat
- Unix: %WAS_ROOT%/bin/DrAadmin.sh
Reasons to use DrAdmin:
- Allows "on the fly" tracing
- If Admin Console or other tracing facilities are
unusable/unresponsive
- Will not disrupt production system with continuous tracing
enabled
To trace AdminServer thru DrAdmin:
- Find DrAdmin port in the Tracefile (%WAS_ROOT%/logs)
- Specify trace setting:
- DrAdmin -serverPort xxxx -setTrace
zzzz=all=enabled
- Example: DrAdmin -serverPort 1234 -setTrace
com.ibm.*=all=enabled
- Once action traced is completed dump buffer:
- DrAdmin -serverPort xxxx -dumpRingBuffer
C:\temp\bufferdump.txt
- Disable tracing:
- DrADmin -serverPort xxxx -setTrace
zzzz=all=disabled
- View Trace
All available options are:
DrAdmin -usage
( -usage |
-help |
( -defaultConfiguration
[ -serverHost ( <host name> | 'localhost' ) ]
[ -server <server name> ] |
-configurationFile <file>
[ -serverHost ( <host name> | 'localhost' ) ]
[ -server <server name> ] |
-serverPort <port number>
[ -serverHost ( <host name> | 'localhost' ) ] )
[ -testConnection ]
[ -testVersions ]
[ -retrieveServerNames ]
[ ( -stopServer | -stopNode ) ] -- AEs ONLY
[ -retrieveTrace ]
[ -retrieveComponents ]
[ -setTrace <trace specification> ]
[ -setRingBufferSize <buffer size> ]
[ -dumpRingBuffer <file name> ]
[ -dumpState <dump specification> ]
[ -dumpThreads ]
[ -dumpConfig ( 'all' | 'server' ) ]
[ -retrieveConfig ( 'all' | 'server' ) ]
[ ( -list | -long | -isRunning )
[ -application <archive URL> [ -module <module URI> ]
[ -applicationOnly ] ]
[ ( -start | -stop | -restart ) -- AEs ONLY
[ -application <archive URL> [ -module <module URI> ] ]
These options are not case sensitive. |
|
|
|
|
|
|