Using the wsadmin command to set instrumentation levels

To set the overall instrumentation level to low for the server1 appserver, use the wsadmin set commands as shown in Example 16-1.

Example 16-1 Using wsadmin to set instrumentation levels

wsadmin> set perfObjRef [$AdminControl makeObjectName \

	[$AdminControl completeObjectName type=Perf,process=server1,*]]

wsadmin> set params [java::new {java.lang.Object[]} 2]

wsadmin> $params set 0 [java::new java.lang.String pmi=L]

wsadmin> $params set 1 [java::new java.lang.Boolean true]

wsadmin> set sigs  [java::new {java.lang.String[]} 2]

wsadmin> $sigs set 0 java.lang.String

wsadmin> $sigs set 1 java.lang.Boolean

wsadmin> $AdminControl invoke_jmx $perfObjRef setInstrumentationLevel \ 

	$params $sigs

The setInstrumentationLevel method call doesn't produce any output. You can use the Tivoli Performance Viewer as a quick way to check that the commands actually had an effect on the instrumentation level setting.

The string passed in as the first parameter to the setInstrumentationLevel method (here: pmi=L) specifies the instrumentation level setting (possible values are N, L, M, H, X). This string can hold the overall instrumentation level or a compound of instrumentation levels for each module and/or submodule like this:

java::new java.lang.String \

	beanModule=H:connectionPoolModule=H:jvmRuntimeModule=L:orbPerfModule=H

  Prev | Home | Next

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.

 

Tivoli is a trademark of the IBM Corporation in the United States, other countries, or both.