Enable the Runtime Performance Advisor tool using scripting

Enable the Runtime Performance Advisor tool using scripting

You can configure the Runtime Performance Advisor using the wsadmin tool or the console. Before starting this task, the wsadmin tool must be running. See the Start the wsadmin scripting client article for more information.

Overview

The Runtime Performance Advisor tool provides advice to help tune systems for optimal performance. See the Using the Runtime Performance Advisor article for more information on how to enable this tool using the console. The recommendations display as text in the SystemOut.log file.
The Runtime Performance Advisor (RPA) requires that the Performance Monitoring Service (PMI) is enabled. It does not require that individual counters be enabled. When a counter that is needed by the RPA is not enabled, the RPAr will enable it automatically. There is no MBean/object available for wsadmin to create a RPA configuration. You can use wsadmin to change the settings and make them effective at runtime. These changes will not be persisted. The changes remain until you stop the server. Since the RPA is disabled once you stop the server, you may want to disable the PMI Service or the counters that were enabled while it was active. You can enable the following counters using the Runtime Performance Advisor:
ThreadPools (module)
Web Container (module)
Pool Size
Active Threads
Object Request Broker (module)
Pool Size
Active Threads
JDBC Connection Pools (module)
Pool Size
Percent used
Prepared Statement Discards
Servlet Session Manager (module)
External Read Size
External Write Size
External Read Time
External Write Time
No Room For New Session
System Data (module)
CPU Utilization
Free Memory
The following provides an explanation for some of the settings used to:

Calculation interval PMI data - This setting is taken over an interval of time and averaged to provide advice. The calculation interval specifies the length of the time over which data is taken for this advice. Details within the advice messages will appear as averages over this interval.

Maximum warning sequence - This setting refers to the number of consecutive warnings issued before the threshold is relaxed. For example, if the maximum warning sequence is set to 3, then the advisor only sends three warnings to indicate that the prepared statement cache is overflowing. After that, a new alert is only issued if the rate of discards exceeds the new threshold setting.

Number of processors - This setting specifies the number of processors on the server. It is critical in order to ensure accurate advice for the specific configuration of the system.

To enable the Runtime Performance Advisor tool using the wsadmin tool, perform the following steps:

Procedure
Setup the Runtime Performance Advisor (RPA)...
Use Jacl:
set perf [$AdminControl queryNames mbeanIdentifier=ServerRuleDriverMBean2,process=server1,*] set enabledVal [java::new java.lang.Boolean true] set attr [java::new javax.management.Attribute enabled $enabledVal] set perfObject [$AdminControl makeObjectName $perf] set ObjectArray [java::new {java.lang.Object[]} 1] set sigArray [java::new {java.lang.String[]} 1]
$ObjectArray set 0 $attr
$sigArray set 0 "javax.management.Attribute"
$AdminControl invoke_jmx $perfObject setRPAAttribute $ObjectArray  $sigArray

$AdminConfig save
What to do next
After completing the previous steps, start the server and monitor RPA.

Use the AdminControl object for scripted administration

Related Reference

Commands for the AdminControl object

Related information

Use the Performance and Diagnostic Advisor