InfoCenter Home > 6.6.21: Performing tasks with the Resource AnalyzerThis section describes how to start the Resource Analyzer, how to set instrumentation levels, and how to enable data reporting with the Java Virtual Machine Profiler Interface (JVMPI). It also provides step-by-step instructions for monitoring data with the Resource Analyzer. It contains the following topics:
A full listing of all counters for all resource categories is shown in Performance data. Opening the Resource AnalyzerThe Resource Analyzer is included with WebSphere Application Server 4.0. You can access the Analyzer through the following menu options:
If the administrative server is not running, you can start the Resource Analyzer from the command line, for example, when you want to run the Analyzer in logging mode to view data from previously logged sessions. To start the Resource Analyzer from the command line, invoke a script provided in the bin directory where WebSphere Application Server is installed.
By default, the Resource Analyzer looks for the administrative server on the machine where the Analyzer is started. If the Resource Analyzer is running on a separate machine, you can start it from the command line, specifying the host and port number. For example, on Windows systems, use the following command: C:\> WebSphere\AppServer\bin\ra.bat [host_name [port_number]] Due to memory requirements, it is recommended that you run the Resource Analyzer on a separate machine from the administrative server. Setting the instrumentation levelUse the Performance Monitoring Settings dialog box to set instrumentation levels in the Resource Analyzer. The levels are set separately for each application server. You can access the Performance Monitoring Settings dialog box from within the Resource Analyzer or from the WebSphere Advanced Administrative Console. The access methods are discussed in the following topics:
In the Performance Monitoring Settings dialog box, perform the following steps to set the instrumentation level for a resource category:
Choosing an instrumentation level causes the same level to be applied recursively to all elements below the selected resource. To ensure that an instrumentation level is applied to the desired resource, expand the node and make sure that only the desired resource is selected before setting the level. The instrumentation level for any element below a resource can be selected and individually set to a different instrumentation setting. If the instrumentation level excludes a counter, that counter does not appear as an entry in the tables or charts in the Resource Analyzer. For example, if the instrumentation level is set to low on the Administrative Console, counters for that resource having a impact rating of medium or high are not displayed on the selection list in the Counter Selection panel of the Data Monitoring pane. Setting the level for individual enterprise bean methodsTo avoid the overhead cost of monitoring individual remote methods, individual methods in enterprise beans are not displayed in the performance panel unless the methods level is set to maximum. To display individual methods and specify their instrumentation levels, set the instrumentation level for the methods category to maximum by following the procedure described in Setting the instrumentation level. Close and reopen the Performance Monitoring Settings dialog box. Individual methods are now displayed, and you can set the method for individual methods. Note that only methods that have been called by an application are displayed. If a remote method has not been called since the application server was started, it does not appear in the performance panel. Setting the instrumentation level through the Resource AnalyzerThe instrumentation level for a resource category is set in the Performance Monitoring Settings dialog box. To open this dialog box from the Resource Analyzer, do one of the following:
Follow the instructions in Setting the instrumentation level to change the instrumentation levels. Alternatively, clicking a resource with an instrumentation level of none causes the Performance Monitoring Settings dialog box to open. To use this access method, follow these steps:
Setting the instrumentation level from the administrative consoleThe instrumentation level for a resource performance category is changed through the Performance Monitoring Settings dialog box. To access this dialog box from the WebSphere Advanced Administrative Console, perform the following steps:
Enabling JVMPI data reportingThe Resource Analyzer leverages a Java Virtual Machine Profiler Interface (JVMPI) to enable a more comprehensive performance analysis. This profiling tool enables the collection of information, such as data about garbage collection, about the Java Virtual Machine (JVM) that runs the application server. JVMPI is a two-way function call interface between the JVM and an in-process profiler agent. The JVM notifies the profiler agent of various events, such as heap allocations and thread starts. The profiler agent can activate or inactivate specific event notifications, based on the needs of the profiler. JVMPI supports partial profiling by enabling the user to choose which types of profiling information is to be collected and to select certain subsets of the time during which the JVM is active. JVMPI moderately increases the performance impact. This functionality is available on the Windows, AIX, and Solaris platforms. To enable JVMPI reporting for each individual application server, do the following on the Administrative Console of the WebSphere Application Server:
Displaying current dataThe following instructions describe how to display current performance data in the Data Monitoring pane.
Starting data retrievalTo start data retrieval, do the following:
If a new module or instance (servlet or JSP file) is loaded by WebSphere Application Server after the Resource Analyzer is started, perform the following steps to display performance data for a newly loaded servlet or JSP file:
Only default servlets, for example, the ErrorReporter servlet in the Default application server, have a the value for the Load at startup option set to true. The option is set to false for other servlets. To change this setting, follow these steps:
Stopping data retrievalTo stop data retrieval, do the following:
If you want to stop data reporting for all resources, click Actions --> Stop All. When a running application server is stopped in the administrative console, the Resource Analyzer icon for the server turns from green to red. In addition, data reporting for this server automatically stops, and icons for the server's resources turn red. Refreshing dataNew performance data can become available in either of the following situations:
In both cases, if the resource in question is already being polled by the Resource Analyzer (or the parent of the resource is being polled), the system is automatically refreshed. That is, if more counters are added for a group that the Resource Analyzer is already polling, the Resource Analyzer automatically detects this and adds the counters to the table or chart views. If the parent of the newly added resource is being polled, the new resource is detected automatically and added to the Resource Selection tree. Otherwise, the Resource Selection tree, or parts of it, can be refreshed manually by selecting the appropriate node and clicking the Refresh icon (or by right-clicking a resource and choosing Refresh). When an application server is running, the Resource Analyzer's tree is automatically updated with the server's local structure (its containers and enterprise beans) to reflect changes on the server. However, if a stopped server is started after the Resource Analyzer starts, a manual refresh operation is required so that the server's structure is accurately reflected in the Resource Selection tree. To query the administrative server for new resources or counters, do the following:
Note that the refresh operation is a local, not global, operation. It applies only to those resources that are selected. Also, the refresh operation is recursive; all subordinate (children) resources are also refreshed when a selected resource is refreshed. Getting current dataTo obtain the current values for all counters that belong to a resource:
The values are displayed independently of the refresh rate. The resource does not need to be running in order to get the values of the counters. Clearing values from tables and chartsAfter stopping a resource, you can use the Clear Values operation to remove remaining data from a table or chart. You can then begin populating the table or chart with new data. To clear the values currently displayed, do the following:
Resetting counters to zeroTo reset the start time for calculating aggregate data, do the following:
The reset operation sets the "clock" used for reporting aggregate data for counters of the selected performance category. Instead of reporting data from the time the server was started, reporting now begins from the time of the reset action. Not all counters can be reset. If you use the reset operation for a group containing counters which cannot be reset, the reset action has no effect. You can select multiple performance groups and reset them simultaneously. Viewing and modifying chart dataThe View Chart window displays a graph with time as the x axis and the performance value as the y axis. To view data in a chart, do the following:
The default scaling factor is 1. Negative results are displayed as zero (0). When selected counters are using measurement units that are not proportionally similar, the scaling factor can be set manually to enable a meaningful graphic display. See Scaling the chart display manually for information on manually scaling the graphic display for the View Chart window. Scaling the chart display manuallyYou can manually adjust the scale for counters so that the graphic displays enable meaningful comparisons between graphs of different counters. Follow these steps:
The View Chart display immediately reflects the change in the scaling factor. The possible values for the Scale field range from 0 to 100 and show the following relationships:
This value is reflected only in the View Chart window. Storing and replaying data from a log fileThe Resource Analyzer can be used to both store and view data saved in previous sessions.
Starting to record dataAll data being reported by the Resource Analyzer can be saved in a log file. The data is written to the log as serialized Java objects or as an XML document. To start recording data, do the following:
Stopping the recording of dataTo stop recording data, click Logging --> Off. Replaying a log fileOnly log files saved in binary format (*.lra) can be replayed by using the Resource Analyzer. To replay a log file, do the following:
By default, the data is replayed at the same rate it was collected (written to the log). If data was collected every minute, it is displayed every minute. You can change the speed at which the log is replayed by clicking Options --> Play Speed. If the data was collected every minute and the speed factor is set to 60x, then data is displayed every second. While replaying the log, you can choose different groups to view by selecting them in the Resource Selection pane. You can also view the data in either of the views available in the tabbed Data Monitoring pane. You can stop and resume the log at any point. However, data cannot be replayed in reverse. Changing the speed for replaying a logThe log speed is used to control how fast to replay a log file. The available speeds are 1x, 5x, 20x, and 60x. The 1x speed plays the log at the same speed at which the data was originally collected (written to the log). The 5x speed plays the log five times faster than the rate at which the data was collected, and so on. To change the log speed, do the following:
Rewinding the log fileTo rewind the log file, click Actions --> Rewind. Alternatively, use the Rewind icon on the toolbar. Changing display settingsYou can change several aspects of data monitoring. The following sections describe the possible changes:
Changing the View Data As settingThe View Data As setting determines whether counter values represent absolute values, changes in values, or rates of change. The meanings for these settings differ slightly depending on where you are viewing data. The choices follow:
Changing the refresh rateBy default, the Resource Analyzer retrieves data from the administrative server every 10 seconds. To change the rate at which data is retrieved from the server, do the following:
Changing the table sizeBy default, the View Data window displays 40 rows, corresponding to the values of the last 40 data points retrieved from the administrative server. To change the size of the table (number of rows displayed), do the following:
|
| ||
|