Monitor WAS

Monitor WAS

+
Search Tips | Advanced Search

Organization of the predefined workspaces
Summary workspaces
Summary Workspace Views
WebSphere agent summary workspace
WebSphere agent summary status workspace
Application Server Summary and BPM Summary workspaces
Resources and Applications workspaces
Situation Mapping and Summary Workspaces
Summary Workspaces error messages
Configuration workspaces

Application Diagnostics Configuration - Basic Tab
Application Dashboard (Basic) tab
Collection Advanced tab
Application Dashboard (Auto Threshold) tab

Workspace link to managing server visualization engine

Grant users access to managing server visualization engine from monitoring portal
Access the managing server visualization engine from monitoring portal workspaces
Access the managing server visualization engine from the monitoring portal
Create links to the managing server visualization engine using the Link Wizard

Workspace link to ITCAM for SOA
Alarm Manager workspace
Allocation Failures workspace
Selected Application - Application Trend at L1 workspace
Selected Application - Application Trend at L2/L3 workspace
Application Health workspace
Application Registry workspace
BPM workspace
Cache Analysis workspace
Client Communications workspace
Container Object Pools workspace
Container Transactions workspace
Data sources workspace
DB Connection Pools workspace
DCS Stacks workspace
Destinations workspace
Durable Subscriptions workspace
EJB Containers workspace
Enterprise Java Beans workspace
Garbage Collections - Selected Allocation Failure workspace
Garbage Collection Analysis workspace
High Availability Manager workspace
IMAP/POP workspace
J2C Connection Pools workspace
JMS Summary workspace
JVM Stack Trend workspace
Log Analysis workspace
Lotus Workplace Server workspace
Messages Queues workspace
Messaging Engine Communications workspace
Messaging workspace
OS Stack workspace
Pool Analysis workspace
Portal Pages Summary workspace
Portal Summary workspace
Portlet Summary and Selected Portlet - History workspaces
Request Analysis workspace
Request Baseline workspace
EJB Tier Analysis workspace
Application Configuration workspace
Backend Tier Analysis workspace
Application Health History workspace
Web Tier Analysis workspace
Selected Datasources - Datasource Trend workspace
Selected Request - Datasources workspace
Selected Request - JMS Queues workspace
Selected Request - Portal Processing workspace
Selected Request - Resource Adapters workspace
Selected Request - Service Components workspace
Service Component Elements workspace
Selected Request - History workspace
Service Components workspace
Servlets/JSPs - Selected Web Application workspace
Scheduler workspace
Sessions workspace
Thread Pools workspace
Thread Pool Trend workspace
Web Applications workspace
Web Services workspace
WebSphere Agent workspace
WAS workspace
WebSphere ESB Server workspace
WebSphere Portal Server workspace
WMQ Client Link Communications workspace
WMQ Link Communications workspace
Workload Management workspace
Workplace Mail workspace
Region workspaces in a z/OS environment

Monitoring agent for WebSphere Application Server

The monitoring agent for WebSphere Application Server provides a Systems Management solution for the WebSphere application server Versions 7, 8 and 8.5. Using the agent, you can monitor multiple WebSphere Application Server servers running on the same physical node. Each application server must have been configured with its own ITCAM Data Collector for WebSphere.
The monitoring agent collects four types of data through the data collector embedded in the WebSphere Application Server process:

Data for application server requests from the ITCAM Data Collector for WebSphere
Resource data from WebSphere Performance Monitoring Infrastructure (PMI)
Data from WebSphere log files
Process data from the operating system

Initiating data collection and the reporting of data

Because of high processor usage, some data items are not automatically collected and reported. The collection of some data and statistics depends upon the setting of instrumentation levels for certain attributes. If the instrumentation levels are not set appropriately, certain information is not collected and displayed in the workspaces. Similarly, those attributes that collect request and application trace data require you to complete several configuration steps.

Automatic baselining

To display application health status, ITCAM monitors request response times (averaged over a sampling interval, by default 60 seconds) for every application. Every top-level request available in an application is monitored separately.
For every request, two thresholds are set, known as fair and bad. Response time below both thresholds is considered good. When at least one average request response time for an application rises over the fair threshold, a health warning (indicated with an exclamation mark symbol) for this application is reported. In the same way, when at least one average request response time rises over the bad threshold, an application health alarm (indicated with an x symbol ) is reported.
ITCAM also monitors the "nested" requests (for example, database calls) within every top-level request. In the event of a warning or alarm, it checks which of the nested requests is taking more than its usual share of time. Depending on the type of such nested requests, ITCAM shows whether the client, application, or backend tier is the likely cause of the warning/alarm. Servlet and Portal request types are assigned to the client tier; EJB and User (Custom) request types, to the application tier; all other request types (JNDI, JDBC, JCA, JMS) to the backend tier.
Baselining is currently not supported for SCA requests.
When ITCAM starts to monitor a new application, it automatically starts a baselining process. This process normally runs for seven days and provides updated information every hour from the beginning. During the process, ITCAM collects statistical data for all requests in this application. Once the data is collected, ITCAM sets the thresholds automatically; it also records the typical share of response time for each nested request type.
In most cases, this automatic setting is adequate. During the baselining process, the baselines get updated periodically, and the alarms/warnings start to correspond to real problems. There is no need to adjust baselining settings when things are working normally. (The automatic thresholds usually become usable earlier, after the application has been observed through its typical load patterns). To acquire thresholds, based on whatever data is available, before the hourly automatic update, you can manually update baselining.
However, in some situations the threshold levels can become inadequate. This results in either too many false alarms/warnings, or in real problems going undetected. Such situations can be broadly split into two categories:

If some time has passed since the baselining process for an application, its response times might have changed because of configuration alteration, database growth, changing load patterns, and so on. In this case, you might need to run the baselining process again. It is good practice to do it after any configuration or infrastructure change.
If the thresholds are incorrect immediately after the baselining process has been completed, you might have to adjust the auto threshold settings.

As a last resort, you can also override the thresholds with fixed values. However, do not do this unless you know a lot about the monitored application, or unless instructed by IBM Level 3 Support.
To have the thresholds set before they are updated automatically for the first time, you can trigger a baseline update. This immediately sets the thresholds based on the request data collected so far.

Workspaces

As part of the monitoring agent for WebSphere Application Server product integration with the IBM PureApplication System Monitoring Portal, workspaces offer views of monitoring data that provide detailed current data about WebSphere Application Server servers running on Linux, UNIX, and Windows platforms on your site. In addition to reports and graphs, a workspace can contain other views (that is, windows), such as a Notepad editor session, a browser session, a telnet session, an event console, or a Take Action view from which you can issue commands.

Several views of high-level information

Several workspaces provide high-level information to help you meet the monitoring and administrative needs of your site. These workspaces report on status and availability for both the WebSphere administrative server and its application server instances. They allow you to easily monitor the availability of your enterprise, the WebSphere Application Server, and application server instances.

Primary and secondary workspaces

The workspaces listed in the Navigator are directly accessible and are thus termed primary workspaces. Some of these also contain secondary workspaces, which are not accessible directly from the Navigator. Instead, you must select and display the primary workspace. Then, use either a menu option or a special link icon in the primary workspace views to reach the secondary workspaces (sometimes called subsidiary workspaces).

Workspaces with historical data links

Several workspaces provide secondary workspaces that display historical data. You can specify a time span over which to collect historical data, which accumulates and summarizes the data in the primary workspaces that generate them. (The default setting is 15 minutes; you can modify this setting to suit your needs.) The descriptions of the historical workspaces follow the descriptions of the primary workspaces that generate them in the workspace helps.

Available monitoring portal workspaces

For an overview of the organization of the available workspaces, see Organization of the predefined workspaces.

Organization of the predefined workspaces

The monitoring agent for WebSphere Application Server workspaces for the IBM PureApplication System Monitoring Portal define data displays that appear in the Navigator Physical view. In addition to the workspaces that the Navigator lists, you can reach their subsidiary (that is, secondary) workspaces from the primary workspaces (those listed in the Navigator).

Access the subsidiary workspaces

You can access the subsidiary workspaces of a primary workspace by using one or more of the following methods:

From the Navigator:

Select the primary workspace.
Right-click the name of the selected workspace in the Navigator.
Select Workspaces from the menu.
Select the desired subsidiary workspace.

From the View menu:

Select the primary workspace.
From the menu bar, select View > Workspaces.
Select the desired subsidiary workspace.

From a report:

Select the primary workspace.
If the workspace report contains a link icon, click the icon to navigate to the default subsidiary workspace pertaining to the selected row or right-click the icon and select a subsidiary workspace from the menu.

From a chart view:

The data displayed in some bar charts and plot charts is linked to subsidiary workspaces. To search for a link, right-click a bar or data point in the chart. If Link to displays in the menu, you can select a subsidiary workspace pertaining to the data in the chart.

Workspace organization

The hierarchy levels shown in the Navigator depend on how your enterprise customizes the IBM PureApplication System Monitoring Portal. However, monitoring agent for WebSphere Application Server does provide a set of predefined workspaces, which do not require customization. The following list shows the order and hierarchy of the predefined workspaces provided by the monitoring agent for WebSphere Application Server. It is a representation of how the predefined workspaces are organized in the Navigator.
Some workspaces are only available when running a monitoring agent in a z/OS environment. For more information, see Region workspaces in a z/OS environment.

Summary workspaces

You can use summary workspaces to quickly see the status of WebSphere application servers and applications in your enterprise.
Summary workspaces provide a way to quickly monitor the status of application servers and applications. ITCAM for Application Diagnostics provides predefined situations that you can use to monitor WebSphere application servers in your enterprise. Summary workspaces enable you to quickly determine the status of these situations. User-defined and predefined situations are mapped to various colored icons in the summary workspaces. The icon color indicates status which enables you to quickly determine the overall health of applications servers and applications. The following organization chart shows the structure of the icons in the summary workspaces:

Summary Workspace Icons

In summary workspaces, each icon displays as one of the following statuses: Critical, Warning, Normal, or Unknown. The status is calculated based on the status of the underlying situations being monitored. Each icon also displays the metrics for the first two situations shown on the flyover. The following table shows the possible status of icons:

Status Icons

Status Icon Status

Critical

Warning

Normal

Unknown or Application Stopped

Summary Workspace Flyovers

The icons indicate the status of the WebSphere application servers and applications in your enterprise. To access more detailed information from the summary workspaces, point to the icon and a flyover is displayed. The flyover provides relevant metrics pertaining to the icon. It also shows the top 10 situations that are linked with the icon. You can go directly to the situation event result workspace by clicking the situation link icon in the flyover.

Drill Down on Summary Workspaces

You can drill down on the icons to see more information. When you double-click an icon, further workspace views showing more detailed monitoring data are displayed.

Summary Workspace Views

You can use summary workspaces to quickly see the status of WebSphere application servers and applications in your enterprise. Each workspace can contain one or more views.

There are five summary workspaces. The following table describes the summary workspaces:

Summary Workspace Table

Workspace Name Level in TEP Views Available
WebSphere Agent Summary Agent level

Application Servers Status Table
Application Servers Summary

WebSphere Agent Summary Status Agent level

Application Servers Status
Application Servers Summary

application server Summary application server Level

application server - Resources
application server - Applications

Resources application server Level

application server - Resources
Situation Event Console

Applications application server Level

application server - Applications
Situation Event Console

WebSphere agent summary workspace

The WebSphere Agent Summary Workspace provides summary monitoring information for WebSphere application servers in your enterprise. It contains two views, the Application Servers Status Table view and the Application Servers Summary view.

Application Servers Status Table view

Two icons are displayed in this view: the Application and the Resources icons.
The flyover for the Applications icon displays the following metrics:

application server Name
Average Response Time (ms)
Request Rate (Req/Sec)
Error Rate (Errors/sec)
Number of problem Situations
List of top 10 situations
The flyover for the Resources icon displays the following metrics:

application server Name
JVM CPU%
GC Active Time (ms)
Number of problem Situations
List of top 10 situations

WebSphere agent summary status workspace

The WebSphere Agent Summary Status workspace is an alternative summary workspace available at the WebSphere agent level. The WebSphere Agent Summary Status workspace provides summary monitoring information for WebSphere Application servers.
To switch to the WebSphere Agent Summary Status workspace, right-click the WebSphere Agent in the monitoring portal navigator and select Workspace and then select WebSphere Agent Summary Status.
The WebSphere Agent Summary Status workspace contains two views, the Application Servers Status view and Applications Servers Summary view.

Application Servers Status View

In this view, the Server icon indicates the status of both applications and resources. The flyover for the Server icon displays the following metrics:

Average Response Time (ms)
Request Rate (Req/Sec)
Error Rate (Errors/sec)
JVM CPU%
GC Active Time (ms)
WAS Node Name
WAS Cell Name
WAS Cluster Name
Number of Problem Situations
List of top 10 situations

Application Server Summary and Business Process Manager Summary workspaces

The Application Server Summary workspace provides summary monitoring information for a WebSphere Application Server. The Business Process Manager Summary workspace provides summary monitoring information for a Business Process Manager Server. These workspaces are identical and contain two views: the Application Server - Resources view and the Applications Server - Applications view.

Application server - Resources View

The Application server - Resources view contains the following icons:

OS
JVM
Datasource
Threadpool
Services
If ITCAM for SOA is installed on the monitored Business Process Manager server, right-click any resource and select Operation Flow for Application Server to view the Operation Flow for Application Server workspace, provided by ITCAM for SOA. In this workspace, you can see the topology for all components running on the server.

OS icon

The OS icon provides summary metrics for machine CPU and paging metrics. The flyover for the OS icon displays the following metrics:

System CPU (ms)
System Paging Rate (Kbytes/sec)
Number of problem situations
List of top 10 situations
When you double-click the OS icon, the following subsidiary views display in the OS Stack workspace:

Current OS stack summary
CPU used
System Paging
For further information about the OS Stack workspace, see OS Stack

JVM icon

The JVM icon flyover provides summary metrics for: CPU for the JVM process, garbage collection, and heap metrics. The flyover information for the JVM icon displays the following metrics:

JVM CPU%
GC Active Time (ms)
List of top 10 situations
When you double-click the JVM icon, the following subsidiary views display in the JVM Stack Trend workspace:

JVM CPU Trend
Percent GC time used
Heap Usage trend
For further information about the JVM Stack Trend workspace, see JVM Stack Trend

Datasources icon

The Datasources icon flyover provides summary metrics for JDBC, JMS, JCA, and JTA, it also indicates the number of problem situations. When you double-click the Datasource icon, the following subsidiary views display in the Datasources workspace:

Worst Datasource Query Times
Worst Datasource Update Times
Datasources - Current Interval

Threadpool icon

The Threadpool icon flyover provides summary metrics for threadpool information including the number of problem situations. When you double-click the Threadpool icon, the following subsidiary views are displayed in the Threadpools workspace:

Highest Average Pool Sizes
Average thread pool usage
Threadpools table

Services icon

The Services icon flyover provides summary metrics for web services, Workload Management, and System Integration Bus. When you double-click the Services icon:

for Portal, Services icon takes you to web Services which has the following views:

Worst Response Times
Most Popular
Web Services
Web Service Gateway

for Lotus, the Services icon takes you to Workload Management which has these views:

WLM Server Incoming Requests
WLM Client Outgoing Requests
Workload Management Server
Workload Management Client

Application server - Applications View

In this view, there is an icon per application. The flyover for an Application icon displays the following metrics:

Average Response Time (ms)
Request Rate (Req/Sec)
Error Rate (Errors/sec)
Monitor Level
Number of problem Situations
List of top 10 situations
If ITCAM for SOA version 7.2 is installed on the monitored Business Process Manager server, right-click any application and select Selected Application - Group Summary to view the Group Summary workspace, provided by ITCAM for SOA. In this workspace, you can see the status of all process groups that include any components or operations that are a part of the selected application.
When you double click an Application icon, the following subsidiary views are displayed in either the Application Trend at L1 or Application Trend at L2/L3 workspace:

Response Time Trend
Error Rate Trend
Request Rate Trend
Selected Application Summary: Application Name
For further information about the Application Trend workspace, see Selected Application - Application Trend at L1 workspace, and Selected Application - Application Trend at L2/L3 workspace

Application Server Summary and Business Process Manager Summary workspaces

To access the workspaces, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, click a WebSphere Application Server or Business Process Manager entry.

Resources and Applications workspaces

The Resources and Applications workspaces provide monitoring data for your application server.

Resources Workspace

To access the Resources workspace, right-click the application server node in the monitoring portal navigator and select Workspace and then select Resources. The Resources workspace contains the following views:

Application Servers Resources
Situation Event Console
For information about the Application Servers Resources view, see Application Server Summary and Business Process Manager Summary workspaces. The Situation Event Console displays additional detail for all open situations. For details on how to perform filtering on open situations, see Tivoli Monitoring help.
If ITCAM for SOA is installed on the monitored Business Process Manager server, right-click any resource and select Operation Flow for Application Server to view the Operation Flow for Application Server workspace, provided by ITCAM for SOA. In this workspace, you can see the topology for all components running on the server.

Applications Workspaces

To access the Applications workspace, right-click the application server node in the IBM PureApplication System Monitoring Portal navigator and select Workspace and then select Applications. The Applications workspace contains the following views:

Application Servers Applications
Situation Event Console

If ITCAM for SOA is installed on the monitored Business Process Manager server, right-click any application and select Selected Application - Group Summary to view the Group Summary workspace, provided by ITCAM for SOA. In this workspace, you can see the status of all process groups that include any components or operations that are a part of the selected application.

Situation Mapping and Summary Workspaces

User-defined situations are mapped to icons in summary workspaces. When you create a situation, if the situation then triggers an alert, detail of the situation is displayed in one of the summary workspaces icon flyovers.
When you create a situation, the attribute group you base the situation on determines which summary workspace icon flyover the situation displays in. The following table shows which attribute groups map to which icons and predefined situations :

Mapping of attribute groups to predefined situations

Tivoli Enterprise Monitoring Agent Attribute Group Name Icons Predefined Situations
Applications Monitoring Configuration N/A WASAppDiscovered
Requests Monitoring Configuration N/A
Baseline N/A
Applications Health Status Applications WASApplicationBad, WASApplicationFair, WASApplicationGood
Applications Server Status JVM
Log Analysis JVM WASError
KYN Command N/A
WebSphere Agent Events N/A
DC Messages WebSphere JVM
Dynamic Cache Services
Dynamic Cache Templates Services
Workload Management Client Services
Workload Management Server Services
DB Connection Pools Datasources WASDBConnectionPoolThrdTimeout WASDBConnectionPoolUsageMaxed WASDBConPAverageUsageTimeHigh WASDBConPAvgWaitTimeHigh
Container Object Pools Threadpools
Enterprise Java. beans Applications WASEJBCreateTimeHigh WASEJBMethodResponseTimeHigh WASEJBRemoveTimeHigh
Web Applications Applications WASWebApplicationError
Web Applications - Sessions Applications WASSrvlSessAvgActiveSessionHigh WASSrvlSessExtReadTimeHigh WASSrvlSessExtWriteTimeHigh
Applications Server JVM, OS WASHighCPUPercentUsed
EJB Containers Applications
Servlets JSPs Applications WASServletsJSPError
Servlet Sessions Applications
Thread Pools Threadpools WASThreadPoolPercentMaxed WASThreadFreeLow
Container Transactions Datasources WASContainerTransactionRollback WASCTGlbTransDurationHigh WASCTLclTransDurationHigh
J2C Connection Pools Datasources WASJ2CConnectionPoolUsageMaxed WASJ2CCPAverageUsageTimeHigh WASJ2CCPAvgWaitTimeHigh
DCS Stack
High Availability Manager
Web Services Gateway
Web Services
Alarm Manager
Scheduler Services
Client Communications Services
Durable Subscriptions Services
Messaging Engine Communications Services
Messaging Engines Services
Queue Services
Service Component Elements Services
Service Components Services
Topic Spaces Services
WMQ Client Link Communications Services
WMQ Link Communications Services
Workplace Mail Service Datasources
Workplace Mail Queues Datasources
Workplace Mail IMAP/POP Services
Portal Summary Services
Portal Page Summary Services WASPortalPageResponseTime
Portlet Summary Services WASPortletResponseTime
Datasources Services WASDataSrcConWaitTimeHigh
Request Times and Rates Applications WASHighResponseTime
Request Analysis Applications WASReqSQLExecuteTimePercentHigh WASReqSQLQueryTimePercentHigh WASReqSQLUpdateTimePercentHigh
JMS Summary Datasources
Selected Request Applications
Garbage Collection Analysis JVM
WASHighGCTimePercent
WASAvgHeapSizeAfterGCHigh
Allocation Failure JVM WASOutofHeapSpace
Garbage Collection Cycle JVM
WebSphere Agent WASNotConnected
WebSphere App Server WASHighCPUPercentUsed WASHighResponseTime
Where NA is indicated for the icon, it means that situations created based on these attribute groups are not reported in the summary workspaces. This is because these tables are strictly related to monitoring agent configuration parameters that do not reflect the application or application server health.
For more information, see: WebSphere Agent attributes

Summary Workspaces error messages

Four possible error messages can be displayed in the summary workspace status bar.
The following table lists and explains the error messages:

Summary Workspaces error messages

Error Message Explanation
Internal Communication Error This message indicates a communication problem between the summary workspaces front end and the summary workspaces back-end code (called evaluator) running inside the embedded WebSphere server on the monitoring portal server. This error displays for two reasons:

If this error message is displayed for only some of the summary workspaces, turn up tracing and send to IBM support for review.

Invalid Data This message indicates that data being sent from the summary workspaces back-end code (called evaluator) running inside the embedded WebSphere server on the monitoring portal server is malformed. Turn on the tracing, collect the logs, and send to IBM support for further analysis.
No Applications Configured This message indicates that no applications are configured on the WebSphere server. This message also displays if the WebSphere server is not connected to the monitoring agent. The message no longer displays when the WebSphere server is back online. No user action is needed.
No Applications Servers Connected This message indicates that no WebSphere servers are connected to the monitoring agent. The message is no longer displayed when the WebSphere server is back online. No user action is needed.

10. Configuration workspaces

Monitor Agent configuration and tuning is facilitated in the monitoring portal through configuration workspaces. There are two configuration workspaces: one for the Monitoring Agent level and one for the server level:

WebSphere Agent Configuration workspace
application server Configuration workspace

Both configuration workspaces have the same tabs and configuration settings.
The WebSphere Agent Configuration workspace settings are initial settings applied to all data collectors managed by the Monitoring Agent. For example, when a data collector connects to the Monitoring Agent for the first time or if the data collector configuration was deleted. In both these examples, the configuration settings specified in the WebSphere Agent Configuration workspace are applied.
The application server Configuration workspace contains individual server settings and the settings in this workspace override the settings in the WebSphere Agent Configuration workspace.
Sets for the WebSphere Agent Configuration and application server Configuration workspaces are saved in the following files:

Workspace configuration files

Workspace Configuration file
WebSphere Agent Configuration workspace in windows: CANDLE_HOME\TMAITM6\hostname_productcode.xml
application server Configuration workspace in windows: CANDLE_HOME\TMAITM6\hostname_productcode_servervendor.servernode.server name.xml
WebSphere Agent Configuration workspace in other platforms: CANDLE_HOME/config/hostname_productcode.xml
application server Configuration workspace in other platforms: CANDLE_HOME/config/hostname_productcode_servervendor.servernode.server name.xml

The WebSphere Agent Configuration workspace configuration settings are initial settings which are applied to all data collectors managed by the selected WebSphere agent. The application server Configuration workspace configuration settings override agent level configuration settings.
Both configuration workspaces have the following two views:

Application Diagnostics Configuration view - this view has the following four tabs

Collection (Basic)
Collection (Advanced)
Application Dashboard (Basic)
Application Dashboard (Auto Threshold)

Application Servers view - this view has one tab which lists all application servers monitored by the selected WebSphere agent, for each application server, there is a link to application server Configuration workspace.

10.1. Application Diagnostics Configuration - Basic Tab

The Basic tab contains the following fields:

Request Data Monitoring - in this field, specify the monitoring level for requesting data from connected data collectors. The following values can be entered into this field:

Disable - request data is not monitored and is not displayed
Level 1 - only monitors edge request data, for example, servlets, JSPs, EJBs, SCA requests, and web service requests
Level 2 - monitors nested request data in addition to edge request data, for example, JNDI, JMS, JDBC, and JCA requests

This monitoring level is applied by default to newly discovered applications. However, you can set the monitoring level for any operation separately, using the Set_Application_Monitoring: Set monitoring Take Action command.
Request Data Monitoring Method - in this field, specify the monitoring method used by the Monitoring Agent to govern when it uploads request and garbage collection data from connected data collectors. The following values can be entered into this field:

On Demand - when the monitoring method is set to On Demand, data is uploaded only when requested by the user. The exception to this is if the cache of data is still current. Whether this data is current is determined by the Request Data On Demand Maximum Sample Age (sec) field in the Collection Advanced tab. With On Demand monitoring, the Tivoli Enterprise Portal response time is slower because the data is collected as requested. However, the retrieved data is the most current available. CPU and memory usage on the monitored systems is lower for On Demand monitoring.
Fixed Interval - when the monitoring method is set to Fixed Interval, the Monitoring Agent will upload sample data from the data collectors at regular fixed intervals, and respond to a user request using the latest cache of sample data gathered at the last interval. With Fixed Interval monitoring, CPU and memory usage can be higher because more data is collected more frequently but monitoring portal response time is faster as the data is more readily available. Data samples are calculated for the same time interval and as a result are more consistent.

Resource Data Monitoring - in this field, specify whether resource data is monitored from connected data collectors. The following values can be entered in this field:

Disable - resource data is not collected by the Monitoring Agent and is not displayed in the monitoring portal.
Enable - resource data is collected by the Monitoring Agent and is displayed in the monitoring portal.

Resource Data Monitoring Method - in this field, specify the monitoring methodology used by the agent to govern when it uploads resource data from connected data collectors. The following values can be entered into this field

On Demand - when the monitoring method is set to On Demand, data is uploaded only when requested by the user. The exception to this is if the cache of data is still current. Whether this data is current is determined by the Resource Data On Demand Maximum Sample Age (sec) field in the Collection Advanced tab. With On Demand monitoring, the Tivoli Enterprise Portal response time is slower as the data is collected as requested. However, the retrieved data is the most current available. CPU and memory usage on the monitored systems is lower for On Demand monitoring.
Fixed Interval - when the monitoring method is set to Fixed Interval, the Monitoring Agent will upload sample data from the data collectors at regular fixed intervals, and respond to a user request using the latest cache of sample data gathered at the last interval. With Fixed Interval monitoring, CPU and memory usage can be higher because more data is collected more frequently but monitoring portal response time is faster as the data is more readily available. Data samples are calculated for the same time interval and as a result are more consistent.

Garbage Collection Monitoring - in this field, specify if verbose garbage collection output monitoring is enabled. The following values can be entered in this field:

Disable - verbose garbage collection output data is not collected by the Monitoring Agent and is not displayed in the Tivoli Enterprise Portal.
Enable - verbose garbage collection output data is collected by the Monitoring Agent and is displayed in the Tivoli Enterprise Portal.

10.2. Application Dashboard (Basic) tab

The Application Dashboard (Basic) tab contains the following fields:

Application Fair Completion Rate Threshold (%) - Defines the default completion percentage for application fair availability threshold.
Application Bad Completion Rate Threshold (%) - Defines the default completion percentage for application bad availability threshold.
Application Fair Resource Usage Threshold (%) - Defines the threshold percentage for fair usage level of an application resource.
Application Bad Resource Usage Threshold (%) - Defines the threshold percentage for bad usage level of an application resource.
Application Resource Usage Monitoring Cutoff Threshold (%) - Defines the cutoff threshold percentage for application resources usage monitoring.
Request Monitoring Control Level - Specifies the request monitoring control level for the server. The following entries can be entered to this field:

Application Request monitoring settings are defined for each application independently.
Server Request monitoring settings are defined on the server level

The Request Monitoring Control Level option gives you more control over request monitoring settings. In certain sequences, you can benefit from locking the request monitoring control on the server level, because you can change data collector monitoring level in one place.
In ITCAM For Application Diagnostics, the request data monitoring level (Level1 or Level2) that displays on the monitoring portal depends on the Request Monitoring Control Level setting you choose.

If you select the Request Monitoring Control Level as Application (the default setting), the monitoring level is set separately for every application. For a newly discovered application, the current monitoring level for the agent is applied. Therefore, to display Level2 data for an application in the monitoring portal, you must set the monitoring level for the application using the Set_Application_Monitoring: Set monitoring Take Action command.
If you select the Request Monitoring Control Level as Server, the level is set for the server and affects all applications. If you set the Request Data Monitoring Level at Level2 using the Start_Request_Monitoring : Begin reporting request data Take Action command, the Request Data Monitoring Level for all the applications in this server is Level2. While you can still use the Set_Application_Monitoring Take Action command to set the monitoring level for an individual application, the level does not apply as a server-wide level is in operation. To apply the levels set for individual applications, change the Request Monitoring Control Level setting to Application.

10.3. Collection Advanced tab

The Collection Advanced tab contains the following fields:

Request Data On Demand Maximum Sample Age (sec) - The maximum allowed age of sample request data in seconds before collecting a new sample of data. If the monitoring method is set to On Demand, when a user request is received, and the current sample cache is older than the value specified, then the Monitoring Agent uploads a new sample before servicing the request. Two successive on-demand requests received from users within the period specified by the maximum sample age return the same results without incurring the CPU and memory cost of a new data sample.
Request Data Fixed Interval between Collections (sec) - The amount of time in seconds between uploads of sample request data from the data collectors to the Monitoring Agent when the monitoring method is set to Fixed Interval. When a user request is received, it is serviced from the latest uploaded sample.
Request Data Sampling Rate (%) - The percentage of requests that are sampled for request data monitoring.
Resource Data On Demand Maximum Sample Age (sec) - The maximum allowed age of sample resource data in seconds before collecting a new sample of data. If the monitoring method is set to On Demand, when a user request is received and the current sample cache is older than the value specified in this field, then the Monitoring Agent uploads a new sample before servicing the request. Two successive on-demand requests received from a user within the period specified by the maximum sample age return the same results without incurring the CPU and memory cost of a new data sample.
Resource Data Fixed Interval between Collections (sec) - The amount of time in seconds between uploads of sample resource data from the data collectors to the agent. When an monitoring portal request is received, it is serviced from the latest uploaded sample.
Garbage Collection Polling Interval (sec) - The interval in seconds between the Monitoring Agent scanning the verbose Garbage Collection output.
Log Scan Polling Interval (sec) - The interval in seconds between the Agent scanning the application server standard output log for changes.

10.4. Application Dashboard (Auto Threshold) tab

The Application Dashboard (Auto Threshold) tab contains the fields:

Response Time Selection (%) - Defines the percentage from baseline to be used for response time auto-thresholding.
Response Time Deviation (%) - Defines the deviation for baseline selection to be used for response times auto-thresholding.
Fair Response Time Projection (%) - Defines the percentage to derive the fair response time threshold from the baseline selection.
Bad Response Time Projection (%) - Defines the percentage to derive the bad response time threshold from the baseline selection.

Workspace link to managing server visualization engine

With the appropriate configuration and permissions, you can access the managing server visualization engine from specific workspaces in the monitoring portal. Instead of opening another browser and clicking the relevant link, you can access the managing server visualization engine from monitoring portal using a link called Diagnostic Server Activity Display. Some of the workspaces have additional links you can use to access the managing server visualization engine. All these links begin with the word Diagnostic. When you log in to the Welcome to the Application Monitor page, the information displayed is specific to the content in the monitoring portal workspace you selected. You also can manually create your own links to the managing server visualization engine using the Link Wizard, which is available on all workspaces.
To use this functionality, you need ITCAM for Application Diagnostics Managing Server.
You can access the managing server visualization engine from the following workspaces.

WebSphere Agent
Request Analysis
Garbage Collection Analysis
Datasources
JMS Summary
Web Applications
EJB Containers
DB Connection Pools
J2C Connection Pools
Thread Pools

Here is a list of the managing server visualization engine links available from the workspaces:

Diagnostic Server Activity display. Use this link to diagnose application problems, for example, slow transactions or high response times. This link is available from all workspaces except Request Analysis and Garbage Collection Analysis.
Diagnostic In-Flight Request Search. Use this link to identify any hanging transactions. This feature is only available from the WebSphere Agent and Request Analysis workspaces.
Diagnostic Recent Completed Requests. The Recent Requests tab displays data regarding recently completed server requests. This feature is only available from the Request Analysis workspace.
Diagnostic SMF Data. This feature is only available you are using a z/OS data collector and in the Request Analysis workspace. The SMF Overview displays summary information for all the resources on the selected application server.
Diagnostic JVM Thread Display Use this link to diagnose application problems, for example, slow transactions by examining threads running in JVM. This link is available from the Thread Pools workspace.
Diagnostic Memory Leak Use this link to diagnose memory leak problems. This link is available from the Garbage Collection Analysis workspace.

For information about accessing workspaces, see Accessing the managing server visualization engine from monitoring portal workspaces.

Prerequisites for access

The following conditions must be met to gain access to the managing server visualization engine through the monitoring portal.

ITCAM for Application Diagnostics managing server and ITCAM Data Collector for WebSphere must be installed in your environment.
Tivoli Enterprise Portal users must be members of the Diagnostic Users Group within the monitoring portal. For more information, see Granting users access to managing server visualization engine from monitoring portal.
During the installation of the managing server, kernel properties in the managing server must be set up accordingly with the correct host name and port number. This action is completed by the user installing the managing server.
You can also create your own links to the managing server visualization engine using the Link Wizard.
For more information, see Creating links to the managing server visualization engine using the Link Wizard

Kernel Settings to access the managing server visualization engine through the monitoring portal

If users access the managing server visualization engine through the monitoring portal, the kernel properties in the managing server must be set up accordingly with the correct host name and port number.
The following properties must be added to kl1.properties and kl2.properties (By default, the managing server installer replaces @{HOST_VE} and @{PORT_VE_HTTP} at managing server installation time) :

ve.host=@{HOST_VE}
ve.port=@{PORT_VE_HTTP}
At kernel startup time, the kernel must read these two properties and set them as part of properties in PROBE_CONFIG.PROPS. If a user changes the VE host name or port number, then the kernel needs to be restarted. Use the following steps to start and stop the kernel In $MS_HOME/bin:

To start kernel, issue:./amctl.sh wd<kernel count> start
To stop kernel, issue: ./amctl.sh wd<kernel count> stop
where <kernel count> is 1 by default.

11.1. Grant users access to managing server visualization engine from monitoring portal

As a user, you must be set up as a member of the DIAGNOSTIC USERS group in the monitoring portal, otherwise you cannot access the visualization engine from the monitoring portal. The default administration user Sysadmin is automatically a member of this group. Any user with administrator permissions can add or remove additional users to the DIAGNOSTIC USERS group. To complete this task you must be a user with administrator permissions to add or remove additional users to the DIAGNOSTIC USERS group. For more information about access, see Prerequisites for access.

Procedure

From the monitoring portal main menu, click Edit > Administer Users.
In the Administer Users window, click the Users Groups tab.
Click the group name, in this case DIAGNOSTIC USERS.
Click the Members tab to view existing members of this group and to assign additional users.
To add users, in the Available Members section, select the users to assign to the Group.
Click the left arrow to move the selected users to the Assigned Members section of the window.
Click Apply and OK to implement the changes.
To remove a user from the group, click the Assigned Members tab, and select the users to remove.
Click the right arrow to move the selected users to the Available Members tab. Then click Apply and OK.

What to do next
Users who are members of this group can access the managing server visualization engine from the monitoring portal. See Accessing the managing server visualization engine from monitoring portal workspaces.

Add the LDAP user to monitoring portal user accounts

About this task

To add the LDAP user to monitoring portal user accounts, use monitoring portal user administration.
In the monitoring portal main menu, select Administer Users.
Click Create New User to create a user profile from defaults, or Create Another User to create a user profile as a copy of an existing one.
In the Modify User window, enter the user name for the new user in the User ID field.
In the Distinguished Name field, enter the following string:
uid=username,cn=users,dc=ibm,dc=com
This string registers the LDAP user with monitoring portal. If you are using an existing LDAP configuration, use the applicable distinguished name.
11.2. Access the managing server visualization engine from monitoring portal workspaces

Use the following links for information about how to access the managing server visualization engine from the monitoring portal workspaces.
To ensure that you have access to the managing server visualization agent, see ">Prerequisites for access before you begin.

11.3. Access the managing server visualization engine from the monitoring portal

You can access the managing server visualization engine from links in the monitoring agent for WebSphere Application Server workspaces.
When you access the managing server visualization engine in this way, the managing server visualization engine displays in a browser view in a workspace. The monitoring portal navigation tree is automatically hidden in the workspace. To show or hide the monitoring portal navigation tree, click the small black arrow.
The following table displays a list of monitoring portal workspaces that have links to the managing server visualization engine.

monitoring portal workspaces that have links to managing server visualization agent

Workspace: Table View Name Number of links to managing server visualization agent Link Name Link Target Pages managing server visualization agent Pre-populated information in the link page to managing server visualization engine

WebSphere Agent Summary Status > Application Servers
WebSphere Agent Summary Status > Application Servers
WebSphere Agent Configuration > Application Servers
2

Diagnostic Server Activity Display
Diagnostic In-Flight Request Search

Server Activity Display . Active Requests
In-Flight Request Search

The Group Server drop-down menu is pre-populated based on data collector information from monitoring portal workspace.
OS Stack >Current OS Stack Summary 3

Diagnostic Server Activity Display
Diagnostic In-Flight Request Search
<platform OS> <platform> is one of the following operating systems: Linux, UNIX, Windows or z/OS

Server Activity Display . Active Requests
In-Flight Request Search
Use the dynamic workspace link to the corresponding OS agent workspace. For z/OS, the link is to OMEGAMON XE for z/OS.

The Group Server drop-down menu is pre-populated based on data collector information from Tivoli Enterprise workspace.
JVM Stack Trend >JVM Stack Trend 1 Diagnostic Memory Leak Memory Leak Analysis The Group Server drop-down menu is pre-populated based on data collector information from Tivoli Enterprise workspace.
Request Analysis > Requests . Current Interval 3

Diagnostic Recent Completed Requests
Diagnostic In-Flight Request Search
Diagnostic SMF Data (z/OS only)

Server Activity Display . Recent Requests
In-Flight Requests
SMF Data (for z/OS data collectors only)

The Group Server drop-down menu is pre-populated based on data collector information from Tivoli Enterprise workspace.
Content in Request Detail column of Requests table view in monitoring portal is pre-populated in the following fields:

Recent Requests: Client Request
In-Flight Request Search: Search Request/Transaction field

Garbage Collection Analysis >Garbage Collection Analysis
1 Diagnostic Memory Leak Memory Leak Analysis The Group Server drop-down menu is pre-populated based on data collector information from monitoring portal workspace.

Thread Pools >Thread Pools
1 Diagnostic JVM Thread Display JVM Thread Display The Group Server drop-down menu is pre-populated based on data collector information from monitoring portal workspace.

Datasources > Datasources . Current Interval
Web Applications >Web Applications
EJB Containers >EJB Containers
JMS Summary >JMS Summary . Current Interval
DB Connection Pools > DB Connection Pools
J2C Connection Pools > J2C Connection Pools
1 Diagnostic Server Activity Display Server Activity Display . Active Requests The Group Server drop-down menu is pre-populated based on data collector information from monitoring portal workspace.

The Server Group feature that displays applies to the managing server visualization engine. When you access any of these pages from the monitoring portal, the information in the Groups and Servers fields is automatically populated based on the data collector associated with the link and workspace you selected in the monitoring portal.
Groups are a set of application servers which have similar functionality. All configured data collectors are automatically in the Unassigned Servers Group. The relationship between Server Group and data collector is many to many. A data collector can belong to one or more server groups. A server group can have one or more data collectors. You can add data collectors to groups using the Server Management functionality in the managing server visualization engine.
The Server Activity Display section has three tabs.

Active Requests: provides real-time request or transaction data for an application server at the time the page displays.
Recent Requests: displays the last 100 or less completed request or transaction data for an application server.
Lock Contentions: displays requests that are hanging because they are waiting on a lock. The data shows data that is currently locked and the item that is waiting to be locked.

The Active Requests tab and the Recent Requests tab have a toolbox icon . You can click this icon to access direct links to the following features:

JVM Display
System Resources
Monitor On Demand
data collector Properties
Trap and Alert Management

When you access the managing server visualization engine in this way, the managing server visualization engine displays in a browser view in a workspace. The Tivoli Enterprise Portal navigation tree is automatically hidden in the workspace. To show or hide the monitoring portal navigation tree, click the small black arrow.

11.4. Create links to the managing server visualization engine using the Link Wizard

Throughout the monitoring portal, you can use the Link Wizard to manually create links to the managing server visualization engine.

Create links

You can access the Link Wizard feature from other views and workspaces in the monitoring portal.

To access the Link Wizard, from any of the tables or views, right-click the link icon and click Link Wizard.
Follow the steps in the wizard to do one of the following actions:

Create a link.
Modify an existing link.
Delete one or more links.

Type the name and description of the link.
Choose one to the following options with the aid of the descriptions in the Link Wizard.

Dynamic
Absolute
Relative

Choose the option to use. Follow the instructions in the help within the application until you get to the Workspace Link Wizard Parameters page.

Add parameters to the Link Wizard

When you get to the Workspace Link Wizard Parameters page in the Link Wizard you must manually add these two symbols VEHOSTPORT and VEPATH and add information to these parameters. There are two predefined workspaces which have an embedded browser as its only view.

Diagnostic Link for Agent. Choose this workspace if the link is from the agent level workspaces.
Diagnostic Link. Choose this workspace if the link is from the server level workspace.
To add Symbols to the Link Wizard, complete the following steps:

Click Symbol and type VEHOSTPORT.
Click OK to add the Symbol.
To add an expression, select VEHOSTPORT, and click Modify Expression.
Basic Setup: In the text field, type the expression to add. The value for the VEHOSTPORT is <your ve host>:<your ve port>. For example, if in your environment, the managing server visualization engine is installed on host1, with port 9080, then the VEHOSTPORT value is: .host1:9080..

Double quotation marks are required in the expression.
If your managing server visualization engine host or port information changes, then you must update the link you defined and correct the VEHOSTPORT information manually.

Advanced Setup: In the text field, type the expression to add. The value for the VEHOSTPORT value is CALL(candle.kwj.ve.ITCAMLinkHelper, getVehostportForWASServer, null, null, $kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$). To get the expression: $kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$, in the Expression Editor, click Symbol.
Click Origin Node and click OK to get $kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$.
When using the Advanced set up option, if your managing server visualization agent host or port information changes, ITCAM for Application Diagnostics custom code updates the changes automatically, you do not have to modify the links you defined manually to correct the information.
To add an expression, Basic Setup: the VEPATH value can be set as .am/ve/sad/threadList?mappingTEPUrl=true.

Double quotation marks are required in the expression.
When you use the Basic Setup option, you must select the server group and the server in the managing server visualization engine yourself when you log in to managing server visualization engine.

To add an expression, Advanced Setup: Set the VEPATH value in the Expression Editor as:"am/ve/sad/threadList?mappingTEPUrl=true&server=" + CALL(candle.kwj.ve.ITCAMLinkHelper, getServerIdForWASServer, null, null, $kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$)
Where the correct expression of $kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$ can be found by using Symbols view under Expression Editor: $kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$ (Symbol: Origin Node).
Review the details in the Workspace Link Wizard - Summary. Click Finish.
If you use the Advanced Setup options in Step 4 and Step 6, modify the linkIsEnabled parameter in the Workspace Link Wizard Parameters view with expression: CALL(candle.kwj.ve.ITCAMLinkHelper, isEnabledForWASServer, null, null, $kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$) && $kfw.TableRow:ATTRIBUTE.<table_name>.ASID$ != -3. In the Expression Editor, use the Symbols view to find expressions of $kfw.TableRow:ATTRIBUTE.<table_name>.ORIGINNODE$ (Symbol: Origin Node)and $kfw.TableRow:ATTRIBUTE.<table_name>.ASID$ (Symbol: ASID).

Manually adding your own links to the Link Wizard

The minimum settings are VEHOSTPORT and VEPATH. To link to a different page, you must change this value to corresponding URL path. Here is a list of frequently used managing server visualization engine pages and URL paths:

Enterprise Overview: am/home
Server Overview: am/ve/serverOverview
Server Statistics Overview : am/avm/main
Server Activity Display: am/ve/sad/threadList
Memory Leak: am/ve/memory/leakReport
JVM Thread Display: am/ve/jtd/threadGroupList
Monitor On Demand: am/ve/mod/console
Trap and Alert Management: am/trap
System Resources:am/ve/jmxbrowser

If you change the host port number at any point, you must modify these two properties again and the kernel properties on the Managing Server installation must be restarted to identify the changes.

Link anchor

You can use the Link anchor option to access the Link anchor properties window. You can use the Link anchor properties window to display visual indicators on tables where customized links have been defined, and to establish a default link that opens when the user clicks the indicator.

From any of the tables, right-click the choose link icon and click Link Anchor to display the Link anchor properties window.
Depending on the area of the table item you select, the window displays the following information:

Default no link
Show Link indicator
Link indicator always enabled.

For more information about the uses of these items, refer to the help within the Link anchor properties window.

Workspace link to ITCAM for SOA

You can navigate from monitoring agent for WebSphere Application Server workspaces to ITCAM for SOA.
If ITCAM for SOA is installed and configured for the same application server, you can navigate from the Application Server Summary and Business Process Manager Summary workspaces and from the Application Health workspace to workspaces provided by ITCAM for SOA. ITCAM for SOA is available with ITCAM for Applications. For more information, see the ITCAM for SOA User Guide.
A service group is a set of related service operations that collectively might represent or encompass a business function or application in your enterprise. This can consist of a service flow, a subset of a flow, or any collection of operation aggregates that represent something meaningful to you in your monitored environment. A process group is a Business Process Management (BPM)-specific group that aggregates elements that are part of a BPM solution, such as applications, modules, components, or operations. A process group allows the monitoring of interactions between the components of the solution. This monitoring provides BPM-specific context information.

Alarm Manager workspace

This workspace displays aggregated information about the alarms for each work manager.
This workspace displays data provided by the Alarm Manager attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains:

Highest Alarm Rate bar chart, which displays the five highest number of alarms fired per second
Work Manager Alarms report, which displays detailed information about the alarms for each work manager

Access the Alarm Manager workspace

To access this workspace from the Thread Pools workspace, use one of the following procedures:

Within the Navigator, right-click the Thread Pools entry; then from the menu select Workspace > Alarm Manager.
From the primary monitoring portal menu, expand the View menu, and select Workspace > Alarm Manager.

Allocation Failures workspace

This workspace summarizes all the heap-allocation failures that occurred within the Java. Virtual Machine (JVM) over the current interval and that caused the JVM to initiate garbage collection.
This workspace displays data provided by the Allocation Failure attributes.
Note to Solaris and HP-UX users: Allocation-failure information is not recorded on these platforms; hence this workspace is always empty.
Predefined workspace contains the following items:

Allocation Failure Elapsed Times bar chart, which displays the number of allocation failures during the current interval
Heap Usage bar chart, which displays the heap usage for this JVM. The bar's fail over gives the allocation-failure ID number followed by a range of recording times. This allocation-failure number displays in the Allocation Failures report and associates each bar with that particular row within the report
Allocation Failures report, which displays information about the heap-allocation failure that caused the Java Virtual Machine hosting the application server to start its garbage-collection routine. The Allocation Failures report includes the ASID field.

Access the Allocation Failures workspace

To access this workspace from the Garbage Collector Activity workspace, complete the following steps:

From the Garbage Collection Analysis report, right-click the link icon and from the menu, click Allocation Failures. Note that in the Allocation Failure workspace, the ASID is displayed in the Allocation Failures report.

Selected Application - Application Trend at L1 workspace

This workspace displays access trends for individual applications. It provides trend information for request and response times. It also provides trend information for application errors. This workspace provides a broad overview of the health of an application and draws data from multiple attribute groups.
This workspace displays data provided by the Request Analysis and Request Times and Rates attribute groups.

Predefined workspace contains:

Selected Application Summary report displays application name, average request response time, average request completion rate, error rate, and ASID. For monitoring agents running on z/OS, region ID can be found in the ASID column.
Response Time Trend chart displays summary trend times for the overall response time for the selected application.
Error Rate Trend chart displays the error rate for the application.
Request Rate Trend chart displays the number of requests completed per second for the application.

Access the Selected Application - Configuration workspace

Access this workspace using one of the following methods:

Double click any application in the application server Summary workspace.
Right-click on application icon in the application server Summary workspace and select Link To, then select Application Trend at L1.

Selected Application - Application Trend at L2/L3 workspace

This workspace displays access trends for individual applications. It provides trend information for request and response times. It also provides trend information for application errors. This workspace provides a broad overview of the health of an application and draws data from multiple attribute groups.
This workspace displays data provided by the Request Analysis and Request Times and Rates attribute groups.

Predefined workspace contains:

Selected Application Summary report displays application name, average request response time, average request completion rate, error rate, and ASID. For monitoring agents running on z/OS, region ID can be found in the ASID column.
Response Time Trend chart displays trend times for the following different elements in milliseconds: JNDI, JMS, Application, JCA, SCA, Servlet, EJB, and web service requests.
Error Rate Trend chart displays the error rate for the application.
Request Rate Trend chart displays the number of requests completed per second for the application.

Access the Selected Application - Configuration workspace

Access this workspace using one of the following methods:

Double click any application in the application server Summary workspace.
Right-click on application icon in the application server Summary workspace and select Link To, then select Application Trend at L2/L3.

Application Health workspace

The workspace displays the information about the real-time health status of applications monitored by the monitoring agent.
The health status information is collected from the following sources.

Request Metrics - performance data that measures request execution time collected from the ITCAM instrumentation points in the application code.
Resource Metrics - pool usage and container performance statistics collected from the corresponding PMI modules or MBeans.
GC Metrics - metrics on garbage collection frequency and performance collected from parsing of the GC verbose log file when it is enabled for the application server JVM.
OS metrics - metrics collected about the JVM process and the whole system execution, such as CPU used percentage, paging rate, and so on.

Additionally, the monitoring agent uses thresholds, called Application Health Indicators, to determine the quality of the application service. For request response times, thresholds are assigned automatically during baselining. You can also manually customize the thresholds. There are three monitored application tiers evaluated for health status.

Client Tier provides performance data and status of application execution in servlets/JSPs or portal containers as well as corresponding thread pools servicing these containers.
Application Tier provides application execution metrics of EJB containers and custom requests.
Backend Tier provides application execution in JDBC, JCA, JMS, JNDI API calls.

This workspace displays data provided by the Application Health Status attributes.
By default, the predefined workspace has the following views:

Situation Event console view, which shows the event console with activity associated with the Application Health Summary Navigator item and any other workspaces in the group, as well as linked workspaces. The Navigator displays an event icon overlaid on the Application Health Summary node when a situation becomes true. The report is useful when multiple alerts are raised as you can see them all in a single filtered view.
Application Health Summary report, which shows the report of the application name, status, and health indicator for client, application, and backend tiers health status.

Due to the runtime MBeans configuration, the monitoring agent can find only composition units of business-level applications that associate with either web or EJB modules.
If any applications are running on the Business Process Manager server and ITCAM for SOA is installed on the server, an additional link is available. In the Application Health Summary view, right-click any application and select Selected Application - Group Summary to view the Group Summary workspace, provided by ITCAM for SOA. In this workspace, you can see the status of all process groups that include any components or operations that are a part of the selected application.

Access the Application Health Summary workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere Application server entry of your choice.
Within that server list of available WebSphere application server workspaces, click the Application Health entry.

Application Registry workspace

This workspace displays the information about the server configuration for the application.
This workspace displays data provided by the Application Monitoring Configuration attributes.
Predefined workspace contains:

Situation Event Console report, which shows the event activity for situations associated with the current Navigator item. The Navigator alerts you when a situation becomes true by overlaying the Navigator item with an event indicator. This report is useful when multiple alerts are raised and you might not know newly arrived alerts just by looking at the indicator.
Application Configuration report, which shows the configurations that are discovered, stored and managed for WebSphere applications running within that application server.

Access the Application Registry workspace

To access this workspace from the Application Health Summary workspace, use one of the following procedures:

Within the Navigator, right-click the Application Health entry; then, from the menu, click Workspace > Application Registry.
From the primary monitoring portal menu, click View > Workspace > Application Registry.

Business Process Manager workspace

The Business Process Manager workspace displays overall statistics for a Business Process Manager server being monitored by the monitoring agent.
Predefined workspace contains the following items:

Heap Usage - History bar chart, which displays free memory size and used memory size (in kilo bytes) within the WebSphere application server heap over time. The chart flyovers display the exact values.
This view displays data provided by the Garbage Collection Analysis attributes.
Response Time - History graph, which shows the server response time to requests over time
This view displays data provided by the Request Times and Rates attributes.
Request Rate - History graph, which shows the rate at which requests have been received by this server over time
This view displays data provided by the Request Times and Rates attributes.
Percent CPU Used - History graph, which shows the percentage of the CPU that this server consumed over time
This view displays data provided by the application server attributes.
Application server summary report, which displays overall information about this WebSphere application server, including JVM statistics and CPU usage statistics
This view displays data provided by the application server attributes.

Access the Business Process Manager workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, right-click a Business Process Manager entry, and select Workspaces > Business Process Manager.

Cache Analysis workspace

This workspace reports information about the dynamic cache.
WebSphere application server consolidates several caching activities, including servlets, web services, and WebSphere commands, into one service called the dynamic cache. These caching activities work together to improve application performance. The activities share many configuration parameters, which are set in a dynamic cache service in an application server. The dynamic cache works within a Java. Virtual Machine (JVM) within an application server, intercepting calls to cacheable objects, for example, through a servlet service method or an execute method on a command. The dynamic cache either stores the object output to or serves the object content from the dynamic cache.
This workspace displays data provided by both the Dynamic Cache attributes and the Dynamic Cache Templates attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high overhead, the Tivoli Enterprise Monitoring Agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

In-memory Cache Sizes - History graph, which shows the sizes of in-memory cache entries for the specified interval
Highest Miss Rates bar chart, which shows the most frequent cache entry misses (per second). The Y-axis headings correspond to the row number of the Dynamic Cache Templates report
Dynamic Cache report, which displays information about the dynamic cache, including cache sizes and timeout rates
Dynamic Cache Templates report, which displays information about the cache template data. A cache template is an object type defined by a cache policy specified in WebSphere application server file cachespec.xml. A cache policy specifies the caching rules and indicates what is cached, the invalidation and timeout conditions, and other data

Access the Cache Analysis workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Cache Analysis entry.

Client Communications workspace

This workspace provides overall Service Integration Bus communication performance data and counters for all clients connected to this application server. WebSphere application server 5.1 based products do not support this workspace.
This workspace displays data provided by the Client Communications attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Connection Count - History graph, which shows the number of API sessions used by clients that were network connected to this application server
Error Count - History graph, which shows the communication errors that occurred and that resulted in the disconnection of a network connection to a client
Communication Statistics report, which displays information about client communications, including API connections, errors, reads, writes, sent priority, received priority, MessageSent priority, and MessageReceived priority

Access the Client Communications workspace

To access this workspace from the Platform Messaging workspace, use one of the following procedures:

Within the Navigator, right-click the Platform Messaging entry; then from the menu, click Workspace > Client Communications.
From the primary monitoring portal menu, click View > Workspace > Client Communications.

Container Object Pools workspace

This workspace displays aggregate information about the object pools associated with Enterprise Java. Beans (EJBs). It provides a view of pool performance for all Enterprise Java Beans deployed to each container.
This workspace displays data provided by the Container Object Pools attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Object Pool Rates - History graphs, which show the retrieval, return, discard, and drain rates for the EJBs in each EJB container
Container Object Pools report, which displays:

Aggregated information for each defined EJB container that aggregates bean object pool performance for all Enterprise beans deployed to that container
Aggregated information for the application server that aggregates bean object pool performance data for all Enterprise beans deployed to the application server

Access the Container Object Pools workspace

To access this workspace from the EJB Containers workspace, use one of the following procedures:

From the primary monitoring portal menu, click View > Workspace > Container Object Pools.
Within the Navigator, right-click the EJB Containers entry; then, from the menu, click Workspace > Container Object Pools.

Container Transactions workspace

This workspace displays data about the activities and transactions running in each application server.
This workspace displays data provided by the Container Transactions attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Transaction Rates - History graph, which shows the per-second begin, commit, and rollback rates over time for local and global transactions
Transaction Durations - History graph, which shows the amount of time it takes to complete local and global transactions
Container Transactions report, which displays performance information for global and local transactions that run in each defined EJB container and an aggregated value for all transactions that run in the application server

Access the Container Transactions workspace

To access this workspace from the EJB Containers workspace, use one of the following procedures:

From the primary monitoring portal menu, click View > Workspace > Container Transactions.
Within the Navigator, right-click the EJB Containers entry; then, from the menu, click Workspace > Container Transactions.

Data sources workspace

The data sources workspace displays statistical data for the data sources that your applications reference when accessing databases.
This workspace displays data provided by the Datasources attributes.
Predefined workspace contains the following items:

Worst Datasource Query Times bar chart, which shows the longest times (in milliseconds) the application spent waiting to retrieve data from the database during the specified interval
Worst Datasource Update Times bar chart, which shows the longest times (in milliseconds) the application spent updating data within the database during the specified interval
Datasources - Current Interval report, which displays database usage information. For example, this report shows traffic information such as the time the application spent trying to connect to the database, and the total and average processing times for database queries and updates.

Access the Data sources workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Datasources entry.

Selected Data source - History workspace

The Selected Datasource - History workspace displays the historical information that corresponds to the information in the Datasource workspace for a selected data source. Historical information is collected over a specific time span. See the online help for Tivoli Enterprise Portal for a detailed explanation of historical reporting.

Access the Selected Data source - History workspace

To access this workspace from the Datasource workspace, use one of the following procedures:

From the Datasources - Current Interval report, right-click the link icon and from the menu, click Selected Datasource - History.
From Worst Datasource Query Times bar chart or the Worst Datasource Update Times bar chart, right-click any bar; then, from the menu, click Link To > Selected Datasource - History.

Selected Data source - Datasource Trend workspace

The Datasources Trend workspace displays information about datasource connections. This workspace displays data provided by the Datasources attributes.
This predefined workspace contains the following items:

Current Datasources report displays datasource name, total wait time, connection rate, connection average wait time and connection max wait time. For monitoring agents running on z/OS, region ID can be found in the ASID column.
Total Wait Time chart displays the total time that applications had to wait for a connection to the data source.
Connection Rate Trend chart displays the number of connection requests created for the data source per second.
Connection Average and Max Time Trend chart display the average time in milliseconds and the worst-case time in milliseconds that applications had to wait for a connection.

Access the Selected Data source - Datasource Trend workspace

Right-click the Datasources workspace, select Workspace and then Datasource Trend workspace
For additional information, see:

Access the managing server visualization engine from the Datasources workspace

To use this functionality, you need ITCAM for Application Diagnostics Managing Server.
In the monitoring portal, access the Datasources workspace. You can use the Diagnostic Server Activity Display link to access the managing server visualization engine. For information about access requirements, see ">Prerequisites for access.

In the Datasources - Current Interval window, right-click the choose link icon then click Diagnostic Server Activity Display.
If this is your first time to access the Managing server visualization agent during a session, you see a Welcome to the Application Monitor page.
Depending on the user setup configuration in your environment you might have to type your managing server visualization engine User Name and Password. If you do, you need only to log in using your User Name and Password once per session. Click OK to display the Server Activity Display page in the managing server Visualization engine. You can use this page to diagnose application problems, for example, slow transactions or high response times.
In a z/OS environment, right-click the link icon on a row where the ASID column displays Summary.

Click Selected Datasource- Servant Regions.
In the Selected Datasource - Servant Regions table, right-click the link icon on a row.
Click Diagnostic Server Activity Display.

The results in this page relate directly to the context from where you launched the link in the monitoring portal. For more information about using the Server Activity Display page, and additional features refer to the Composite Application Manager help within the managing server visualization agent Interface.
To return to the previous workspace in the monitoring portal interface at any time choose from the following options:

From the monitoring portal desktop client, including WebStart, click the back arrow on the Portal toolbar.
From the monitoring portal browser client, click the browser back arrow.

DB Connection Pools workspace

This workspace displays information about the database connection pools associated with each application server.
You can use this workspace to monitor Java. Database Connectivity (JDBC) performance for WebSphere application server applications. This workspace displays data provided by the DB Connection Pools attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of the high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Highest Average Pool Sizes bar chart, which shows the largest average size (that is, number of connections) for each database connection pool
Worst Wait Times bar chart, which shows the worst wait times (in milliseconds) for each database connection pool
Highest Allocation Rates bar chart, which shows the rate at which database connections are being made for each connection pool
DB Connection Pools report, which displays information about the database connection pool for each defined data source. The report also displays an aggregated value that aggregates over all data sources. For example, this report displays the number of threads waiting for a connection and the number of connections created and released

Access the DB Connection Pools workspace

To access this workspace, complete the following steps:

In the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server entry of your choice.
Within that server list of available WebSphere application server workspaces, click the DB Connection Pools entry.

Selected DB Connection Pool - History workspace

The Selected DB Connection Pool - History workspace displays historical information that corresponds to the information in the DB Connection Pools workspace for a selected connection pool. Historical information is collected over a specific time span. See the online help for monitoring portal for a detailed explanation of historical reporting.

Access the Selected DB Connection Pool - History workspace

To access this workspace from the DB Connection Pools workspace, use one of the following procedures:

From the DB Connection Pools report, right-click the link icon and from the menu, click Selected DB Connection Pool - History.
From the Highest Average Pool Sizes bar chart, the Worst Wait Times bar chart, or the Highest Allocation Rates bar chart, right-click any bar; then, from the menu, click Link To > Selected DB Connection Pool - History.

Access the managing server visualization engine from the DB Connection Pools workspace

To use this functionality, you need ITCAM for Application Diagnostics Managing Server.
In the monitoring portal access the DB Connection Pools workspace. You can use the Diagnostic Server Activity Display link to access the managing server visualization engine. For information about access requirements, see Prerequisites for access.

In the DB Connection Pools window, right-click the choose link icon then click Diagnostic Server Activity Display.
If this is your first time accessing the managing server visualization agent during a session, you see a Welcome to the Application Monitor page.
Depending on the user setup configuration in your environment you might have to type your managing server visualization engine User Name and Password. If you do, you need only log in once per session using your User Name and Password.
Click OK to display the Server Activity Display page in the managing server Visualization engine. You can use links to diagnose application problems, for example, slow transactions or high response times.
The results relate directly to the context from where you launched the link in the monitoring portal. For more information about using the Server Activity Display page and additional features, refer to the Composite Application Manager help within the managing server visualization agent Interface.
To return to the previous workspace in the monitoring portal interface at any time choose from the following options:

From the monitoring portal desktop client, including WebStart, click the back arrow on the Portal toolbar.
From the monitoring portal browser client, click the browser back arrow.

DCS Stacks workspace

This workspace displays aggregated information about each DCS stack within the entire WebSphere application server domain, including multiple nodes and servers.
This workspace displays data provided by the DCS Stack attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Highest Message Buffer Reallocations bar chart, which displays the highest number of message buffer reallocations that occurred as a result of inadequate buffer size
Most Sent Messages bar chart, which shows most frequent number of message buffer reallocations that occurred as a result of inadequate buffer size
High Severity Congestion Events bar chart, which shows the number of times that a high severity congestion event for outgoing messages was raised
DCS Statistics report, which displays information for the DCS stack data, including incoming and outgoing message size, sent messages, and high severity congestion events

Access the DCS Stacks workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the DCS Stacks entry.

Destinations workspace

In this workspace, you can view performance data and counters for the destinations of a selected messaging engine.
A destination is a virtual location within a service integration bus, to which applications attach as producers, consumers, or both, to exchange messages. There are two types of destinations, queues and topic spaces. WebSphere application server 5.1 based products do not support this workspace. This workspace displays data provided by both the Topic Spaces attributes and the Queue attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains:

Queue report, which displays information about the queue data. A queue is a destination for point-to-point messaging
Topic Spaces report, which displays information about the topic space data. A topic space is a destination for publish/subscribe messaging

Access the Destinations workspace

To access this workspace from the Messaging workspace, complete one of the following steps:

From the Messaging Engines report, right-click the link icon and from the menu, click Destinations.
From Average Local Wait Time - History graph, Expired Messages - History graph, Incomplete Topic Publications - History graph, or Total Published - History graph, right-click any bar; then, from the menu, click Link To > Destinations.

Durable Subscriptions workspace

In this workspace, you can view statistic counters for the durable subscriptions of a selected topic.
The default messaging provider supports the use of durable subscriptions to topics. This enables a subscriber to receive a copy of all messages published to a topic, even messages published during periods of time when the subscriber is not connected to the server. WebSphere application server 5.1 based products do not support this workspace. This workspace displays data provided by the Durable Subscriptions attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Durable Subscriptions report, which displays information about durable subscriptions that pertain to a selected topic, including the number of messages consumed, and message wait time

Access the Durable Subscriptions workspace

To access this workspace from the Destinations workspace, complete the following step:

From the Topic Spaces report, right-click the link icon and from the menu, click Durable Subscriptions.

EJB Containers workspace

This workspace displays aggregated information about each defined EJB.
This workspace displays aggregated bean performance data for all Enterprise beans deployed to an EJB container. It also displays aggregated information for the application server that aggregates bean performance data for all Enterprise beans deployed on the application server. This workspace displays data provided by the EJB Containers attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Method Average Response Time - History graph, which shows the average response time for methods invoked by the EJBs in the container
Method Invocation Rate - History graph, which shows the rate at which the methods of an EJB container were invoked
EJB Containers report, which displays aggregated information for each defined EJB container that aggregates bean performance data for all Enterprise beans deployed to that container. The report also displays aggregated information for the application server that aggregates bean performance data for all Enterprise beans deployed to the application server. For example, this report displays load values, response times, and life cycle activities for Enterprise beans

Access the EJB Containers workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the EJB Containers entry.

Access the managing server visualization engine from the EJB Containers workspace

To use this functionality, you need ITCAM for Application Diagnostics Managing Server.
In the Tivoli Enterprise Portal access the EJB Containers workspace. You can use the Diagnostic Server Activity Display link to access the managing server visualization engine. For information about access requirements, see Prerequisites for access.

In the EJB Containers window, right-click the choose link icon then click Diagnostic Server Activity Display.
If this is your first time to access the managing server visualization engine during a session, you see a Welcome to the Application Monitor page.
Depending on the user setup configuration in your environment you might have to type your managing server visualization engine User Name and Password. If you do, you need only log in once per session using your User Name and Password.
Click OK to display the Server Activity Display page in the managing server Visualization engine. You can use link to diagnose application problems, for example, slow transactions or high response times.
The results relate directly to the context from where you launched the link in the Tivoli Enterprise Portal. For more information about using the Server Activity Display page and additional features, refer to the Composite Application Manager help within the managing server visualization agent Interface.
To return to the previous workspace in the Tivoli Enterprise Portal interface at any time choose from the following options:

From the Tivoli Enterprise Portal desktop client, including WebStart, click the back arrow on the Portal toolbar.
From the Tivoli Enterprise Portal browser client, click the browser back arrow.

Enterprise Java Beans workspace

This workspace reports information about each Enterprise Java. Bean (EJB) defined for an EJB container.
The workspace provides information about these beans that relates to their identity, instrumentation level settings, creation and destruction of bean objects, response times, invocations, calls, and rates for retrievals, returns, and discards. This workspace displays data provided by the Enterprise Java Beans attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Worst Method Response Times bar chart, which shows the worst response times (in milliseconds) for methods invoked by each bean instance
Highest Method Invocation Rates bar chart, which shows the methods that are invoked most often by each bean instance
Enterprise Java Beans report, which shows performance information about each EJB deployed to the application server. This report displays information about bean activity, including the rates at which beans are being instantiated and destroyed

Access the Enterprise Java Beans workspace

You access this workspace from the EJB Containers workspace. To list the EJBs for all containers, use one of the following procedures:

From the primary monitoring portal menu, click View > Workspace > Enterprise Java Beans.
Within the Navigator, right-click the EJB Containers entry; then, from the menu, click Workspace > Enterprise Java Beans.

To see the EJBs referenced by a specific EJB container, complete the following step:

From the EJB Containers report, right-click the link icon and from the menu, click Enterprise Java Beans.

Garbage Collections - Selected Allocation Failure workspace

This workspace provides detailed information about the garbage-collection cycles that occurred in response to a specific heap-allocation failure that occurred within the Java. Virtual Machine.
This workspace displays data provided by the Garbage Collection Cycle attributes.
Note to Solaris and HP-UX users: Allocation-failure information is not recorded on these platforms. Consequently, this workspace is always empty.
Predefined workspace contains the following items:

GC Elapsed Times bar chart, which breaks down the mark, sweep, and compact times (in milliseconds) for each garbage-collection cycle that occurred for the selected allocation failure
Heap Usage bar chart, which displays the JVM heap usage (kilobytes in use, freed, and free at start of garbage collection) for each garbage-collection cycle
Garbage Collections - Selected Allocation Failure report, which displays information about a single garbage-collection cycle that the JVM hosting the application server performed. For example, this report displays the free heap space both before and after garbage collection, the heap space freed, and the number of objects moved during garbage collection. For monitoring agents running on z/OS, region ID can be found in the ASID column.

Access the Garbage Collections - Selected Allocation Failure workspace

To access this workspace from the Allocation Failures workspace, use one of the following procedures:

From the Allocation Failures report, right-click the link icon and from the menu, click Garbage Collections - Selected Allocation Failure.
From the Allocation Failure Elapsed Times bar chart or the Heap Usage - History bar chart, right-click any bar; then, from the menu, click Link To > Garbage Collections - Selected Allocation Failure.

For more information, see:

Garbage Collection Analysis workspace

This workspace summarizes all the Java. Virtual Machine (JVM) garbage-collector activity over a user-defined interval.
The JVM generates detailed garbage collection logs for an application server when started with the verbose:gc runtime parameter. This workspace displays data provided by the Garbage Collection Analysis attributes.
Predefined workspace contains the following items:

Garbage Collection Rate - History graph, which displays the rate at which the garbage-collection algorithm is being invoked
Heap Usage - History bar chart, which displays the high-water mark of free storage (in kilobytes) available in the heap after each garbage-collector run
Percentage of Time Garbage Collector Running - History graph, which displays the percentage of real time the garbage collector was running during the current interval, for each server region
Garbage Collection Analysis report, which displays information about the garbage-collection activities within the Java Virtual Machine that is hosting the application server. For example, this report displays the number of times the collector ran during the interval and the resulting number of objects that the collector freed

Access the Garbage Collection Analysis workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the name of the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Garbage Collection Analysis entry.

Access the managing server visualization engine from the Garbage Collection Analysis workspace

To use this functionality, you need ITCAM for Application Diagnostics Managing Server.
In the monitoring portal navigate to the Garbage Collection Analysis workspace. You can use the Diagnostic Server Activity Display link to access the managing server visualization engine. For information about access requirements, see ">Prerequisites for access.

In the Garbage Collection Analysis window, right-click the choose link icon then click Diagnostic Memory Leak.
If this is the first time you access the managing server visualization agent, you see a Welcome to the Application Monitor page.
Depending on the user setup configuration in your environment you might have to type your managing server visualization engine User Name and Password. If you do, you must log in only once per session using your User Name and Password.
Click OK to display the Memory Leak Confirmation report page in the managing server visualization engine. You can use this page to diagnose memory leak problems.
In a z/OS environment, right-click the link icon on a row where the ASID column displays Summary.

Click Garbage Collection Analysis Servant Regions.
In the Garbage Collection Analysis - Servant Regions table, right-click the link icon on a row.
Click Diagnostic Memory Leak.

For information about Creating a Memory Leak Confirmation report in this page, and additional features refer to the Composite Application Manager help within the managing server visualization engine Interface.
To return to the previous workspace in the monitoring portal interface at any time choose from the following options:

From the monitoring portal desktop client, including WebStart, click the back arrow on the Portal toolbar.
From the monitoring portal browser client, click the browser back arrow.

High Availability Manager workspace

The High Availability Manager workspace provides aggregated information about high availability managers.
This workspace displays data provided by the High Availability Manager attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set the Resource Data Collection Method configuration value to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.

Because of high processor usage, the monitoring Aagent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Local Group - History graph, which shows the number of local groups.
Group State Rebuild Time - History graph, which shows the time taken to rebuild the global group state in milliseconds.
High Availability Manager report, which displays information about the high availability manager, including group state rebuild time, bulletin-board subjects, bulletin-board subscriptions, bulletin-board rebuild time, and local bulletin-board subjects

Access the High Availability Manager workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the High Availability Manager entry.

IMAP/POP workspace

This workspace provides aggregated statistics of the usage information about the IMAP service and the POP3 service connectivity, especially for the performance-related connectivity.
This workspace displays data provided by the Workplace Mail IMAP/POP attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

This workspace does not support linking to ITCAM for Application Diagnostics Managing Server visualization engine.
Predefined workspace contains the following items:

Active Sessions bar chart, which displays the number of active sessions during the sampling interval
Authentication Failures bar chart, which displays the number of authentications failures during the sampling interval
Workplace Mail report, which displays detailed information about the workplace mail for each protocol

Access the IMAP/POP workspace

To access this workspace from the Workplace Mail workspace, use one of the following procedures:

Within the Navigator, right-click the Workplace Mail entry; then from the menu, click Workspace > IMAP/POP.
From the primary monitoring portal menu, click View > Workspace > IMAP/POP.

J2C Connection Pools workspace

This workspace reports information about resource adapters and connectors that adhere to J2C, the WebSphere application server implementation of the J2EE Connector Architecture (JCA).
Data counters for this category contain usage information about the J2C connection pools that enable enterprise beans to connect to and interact with systems such as the Customer Information Control System (CICS) and the Information Management System (IMS.). This workspace displays data provided by the J2C Connection Pools attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the Tivoli Enterprise Monitoring Agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Highest Average Pool Sizes bar chart, which shows the largest average number of managed connections for each J2C connection pool. The Y-axis headings correspond to the row number of the J2C Connection Pools report
Worst Wait Times bar chart, which shows the worst wait time (in milliseconds) for each of the J2C connection pools. The y-axis headings correspond to the row number of the J2C Connection Pools report
Highest Allocation Rates bar chart, which displays the highest managed-connection creation, destruction, and allocation rates (in events per second)
J2C Connection Pools report, which displays information about connectors that adhere to J2C. For example, this report displays the number of managed connections or physical connections and the total number of connections or connection handles

Access the J2C Connection Pools workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the J2C Connection Pools entry.

Access the managing server visualization engine from the J2C Connection Pools workspace

To use this functionality, you need ITCAM for Application Diagnostics Managing Server.
In The Tivoli Enterprise Portal access the J2C connection pools workspace. You can use the Diagnostic Server Activity Display link to access the managing server visualization engine. For information about access requirements see ">Prerequisites for access.

In the J2C connection pools window, right-click the choose link icon then click Diagnostic Server Activity Display.
If this is your first time to access the managing server visualization agent during a session, you see a Welcome to the Application Monitor page.
Depending on the user setup configuration in your environment you might have to type your managing server visualization engine User Name and Password. If you do, you need to log in only once per session using your User Name and Password.
Click OK to display the Server Activity Display page in the managing server Visualization engine. You can use link to diagnose application problems, for example, slow transactions or high response times.
The results relate directly to the context from where you launched the link in the monitoring portal. For more information about using the Server Activity Display page and additional features, refer to the Composite Application Manager help within the managing server visualization agent Interface.
To return to the previous workspace in the monitoring portal interface at any time choose from the following options:

From the monitoring portal desktop client, including WebStart, click the back arrow on the Portal toolbar.
From the monitoring portal browser client, click the browser back arrow.

36. JMS Summary workspace

The JMS Summary workspace displays information about queues being used by your applications using the Java. Message Service (JMS) interface.
The JMS Summary workspace also provides information about how WebSphere application server applications are using WebSphere MQ. It displays such information as the number of messages read and written and which queue managers and queues were used during the interval.
This workspace displays data provided by the JMS Summary attributes.
Predefined workspace contains the following items:

Worst JMS Send Times bar chart, which displays the longest times (in milliseconds) your application spent putting messages onto a queue during the interval
Worst JMS Receive Times bar chart, which displays the longest times (in milliseconds) your application spent getting messages from a queue during the interval
Worst JMS Browse Times bar chart, which displays the longest times (in milliseconds) your application spent browsing messages on a queue during the interval
JMS Summary - Current Interval report, which displays detailed information about how the WebSphere application server uses messaging middleware (that is, WebSphere MQ) using JMS. Details include the send, receive, browse, and publish times for your application. It also includes such information as, which queue managers and queues are being used and how many messages are being read and written

Access the JMS Summary workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the JMS Summary entry.

Access the managing server visualization engine from the JMS Summary workspace

To use this functionality, you need ITCAM for Application Diagnostics Managing Server.
In The Tivoli Enterprise Portal access the JMS Summary workspace. You can use the Diagnostic Server Activity Display link to access the managing server visualization engine. For information about access requirements, see ">Prerequisites for access.

In the JMS Summary - Current interval window, right-click the choose link icon then click Diagnostic Server Activity Display.
If this is your first time to access the managing server visualization agent during a session, you see a Welcome to the Application Monitor page.
Depending on the user setup configuration in your environment you might have to type your managing server visualization engine User Name and Password. If you do, you need to log only once per session using your User Name and Password.
Click OK to display the Server Activity Display page in the managing server Visualization engine. You can use this link to diagnose application problems, for example, slow transactions or high response times.
In a z/OS environment, right-click the link icon on a row where the ASID column displays Summary.

Click Selected JMS - Servant Regions.
In the Selected JMS - Servant Regions table, right-click the link icon on a row.
Click Diagnostic Server Activity Display.

For more information about the options available in a z/OS environment, refer to Region workspaces in a z/OS environment and ..."> Access a Region workspace.
The results in this page relate directly to the context from where you launched the link in the Tivoli Enterprise Portal. For more information about using the Server Activity Display page, and additional features refer to the Composite Application Manager help within the managing server visualization agent Interface.
To return to the previous workspace in the Tivoli Enterprise Portal interface at any time choose from the following options:

From the Tivoli Enterprise Portal desktop client, including WebStart, click the back arrow on the Portal toolbar.
From the Tivoli Enterprise Portal browser client, click the browser back arrow.

37. JVM Stack Trend workspace

This workspace displays trend data regarding JVM CPU usage, JVM garbage collection, and JVM heap usage.
This workspace displays data provided by the application server and Garbage Collection Analysis attribute groups.

Predefined workspace contains:

JVM CPU Trend chart indicates the percentage of the JVM CPU used.
Percent GC Time Used chart
Heap Usage Trend chart

Access the Selected Application - Configuration workspace

Access this workspace using one of the following methods:

Double click the JVM icon in Resources workspace.
Right-click the JVM icon in the Resources workspace and select Link To, then select JVM Stack Trend.

38. Log Analysis workspace

This workspace reports application server error and exception conditions as recorded in the application server log file.
This workspace displays data provided by both the Log Analysis attributes and DC Messages attributes.
Predefined workspace contains the following items:

DC Message Events, which display aggregated information about the messages from WebSphere data collector
Log Analysis report, which displays application server error and exception conditions as recorded in the application server log file, SystemOut.log. This information includes the exception severity as well as the ID and text of the associated message. In the Log Analysis report, if the PID value is displayed as -1, it indicates that the data collector is disconnected. If a WebSphere server shutdown occurs, the connection between the data collector and monitoring agent is closed but the data collector continues to write to log files. The monitoring agent processes these records but sets the PID value to -1.

Access the Log Analysis workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Log Analysis entry.

39. Lotus Workplace Server workspace

The Lotus Workplace Server workspace displays overall statistics for each Lotus Workplace application server being monitored by the monitoring agent.
This workspace does not support linking to ITCAM for Application Diagnostics Managing Server visualization engine.
Predefined workspace contains the following items:

Heap Usage - History bar chart, which displays free memory size and used memory size (in kilo bytes) within the WebSphere application server heap over time. The chart flyovers display the exact values
This view displays data provided by the Garbage Collection Analysis attributes.
Response Time - History graph, which shows the server response time to requests over time
This view displays data provided by the Request Times and Rates attributes.
Request Rate - History graph, which shows the rate at which requests have been received by this server over time
This view displays data provided by the Request Times and Rates attributes.
Percent CPU Used - History graph, which shows the percentage of the CPU that this server consumed over time
This view displays data provided by the application server attributes.
Application server Summary report, which displays overall information about this WebSphere application server, including JVM statistics and CPU usage statistics
This view displays data provided by the application server attributes.

Access the Lotus Workplace Server workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, click the Lotus Workplace Server entry of your choice.

40. Messages Queues workspace

This workspace provides aggregated statistics about the usage information about the message delivery on Lotus Workplace servers.
This workspace displays data provided by the Workplace Mail Queues attributes.
Note:

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

This workspace does not support linking to ITCAM for Application Diagnostics Managing Server visualization engine.
Predefined workspace contains the following items:

Queue Messages bar chart, which displays the number of messages in the ready, retry, unprocessed, and dead state in the queue during the sampling interval
Workplace Mail Message Queues report, which displays detailed information about the state of messages in each queue

Access the Messages Queues workspace

To access this workspace from the Workplace Mail workspace, use one of the following procedures:

Within the Navigator, right-click the Workplace Mail entry; then from the menu, click Workspace > Messages Queues.
From the primary monitoring portal menu, click View > Workspace > Messages Queues.

41. Messaging Engine Communications workspace

This workspace provides aggregated counter statistics for all the messaging engines being hosted by the current application server. WebSphere application server 5.1 based products do not support this workspace.
This workspace displays data provided by the Messaging Engine Communications attributes.
Note:

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Situation Event Console report, which shows the event activity for situations associated with the current Navigator item and any items within the branch. The Navigator alerts you when a situation becomes true by overlaying the Navigator item with an event indicator. This report is useful when multiple alerts are raised and you might not know newly arrived alerts just by looking at the indicator.
Messaging Engine Communications report, which displays information about the messaging engine communications, including API connections, errors, reads, writes, message written and message read.

Access the Messaging Engine Communications workspace

To access this workspace from the Platform Messaging workspace, use one of the following procedures:

Within the Navigator, right-click the Platform Messaging entry; then, from the menu, click Workspace > Messaging Engine Communications.
From the primary monitoring portal menu, click View >Workspace > Messaging Engine Communications.

42. Messaging workspace

In this workspace, you can view of performance counters of the Messaging Engines supported by a server. WebSphere application server 5.1 based products do not support this workspace.
This workspace displays data provided by the Messaging Engines attributes.
Note:

This workspace reports zeros for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Average Local Wait Time - History graph, which shows the historical time spent by messages on this durable subscription on consumption
Expired Messages - History graph, which shows the number of report-enabled messages that expired while on this queue
Incomplete Topic Publications - History graph, which shows the number of publications not yet received by all historical subscribers.
Total Published - History graph, which shows the historical number of publications to the messaging engines.
Messaging Engines report, which displays the aggregated information about each messaging engine. A messaging engine is a server component that provides the core messaging functionality of a service integration bus. A messaging engine manages bus resources and provides a connection point for applications

Access the Messaging workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Platform Messaging entry.

43. OS Stack workspace

This workspace displays information about the operating system performance.
This workspace displays data provided by the application server attribute group.

Predefined workspace contains:

Current OS Stack Summary report which displays:

Server name
Platform CPU Used (ms)
System Paging

The feature Platform CPU Used (ms) does not apply the z/OS platform.
CPU Used chart
System Paging chart

Access the Selected Application - Configuration workspace

Access this workspace using one of the following methods:

Double click the OS icon in Resources workspace.
Right-click the OS icon in the Resources workspace and select Link To, then select OS Stack Trend.

44. Pool Analysis workspace

This workspace displays information about the usage of several types of pools associated with each application server, including web container pools, ORB pools, J2C connection pools, and database connection pools. This workspace helps you detect resource constraints and potential performance congestion.

This workspace reports zeros for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Web Container Pool Usage - History graph, which shows the configured maximum number of web container pooled threads and the average active threads in the web container pool
This view displays data provided by the Thread Pools attributes.
ORB Pool Usage - History graph, which shows the configured maximum number of ORB pooled threads and the average active threads in the ORB pool
This view displays data provided by the Thread Pools attributes.
Web Container Pool % at Max - History bar chart, which shows the maximum usage percentage for the web container pooled threads over time
This view displays data provided by the Thread Pools attributes.
ORB Pool % at Max - History bar chart, which shows the maximum usage percentage for the ORB pooled threads over time
This view displays data provided by the Thread Pools attributes.
Percent CPU Used - History graph, which shows the percentage of the CPU used over time
This view displays data provided by the application server attributes.
DB Connection % at Max - Current Interval bar chart, which shows the maximum usage percentage for a database connection pool over time
This view displays data provided by the DB Connection Pools attributes.
J2C Connection % at Max - Current Interval bar chart, which shows the maximum usage percentage for a J2C connection pool over time
This view displays data provided by the J2C Connection Pools attributes.

Access the Pool Analysis workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Pool Analysis entry.

45. Portal Pages Summary workspace

This workspace reports performances statistics about WebSphere Portal page response times completed on the interval. A historical version of this workspace provides a long-term view of a single portal page that you select.
The following workspace displays only if the request monitoring control level, monitoring level is set to Level2. For more information about the request monitoring control level, see Dashboard (Basic) tab.
This workspace displays data provided by the Portal Page Summary attributes.
Predefined workspace contains the following items:

Worst Response Times bar chart, which displays the worst average response times (in milliseconds) for portlet during the current interval
Most Popular Portal Pages bar chart, which shows the number of requests for portlet
Portal Pages report, which displays aggregated information about portal pages, including average response time and request count

Access the Portal Pages Summary workspace

To access this workspace from the Portal Summary workspace, use one of the following procedures:

Within the Navigator, right-click the Portal Summary entry; then, from the menu, click Workspace > Portal Pages Summary.
From the primary monitoring portal menu, click View > Workspace > Portal Pages Summary.

Selected Portal Page - History workspace

The Selected Portal Page - History workspace displays the historical information that corresponds to the information in the Portal Pages Summary workspace for a selected portal page. Historical information is collected over a specific time span. See the online help for monitoring portal for a detailed explanation of historical reporting.

Access the Selected Portal Page - History workspace

To access this workspace from the Portal Pages Summary workspace, use one of the following procedures:

From the Portal Pages report, right-click the link icon and from the menu, click Selected Portal Page - History.
From the Worst Response Times bar chart, or the Most Popular Portal Pages bar chart, right-click any bar; then, from the menu, click Link To > Selected Portal Page - History.

46. Portal Summary workspace

The workspace reports summarize statistics about response times and functional decomposition of additional requests collected for WebSphere Portal applications. These include statistics about Portal Pages/Gateway Servlet aggregated response times collected on the interval. Others find grained statistics about Portlet, Model Building, Page Loading, Authentication, and Authorization requests response times collected on the same interval. By default, this workspace is configured for long-term historical interval reporting.
The following workspace displays only if the request monitoring control level, monitoring level is set to Level2. For more information about the request monitoring control level, see Dashboard (Basic) tab.
This workspace displays data provided by the Portal Summary attributes.
Predefined workspace contains the following items:

Portal Pages/Gateway Servlet - History graph, which shows the historical average response time (in milliseconds) of portal pages/Gateway Servlet
Portlet - History graph, which shows the historical average response time (in milliseconds) of portlets
Model Building - History graph, which shows the historical response time (in milliseconds) of model building
Page Loading - History graph, which shows the historical response time (in milliseconds) of page loading
Authentication - History graph, which shows the historical response time (in milliseconds) of authentication
Authorization - History graph, which shows the historical response time (in Milliseconds) of authorization

Access the Portal Summary workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere Portal server of your choice.
Within that server list of available WebSphere Portal Server workspaces, click the Portal Summary entry.

47. Portlet Summary and Selected Portlet - History workspaces

These workspaces reports performances statistics about WebSphere Portal portlet response times completed on the interval.

Portlet Summary workspace

The Portlet Summary workspace displays only if the request monitoring control level, monitoring level is set to Level2. For more information about the request monitoring control level, see Dashboard (Basic) tab.
A historical version of this workspace provides a long-term view of a single portlet that you select. This workspace displays data provided by the Portlet Summary attributes.
Predefined workspace contains the following items:

Worst Response Times bar chart, which displays the worst average response times (in milliseconds) for portlet in the current interval
Most Popular Portlets bar chart, which shows the exception and request rates (in events per second) for portlet
Portlets report, which displays aggregated information about portlets, including average response time, request count and request rate

Access the Portlet Summary workspace

To access this workspace from the Portal Summary workspace, use one of the following procedures:

Within the Navigator, right-click the Portal Summary entry; then, from the menu, click Workspace > Portlet Summary.
From the primary monitoring portal menu, click View > Workspace > Portlet Summary.

Selected Portlet - History workspace

The Selected Portlet - History workspace displays the historical information that corresponds to the information in the Portal Summary workspace for a selected portlet. Historical information is collected over a particular measured time span. See the online help for monitoring portal for a detailed explanation of historical reporting.

Access the Selected Portlet - History workspace

To access this workspace from the Portlet Summary workspace, use one of the following procedures:

From the Portlets report, right-click the link icon and from the menu, click Selected Portlet - History.
From the Worst Response Time bar chart, or the Most Popular Portlets bar chart, right-click any bar; then, from the menu, click Link To > Selected Portlet - History.

For more information, see:

48. Request Analysis workspace

The workspace reports response times and functional decomposition information about requests (including servlets, JSPs, and EJB methods) that completed during the interval.
A historical version of this workspace provides a long-term view of a single request that you select. This workspace displays data provided by the Request Analysis attributes.
Predefined workspace contains the following items:

Worst Average Response Times bar chart, which displays the five worst response times for requests processed during the current interval
Worst Completion Rates bar chart, which displays the 11 requests that have the worst completion rates
Requests - Current Interval report, which displays detailed information about the response times recorded for each request

Access the Request Analysis workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Request Analysis entry.

Selected Request - History workspace

The Selected Request - History workspace displays the historical information that corresponds to the information in the Request Analysis workspace for a single request type that you select. Historical information is collected over a specific time span. See the online help for monitoring portal for a detailed explanation of historical reporting.

Access the Selected Request - History workspace

To access this workspace from the Request Analysis workspace, use one of the following procedures:

From the Requests - Current Interval report, right-click the link icon and from the menu, click Selected Request - History.
From the Worst Average Response Times bar chart, right-click any bar; then, from the menu, click Link To > Selected Request - History.

The following workspaces are displayed only if the request monitoring control level, monitoring level is set to Level2. For more information about the request monitoring control level, see Dashboard (Basic) tab.

Selected Request - Datasource
Selected Request - JMS Queues
Selected Request - Resource Adapters
Selected Request - Service Components

Access the managing server visualization engine from the Request Analysis workspace

To use this functionality, you need ITCAM for Application Diagnostics Managing Server.
In the monitoring portal access the request analysis workspace, see ..."> Access the Request Analysis workspace. You can use you can use the following links to access the managing server visualization engine.

Diagnostic Recent Completed Requests
Diagnostic In-flight Request Search
Diagnostic SMF Data (This option is only available if the monitoring portal is connected to a z/OS data controller.)
For information about access requirements, see ">Prerequisites for access.

In the Requests - Current Interval window, right-click the choose link icon then click one of the following options:

Diagnostic Recent Completed Requests
Diagnostic In-flight Request Search

To view Diagnostic Recent Completed Requests or Diagnostic In-flight Request Search in a z/OS environment, right click the link icon on a row where the ASID column displays Summary.

Click Selected Request Servant Regions .
In the Selected Requests - Servant Regions Current Interval table, right-click the link icon on a row.
Click Diagnostic Recent Completed Requests or Diagnostic In-flight Request Search.

To view Diagnostic SMF Data (z/OS data collector only) right-click the link icon on a row where the ASID column displays Summary.

Click Selected Request Servant Regions.
In the Selected Requests - Servant Regions Current Interval table, right-click the link icon on a row.
Click Diagnostic SMF.
For information about the options available in a z/OS environment, refer to Region workspaces in a z/OS environment and ..."> Access a Region workspace
If this is your first time to access the managing server visualization agent during the session, you see a Welcome to the Application Monitor page.
Depending on the user setup configuration in your environment you might have to type your managing server visualization engine User Name and Password. If you do, you need to log in only once per session using your User Name and Password.
Click OK to display the relevant page in the managing server visualization engine.

If you click Diagnostic Recent Completed Requests you see the Server Activity Display page.
If you click Diagnostic In-flight Request Search you see the In-Flight Request Search page.
If you click Diagnostic SMF Data you see the SMF Overview page.

The information in these pages relates directly to the context from where you launched the link in the Tivoli Enterprise Portal.
To return to the previous workspace in the monitoring portal interface at any time choose from the following options:

From the monitoring portal desktop client, including WebStart, click the back arrow on the Portal toolbar.
From the monitoring portal browser client, click the browser back arrow.

49. Request Baseline workspace

This workspace displays aggregated information about the request baseline.
The baselining collects statistical information about an application requests completion times and uses this information to assign fair and bad thresholds on the application requests. The product divides the whole request response times into buckets and collects individual hits into each bucket. Use these attributes to get statistics from individual requests collected during baselining interval.
This workspace displays data provided by the Baseline attributes.
Predefined workspace contains:

Baseline Data report, which shows lower and upper boundaries for each bucket request as well as the breakdown of nested request types in percentage.
Request Label report, which shows the monitoring configuration settings for selected requests, including auto-threshold settings and actual thresholds calculated from the baseline data.
Nested Delays Distribution bar chart, which displays a bar for each bucket of response times across the different nested types (JDBC, JCA, JMS, and so on). This chart provides you with additional hints and insight about how to interpret response times distribution displayed in the distribution chart.
Response Time Distribution bar chart, which displays the distribution of the servlet response times on the baselining interval, also called zones.

You can use the bar charts to customize automatic request time thresholds. See Enable_Auto_Threshold: set threshold parameters.

Access the Request Baseline workspace

Complete the following steps to access this workspace: :

Access the Application Configuration workspace.
In the Application Requests table, right-click the link icon and click Request Baseline.

50. EJB Tier Analysis workspace

The workspace displays detailed information about application tier health for a selected WebSphere application.
The application tier health is derived from the following performance statistics:

Calculated application request delays in EJB container or custom requests delays compared against corresponding thresholds assigned in application configuration.
Completion rates for application edge EJB requests.
Application server ORB thread pool utilization level.
PMI statistics for application EJB container transactions begin, commit, and rollback rates.

This workspace displays data provided by the Application Health Status attributes.
Predefined workspace contains:

Application Tier Analysis report, which shows the overall health status of the Application tier for a selected application. For Tivoli Enterprise Monitoring Agent running on z/OS, region ID can be found in the ASID column.
Container Pool Usage bar chart, which displays the average number of concurrently active threads and the average number of free threads in the pool. This view displays data provided by the Thread Pools attributes.
Worst Application Tier Delays bar chart, which displays the top 10 delayed requests in the application tier. This view displays data provided by the Request Analysis attributes.
Worst Application Tier Completion Rates bar chart, which displays the top 10 worst requests in the application tier. This view displays data provided by the Request Analysis attributes.
Container Transactions - Rates bar chart, which displays the counts of global and local transactions that were started, committed, and undone during the interval. This view displays data provided by the Container Transactions attributes.
JVM Health - CPU Used % graph, which displays the percentage of the CPU used by the Java. Virtual Machine (JVM) during the interval. This view displays data provided by the application server attributes.
JVM Health - Heap Used % graph, which displays the current heap usage for the monitored JVM. This view displays data provided by the Garbage Collection Analysis attributes.
JVM Health - GC Active Time % graph, which displays the percentage of real time that the garbage collector was active during the interval. This view displays data provided by the Garbage Collection Analysis attributes.

Access the EJB Tier Analysis workspace

To access this workspace from the Application Health Summary workspace, use the following procedures:

From the Application Health Summary report, right-click the link icon and, from the menu, click Selected Application - EJB Tier Analysis.

51. Application Configuration workspace

This workspace displays the information about the configuration details of the selected application.
The workspace contains information about application requests and the corresponding thresholds assigned to them, as well as about status and configuration for application baselining activity. An entry is created for each application in the configuration report when a WebSphere application is discovered by the monitoring agent. The data is also stored in a context file local to monitoring agent where it can persist between monitoring agent restarts.
This workspace displays data provided by the Application Monitoring Configuration attributes.
Predefined workspace contains:

Longest Request Thresholds - Top 10 bar chart, which displays the 10 longest (in time) request thresholds configured for the given application (Servlet/JSP URL or EJB class/method call).
Application Requests report, which shows the discovered application requests and thresholds assigned to them. Click the link in the Application Request Configuration report or right-click and select Selected Request - Baseline to go to the Request Baseline Workspace. The link to the Selected Request - Baseline is disabled when the baseline request count is less than or equal to 0.
Application report, which shows the common details about application configuration, including custom requests monitoring levels for application and current baselining status.

Access the Application Configuration workspace

To access this workspace from the Application Health Summary workspace, use the following procedures:

From the Application Health Summary report, right-click the link icon and from the menu, click Application Configuration.

52. Backend Tier Analysis workspace

This workspace displays information about the details of the backend tier for a selected application.
This workspace displays data provided by the Application Health Status attributes.
Predefined workspace contains:

Backend Tier Analysis report, which shows the overall health status of the backend tier for a selected application. For monitoring agents running on z/OS, region ID can be found in the ASID column.
Worst Backend Tier Delays bar chart, which displays the top 10 delayed requests in the backend tier. This view displays data provided by the Request Analysis attributes.
Most Used JDBC resources bar chart, which displays the average time per request used by queries and updates to the data source. This view displays data provided by the Datasources attributes.
Most Used JMS Resources bar chart, which displays the longest times your application spent in getting messages from a queue, putting messages onto a queue, publishing messages to a queue, or browsing messages on a queue during the interval. This view displays data provided by the JMS Summary attributes.
Most Used JDBC Pools bar chart, which displays the average percentage of the connection pool in use during the interval. This view displays data provided by the DB Connection Pools attributes.
Most Used JCA Pools bar chart, which displays the average percent of the pool that is in use for the interval. This view displays data provided by the J2C Connection Pools attributes.
JVM Health - CPU Used % graph, which displays the percentage of the CPU used by the Java Virtual Machine (JVM) during the interval. This view displays data provided by the application server attributes.
JVM Health - Heap Used % graph, which displays the current heap usage for the monitored JVM. This view displays data provided by the Garbage Collection Analysis attributes.
JVM Health - GC Active Time % graph, which displays the percentage of real time that the garbage collector was active during the interval. This view displays data provided by the Garbage Collection Analysis attributes.

Access the Backend Tier Analysis workspace

To access this workspace from the Application Health Summary workspace, use the following procedures:

From the Application Health Summary report, right-click the link icon and from the pop-up menu, click Backend Tier Analysis.

53. Application Health History workspace

The workspace displays the information about the historical health status of a selected application. By default, the history data is collected for the last 24 hours.
The workspace displays data provided by the Application Health Status attributes.
Predefined workspace contains:

Availability/Throughput - History graph, which displays average request processing rate by application over the time. This view displays data provided by the Request Times and Rates attributes.
Availability/Completion Rate - History graph, which displays the average request completion rate by application over the time; Completion rate is defined as ratio of successfully completed requests count to the total count of requests processed by application on the interval. This view displays data provided by the Request Times and Rates attributes.
Availability/Average Load- History graph, which displays the average number of concurrent application requests over the time. This view displays data provided by the Request Times and Rates attributes.
Response Time - History graph, which displays the average application response time over the time. This view displays data provided by the Request Times and Rates attributes.
Server Resources/CPU Used - History graph, which displays the percent of CPU time used by the application JVM process over the time. This view displays data provided by the application server attributes.
Server Resources/Paging Rate - History graph, which displays the system paging rate in kilobytes per second over the time. This view displays data provided by the application server attributes.
Server Resources/GC Active Time - History graph, which displays the percentage of total CPU time for which the garbage collector was active over the time. This view displays data provided by the Garbage Collection Analysis attributes.

Access the Application Health History workspace

Complete the following steps to access this workspace from the Application Health Summary:

Click Application Health Summary report.
Right-click the link icon to display the pop-up menu.
Click Application Health history.

54. Web Tier Analysis workspace

This workspace displays detailed information about the client tier health for a selected WebSphere application.
The client tier health indicator is derived from the following performance statistics:

Calculated application request delays inside Servlet/JSP or Portal container compared against corresponding thresholds assigned in application configuration.
Completion rates for edge Servlet/JSP and Portal application requests.
Application server WebContainer thread pool utilization level.
PMI statistics for HTTP session counts by application.

This workspace displays data provided by the Application Health Status attributes.
Predefined workspace contains:

Web Tier Analysis report, which shows the overall health status of application execution in web or portal containers. For monitoring agents running on z/OS, region ID can be found in the ASID column.
Web Contain bar chart, which displays the current utilization level of the web Container thread pool. This view displays data provided by the Thread Pools attributes.
HTTP Sessions - Average bar chart, which displays the average number of concurrently active and live HTTP session numbers for the selected application during the interval. This view displays data provided by the Servlet Sessions attributes.
Worst Web Tier Delays bar chart, which displays the top 10 requests with biggest delays (threshold violations) in the client tier. This view displays data provided by the Request Analysis attributes.
Worst Web Tier Completion Rates bar chart, which displays the top 10 Servlet/JSP/Portal edge requests with the worst completion rates. This view displays data provided by the Request Analysis attributes.
JVM Health - CPU Used % graph, which displays the percentage of the host CPU used by the Java. Virtual Machine (JVM) during the interval. This view displays data provided by the application server attributes.
JVM Health - Heap Used % graph, which displays the current heap usage for the monitored JVM. This view displays data provided by the Garbage Collection Analysis attributes.
JVM Health - GC Time % graph, which displays the percentage of real time that the garbage collector was active during the interval. This view displays data provided by the Garbage Collection Analysis attributes.

Access the Web Tier Analysis workspace

Complete the following steps to access this workspace from the Application Health Summary:

Click Application Health Summary report.
Right-click the link icon and from the menu click Web Tier Analysis.

55. Selected Datasources - Datasource Trend workspace

The Datasources Trend workspace displays information about datasource connections.
This workspace displays data provided by the Datasources attributes.
Predefined workspace contains the following items:

Current Datasources report displays datasource name, total wait time, connection rate, connection average wait time and connection max wait time.
Total Wait Time Trend line chart displays the total time that applications had to wait for a connection to the data source.
Connection Rate Trend bar chart displays the number of connection requests (per second) created for the data source.
Connection Average and Max Time Trend line chart displays the average time (in milliseconds) and the worst-case time (in milliseconds) that applications had to wait for a connection.

56. Selected Request - Datasources workspace

The Selected Request - Datasources workspace displays information about JDBC activity performed by the request you selected in the primary Request Analysis workspace.
This workspace displays data provided by the Selected Request attributes.
Predefined workspace contains the following items:

Worst Datasources Response Times bar chart, which shows the worst response times (in milliseconds) for data sources accessed by this request
Selected Request - Datasources report, which displays detailed information about the data sources accessed for the selected request. For monitoring agents running on z/OS, region ID can be found in the ASID column.

Access the Selected Request - Datasources workspace

To access this workspace from the Request Analysis workspace, use one of the following procedures:

From the Requests - Current Interval report, right-click the link icon and from the menu, click Selected Request - Datasources.
From Worst Average Response Times bar chart, right-click any bar; then, from the menu, click Link To > Selected Request - Datasources.

57. Selected Request - JMS Queues workspace

The Selected Request - JMS Queues workspace displays information about message queues owned by messaging middleware and accessed by the request that you selected in the primary Request Analysis workspace.
This workspace displays data provided by the Selected Request attributes.
Predefined workspace contains the following items:

Worst JMS Queues Response Times bar chart, which shows the worst response times (in milliseconds) for JMS resources accessed by this request
Selected Request - JMS Queues report, which displays detailed information about the JMS resources accessed by the selected request. For monitoring agents running on z/OS, region ID can be found in the ASID column.

Access the Selected Request - JMS Queues workspace

To access this workspace from the Request Analysis workspace, use one of the following procedures:

From the Requests - Current Interval report, right-click the link icon and from the menu, click Selected Request - JMS Queues.
From Worst Average Response Times bar chart, right-click any bar; then, from the menu, click Link To > Selected Request - JMS Queues.

58. Selected Request - Portal Processing workspace

The Selected Request - Portal Processing workspace displays information about portlet, or portal page response times, or both, referenced by the request you selected in the primary Request Analysis workspace.
This workspace displays data provided by the Selected Request attributes.
Note: This workspace appears under all WebSphere application servers, but it has data only under the WebSphere Portal Server.
Predefined workspace contains the following items:

Worst Portal Processing Response Times bar chart, which shows the worst response times (in milliseconds) for portal sources accessed by this request
Selected Request - Portal Processing report, which displays detailed information about the portal sources accessed for the selected request. For monitoring agents running on z/OS, region ID can be found in the ASID column.

Access the Selected Request - Portal Processing workspace

To access this workspace from the Request Analysis workspace, use one of the following procedures:

From the Requests - Current Interval report, right-click the link and from the menu, click Selected Request - Portal Processing.
From Worst Average Response Times bar chart, right-click any bar; then, from the menu, click Link To > Selected Request - Portal Processing.

59. Selected Request - Resource Adapters workspace

The Selected Request - Resource Adapters workspace displays response-time information about the J2C resources adapters referenced by the request you selected in the primary Request Analysis workspace.
This workspace displays data provided by the Selected Request attributes.
Predefined workspace contains the following items:

Worst Average Response Times bar chart, which shows the worst-performing J2C resource adapter nested requests, in milliseconds
Selected Request - Resource Adapters report, which displays detailed information about each J2C resource adapter that was accessed by the selected request. For monitoring agents running on z/OS, region ID can be found in the ASID column.

Access the Selected Request - Resource Adapters workspace

To access this workspace from the Request Analysis workspace, use one of the following procedures:

From the Requests - Current Interval report, right-click the link icon and from the menu, click Selected Request - Resource Adapters.
From Worst Average Response Times bar chart, right-click any bar; then, from the menu, click Link To > Selected Request - Resource Adapters.

60. Selected Request - Service Components workspace

The Selected Request - Service Components workspace displays information about Service Component Architecture (SCA) activity performed by the request you selected in the primary Request Analysis workspace.
This workspace displays data provided by the Selected Request attributes.
Predefined workspace contains the following items:

Worst Service Components Response Times bar chart, which shows the worst response times (in milliseconds) for data sources accessed by this request
Selected Request - Service Components report, which displays detailed information about the data sources accessed for the selected request. For monitoring agents running on z/OS, region ID can be found in the ASID column.

Access the Selected Request - Service Components workspace

To access this workspace from the Request Analysis workspace, use one of the following procedures:

From the Requests - Current Interval report, right-click the link icon and from the menu, click Selected Request - Service Components.
From Worst Average Response Times bar chart, right-click any bar; then, from the menu, click Link To > Selected Request - Service Components.

61. Service Component Elements workspace

This workspace lists performance metrics for all the service components and their elements. Service components contain one or more elements, which are sets of different steps processed in each service component. In turn, each element has its own set of event natures, which are key points that are reached when processing a service component element.
This workspace displays data provided by the Service Component Elements attributes.
Note:

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Worst Service Times bar chart, which shows the numbers of the Average Response Time in milliseconds
Most Invocations bar chart, which shows the numbers of the invocations per second
Most Failures bar chart, which shows the numbers of the failed invocation counts
Service Component Elements report, which shows aggregated data about the average response time, failed count, success count, error rate, and request rate.

Access the Service Component Elements workspace

To access this workspace from the Service Components workspace, use one of the following procedures:

Within the Navigator, right-click the Service Components entry; then, from the menu, click Workspace > Service Component Elements.
From the primary monitoring portal menu, click View > Workspace > Service Component Elements.

62. Selected Request - History workspace

The Selected Request - History workspace displays information about historical request instances for the named request you selected in the primary Request Analysis workspace.
This workspace displays data provided by the Selected Request attributes.
Predefined workspace contains the following items:

Selected Request Response Times - History bar chart, which shows the average response times (in milliseconds) spent within various request types in instances of this named request.
Selected Request - History sources report, which displays detailed information about historical request instances for the selected request.

Click the icon to select a time span. The item displays the data for the selected time span.

Access the Selected Request - data sources workspace

To access this workspace from the Request Analysis workspace, use one of the following procedures:

From the Requests - Current Interval report, right-click the link icon and select Selected Request - History.
From Worst Average Response Times bar chart, right-click any bar and select Link To > Selected Request - History.

63. Service Components workspace

This workspace provides overview performance of the key service components. WebSphere servers feature their own service components, and each of these components has its own set of event points that can be monitored.
This workspace displays data provided by both the Service Components attributes. This workspace is available only for WebSphere Process Server and WebSphere ESB Server.
Note:

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Service Component Architecture - History graph, which shows historical bad request count, the instrumentation level, set instrumentation level type, and summary, when the component name of the service is Service Component Architecture
Business Rules - History graph, which shows historical bad request count, the instrumentation level, set instrumentation level type, and summary, when the name is Business Rules
Map - History graph, which shows historical bad request count, the instrumentation level, set instrumentation level type, and summary, when the name is Map
Mediation - History graph, which shows historical bad request count, the instrumentation level, set instrumentation level type, and summary, when the name is Mediation
Business State Machine - History graph, which shows historical bad request count, the instrumentation level, set instrumentation level type, and summary, when the name is Business State Machine
Selector - History graph, which shows historical bad request count, the instrumentation level, set instrumentation level type, and summary, when the name is Selector
Bad Requests report, which displays a summary of the bad request counts

Access the Service Components workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Service Components entry.

64. Servlets/JSPs - Selected Web Application workspace

This workspace displays statistical data regarding the servlets and JSPs invoked by a single Web application.
This workspace displays data provided by the Servlets JSPs attributes.
Note:

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Worst Servlet/JSP Response Times bar chart, which displays the worst average response times (in milliseconds) for servlets and JSP invoked by the selected web application
Most Popular Servlet/JSP bar chart, which shows the servlet and JSP exception and request rates (in events per second) for the selected application
Worst Servlet/JSP Error Rates bar chart, which shows the worst servlet and JSP error rates for the selected application during the interval
Servlets/JSPs - Selected Web Application report, which displays performance information about the servlets and JSPs invoked by the application. For example, this report displays the average number of concurrent requests for a servlet and the amount of time it takes a servlet to respond to a request

Access the Servlets/JSPs - Selected Web Application workspace

To access this workspace from the Web Applications workspace, use one of the following procedures:

From the Web Applications report, right-click the link icon and from the menu, click Servlets/JSPs - Selected Web Application.
From the Worst Response Times bar chart, the Most Popular Web Applications bar chart, or the Worst Error Rates bar chart, right-click any bar; then, from the menu, click Link To > Servlets/JSPs - Selected Enterprise Application.

65. Scheduler workspace

The Scheduler workspace contains data for the Scheduler service. The scheduler service schedules and tracks the starting and stopping of applications.
This workspace displays data provided by the Scheduler attributes.
Note:

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Highest Task Failures bar chart, which shows the number of the task failure count. The y-axis headings correspond to the row number of the Scheduler report
Highest Completed Tasks bar chart, which shows the number of the task finished count. The y-axis headings correspond to the row number of the Scheduler report
Schedulers report, which displays information about the scheduler data, including task finish count, task failure count, task expiration rate, task finish rate, and task run rate

Access the Scheduler workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Scheduler entry.

66. Sessions workspace

This workspace displays information about servlet sessions.
A session is a series of requests to a servlet, originating from the same user at the same browser. Applications running in a web container can use these sessions to track individual users. This workspace displays data provided by the Servlet Sessions attributes.
Note:

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Most Active Sessions bar chart, which shows the most frequently referenced servlet sessions for each listed web application
Largest Total Session Object Sizes bar chart, which shows the total session object sizes (in bytes) and the associated web applications
Servlet Sessions report, which shows usage data about the servlet sessions, including the rates as which sessions are created and destroyed and their read and write times

Access the Sessions workspace

To access this workspace from the Web Applications workspace, use one of the following procedures:

Within the Navigator, right-click the Web Applications entry; then, from the menu, click Workspace > Servlet Sessions.
From the primary monitoring portal menu, click View > Workspace > Servlet Sessions.

67. Thread Pools workspace

This workspace reports information about the various thread pools that support the applications running in your Java. Virtual Machine (JVM).
This workspace displays data provided by the Thread Pools attributes.
Note:

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Highest Average Pool Sizes bar chart, which shows the largest thread pools in the JVM
Average Thread Pool Usage bar chart, which shows the average active and free threads for each thread pool
Thread Pools report, which shows information about the usage statistics for thread pools that belong to a WebSphere application server, such as average and maximum pool sizes and creation and destruction rates

Access the Thread Pools workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Thread Pools entry.

Access the managing server visualization engine from the Thread Pools workspace

To use this functionality, you need ITCAM for Application Diagnostics Managing Server.
In the monitoring portal access the Thread Pools workspace. You can use the Diagnostic Server Activity Display link to access the managing server visualization engine. For information about access requirements see ">Prerequisites for access.

In the Thread Pools window, right-click the choose link icon then click Diagnostic JVM Thread Display.
If this is your first time to access the managing server visualization agent during a session, you see a Welcome to the Application Monitor page.
Depending on the user setup configuration in your environment you might have to type your managing server visualization engine User Name and Password. If you do, you need only to log in using your User Name and Password once per session.
Click OK to display the Diagnostic JVM Thread Display page in the managing server Visualization engine. You can use link to diagnose application problems, for example, slow transactions or high response times.
The results relate directly to the context from where you launched the link in the monitoring portal. For more information about using the Diagnostic JVM Thread Display page and additional features, refer to the Composite Application Manager help within the managing server visualization engine Interface.
To return to the previous workspace in the monitoring portal interface at any time choose from the following options:

From the monitoring portal desktop client, including WebStart, click the back arrow on the Portal toolbar.
From the monitoring portal browser client, click the browser back arrow.

68. Thread Pool Trend workspace

The Thread Pool Trend workspace displays information about thread pool size and usage.
This workspace displays data provided by the Selected Request attributes.
This predefined workspace contains the following items:

Current Thread Pool report displays thread pool name, average active threads, average pool size, percentage of time pool at max and average free threads.
Average Pool Size Trend bar chart displays the average number of threads in the pool.
Average Thread Pool Usage Trend bar chart displays the average percentage of time that all threads were in use during the sampling interval.
Percent of Time Pool Size at Max Trend bar chart displays the percentage of time the pool size is running at the maximum value.

Access the Threadpool Trend workspace

Select the Thread Pools workspace, in the Thread Pools report, click the link icon, and select Thread Pool Trend.

69. Web Applications workspace

This workspace displays information about the web applications running in J2EE application servers.
This workspace displays data provided by the Web Applications attributes.
Note:

The Web Applications workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

Worse Response Times bar chart, which shows the worst servlet response times (in milliseconds) during the interval
Most Popular Web Applications bar chart, which shows the servlet exception and request rates (in events per second)
Worse Error Rates bar chart, which shows the worst servlet error rates during the interval
Web Applications report, which displays aggregated performance data for each web application, about all servlets and JSPs deployed to that web application, including response and error rates, and response times.

Access the Web Applications workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Web Applications entry.

Access the managing server visualization engine from the Web Applications workspace

To use this functionality, you need ITCAM for Application Diagnostics Managing Server.
In the Tivoli Enterprise Portal access the WebSphere Agent workspace. You can use the Diagnostic Server Activity Display link to access the managing server visualization engine. For information about access requirements, see ">Prerequisites for access.

In the Web Applications window, right-click the choose link icon then click Diagnostic Server Activity Display.
If this is your first time to access the managing server visualization agent during a session, you see a Welcome to the Application Monitor page.
Depending on the user setup configuration in your environment you might have to type your managing server visualization engine User Name and Password. If you do, you need to log in only once per session using your User Name and Password.
Click OK to display the Server Activity Display page in the managing server Visualization engine. You can use link to diagnose application problems, for example, slow transactions or high response times.
The results in this page relate directly to the context from where you launched the link in the Tivoli Enterprise Portal. For more information about using the Server Activity Display page and additional features, refer to the Composite Application Manager help within the managing server visualization agent Interface.
To return to the previous workspace in the Tivoli Enterprise Portal interface at any time choose from the following options:

From the Tivoli Enterprise Portal desktop client, including WebStart, click the back arrow on the Portal toolbar.
From the Tivoli Enterprise Portal browser client, click the browser back arrow.

70. Web Services workspace

The Web Services workspace displays information about the data counters of the web services.
The examples of the information include the number of loaded web services, the number of requests delivered and processed, the request response time, and the average size of requests. This workspace displays data provided by both the Web Services attributes and the Web Services Gateway attributes.
Note:

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains:

Worst Response Times bar chart, which displays the worst average response times (in milliseconds) for the selected web services
Most Popular bar chart, which shows the exception and request rates (in events per second) for the selected services
Web Services report, which displays aggregated performance data for each web service, including requests, response times, and payload sizes
Web Service Gateway report, which displays aggregated performance data for each Web service gateway, including the number of synchronous and asynchronous requests and responses

Access the Web Services workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Web Services entry.

Selected Web Services - History workspace

The Selected Web Services - History workspace displays the historical information that corresponds to the information in the Web Services workspace for a selected web service. Historical information is collected over a particular measured time span. See the online help for Tivoli Enterprise Portal for a detailed explanation of historical reporting.

Access the Selected Web Services - History workspace

To access this workspace from the Web Services workspace, use one of the following procedures:

From the Web Services report, right-click the link icon and from the menu, click Selected Web Services - History.
From the Worst Response Times bar chart, or the Most Popular bar chart, right-click any bar; then, from the menu, click Link To > Selected Web Services - History.

71. WebSphere Agent workspace

This workspace displays product events that affect the ability of the WebSphere application server agent to collect data.
This workspace displays events occurring within the WebSphere application server agent and WebSphere application servers that are installed on the host computer. It also displays the status of the monitoring agent. Predefined workspace contains the following items:

Agent Events report, which displays information about agent-level events that affect the ability of the monitoring agent to collect data for the WebSphere application server. You can use this view to see exception and error messages, their IDs, and their severity.
The Agent Events report also shows the result of issuing a Take Action command. Place your cursor over a truncated message to display the text of the complete message
This report displays data reported by the WebSphere Agent Events attributes.
Application Servers Summary report displays information about status of the WebSphere server.
This report displays data reported by the application server Status attributes.

Access the WebSphere Agent workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of available monitoring agents, if the WebSphere Agent entry has a name next to it (for example, WebSphere Agent - Primary), click the entry. Otherwise, expand the entry and click one of the agent names.

Access the managing server visualization engine from the WebSphere Agent workspace

To use this functionality, you need ITCAM for Application Diagnostics Managing Server.
In the Tivoli Enterprise Portal access the WebSphere agent workspace. You can use the Diagnostic Server Activity Display or the Diagnostic In-flight Request Search link to access the managing server visualization engine. For information about access requirements, see ">Prerequisites for access.

In the Applications Server Summary window, right-click the choose link icon then click Diagnostic Server Activity Display or Diagnostic In-flight Request Search.
If this is your first time to access the managing server visualization agent, during the session you see a Welcome to the Application Monitor page.
Depending on the user setup configuration in your environment, you might have to type your managing server visualization engine User Name and Password. If you do, you need to log in only once per session using your User Name and Password.
Click OK to display the relevant page in the managing server Visualization engine.

If you click Diagnostic In-flight Request Search you see the In-Flight Request Search page in managing server visualization engine.
If you click Diagnostic Server Activity Display you see the Server Activity Display page in the managing server visualization engine.

The information in both of these pages relates directly to the context from where you launched the link in the Tivoli Enterprise Portal.
To return to the previous workspace in the Tivoli Enterprise Portal interface at any time choose from the following options:

From the Tivoli Enterprise Portal desktop client, including WebStart, click the back arrow on the Portal toolbar.
From the Tivoli Enterprise Portal browser client, click the browser back arrow.

72. WebSphere Application Server workspace

The WebSphere Application Server workspace displays overall statistics for each application server being monitored by the monitoring agent.
Predefined workspace contains the following items:

Heap Usage - History bar chart, which displays free memory size and used memory size (in kilobytes) within the WebSphere Application Server heap over time. The chart flyovers display the exact values
This view displays data provided by the Garbage Collection Analysis attributes.
Response Time - History graph, which shows the server response time to requests over time
This view displays data provided by the Request Times and Rates attributes.
Request Rate - History graph, which shows the rate at which requests have been received by this server over time
This view displays data provided by the Request Times and Rates attributes.
Percent CPU Used - History graph, which shows the percentage of the CPU that this server used over time
This view displays data provided by the application server attributes.
Application server Summary report, which displays overall information about this WebSphere Application Server, including JVM statistics and CPU usage statistics
This view displays data provided by the application server attributes. In the application server summary report, each row represents a different region. When you right-click the link for a row, you can choose to go to Selected Region - application server Summary, Selected Region - Request Analysis, Selected Region - Application Health Status, Selected Region - Datasources, Selected Region - Log Analysis or Selected Region - JMS Summary. All these links are disabled when Tivoli Enterprise Monitoring Agent is running on Distributed data collector.

Access the WebSphere Application Server workspace

Complete the following steps to access this workspace:

Within the Navigator, expand Windows Systems, Linux Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, click the WebSphere App Server entry of your choice.

For more information, see:

73. WebSphere ESB Server workspace

The WebSphere ESB Server workspace displays overall statistics for each application server being monitored by the monitoring agent.
Predefined workspace contains the following items:

Heap Usage - History bar chart, which displays free memory size and used memory size (in kilo bytes) within the WebSphere application server heap over time. The chart flyovers display the exact values
This view displays data provided by the Garbage Collection Analysis attributes.
Response Time - History graph, which shows the server response time to requests over time
This view displays data provided by the Request Times and Rates attributes.
Request Rate - History graph, which shows the rate at which requests have been received by this server over time
This view displays data provided by the Request Times and Rates attributes.
Percent CPU Used - History graph, which shows the percentage of the CPU that this server consumed over time
This view displays data provided by the application server attributes.
Application server summary report, which displays overall information about this WebSphere application server, including JVM statistics and CPU usage statistics
This view displays data provided by the application server attributes.

Access the WebSphere ESB Server workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, click the WebSphere ESB Server entry of your choice.

For more information, see:

74. WebSphere Portal Server workspace

The WebSphere Portal Server workspace displays overall statistics for each application server being monitored by the monitoring agent.
Predefined workspace contains the following items:

Heap Usage - History bar chart, which displays free memory size and used memory size (in kilo bytes) within the WebSphere application server heap over time. The chart flyovers display the exact values
This view displays data provided by the Garbage Collection Analysis attributes.
Response Time - History graph, which shows the server response time to requests over time
This view displays data provided by the Request Times and Rates attributes.
Request Rate - History graph, which shows the rate at which requests have been received by this server over time
This view displays data provided by the Request Times and Rates attributes.
Percent CPU Used - History graph, which shows the percentage of the CPU that this server consumed over time
This view displays data provided by the application server attributes.
Application server summary report, which displays overall information about this WebSphere application server, including JVM statistics and CPU usage statistics
This view displays data provided by the application server attributes. In the application server summary report, each row represents a different region. When you right-click the link for a row, you can choose to go to Selected Region - application server Summary, Selected Region - Request Analysis, Selected Region - Application Health Status, Selected Region - Datasources, Selected Region - Log Analysis, Selected Region - JMS Summary, Selected Region - Portal Summary, Selected Region - Portlet Summary. All these links are disabled when monitoring agent is running on Distributed data collector and enabled when the monitoring agent is running on z/OS data collector.

Access the WebSphere Portal Server workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, z/OS Systems or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, click the WebSphere Portal Server entry of your choice.

For more information, see:

75. WMQ Client Link Communications workspace

This workspace provides aggregated counter statistics for all of the clients of WMQ Queue Managers that are or have been connected to this application server. WebSphere application server 5.1 based products do not support this workspace.
This workspace displays data provided by the WMQ Client Link Communications attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

WMQ Client Link Communication Errors - History graph, which shows the number of errors that have caused connections to WMQ JMS clients to be dropped
WMQ Client Link Statistics report, which displays information about the messaging engine communications, including batch sent, message sent, message received, comm errors, writes blocked, and reads blocked

Access the WMQ Client Link Communications workspace

To access this workspace from the Platform Messaging workspace, use one of the following procedures:

Within the Navigator, right-click the Platform Messaging entry; then, from the menu, click Workspace > WMQ Client Link Communications.
From the primary monitoring portal menu, click View > Workspace > WMQ Client Link Communications.

76. WMQ Link Communications workspace

This workspace provides aggregated counter statistics for all of the WMQ Queue Managers that are or have been connected to this application server. WebSphere application server 5.1 based products do not support this workspace.
This workspace displays data provided by the WMQ Link Communications attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

WMQ Link Communication Errors - History graph, which shows the historical number of communication errors that resulted in the disconnection of a network connection to a WMQ Queue Manager
WMQ Link Statistics report, which displays information about the messaging engine communications, including batches sent, batches received, message sent, message received, and comm errors

Access the WMQ Link Communications workspace

To access this workspace from the Platform Messaging workspace, use one of the following procedures:

Within the Navigator, right-click the Platform Messaging entry; then, from the menu, click Workspace > WMQ Link Communications.
From the primary monitoring portal menu, click View > Workspace > WMQ Link Communications.

77. Workload Management workspace

This workspace displays information about the Workload Management (WLM) server and about the WLM client that initiates workload requests to that server.
Workload management optimizes the distribution of client processing tasks. Incoming work requests are distributed to the application servers, enterprise beans, servlets, and other objects that can most effectively process the requests. Workload management also provides failover protection when servers are not available, improving application availability. In a WebSphere application server environment, you implement workload management using clusters, transports, and replication domains.
This workspace displays data provided by both the Workload Management Server attributes and the Workload Management Client attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

Predefined workspace contains the following items:

WLM Server Incoming Requests bar chart, which shows the incoming strong affinity requests and the incoming nonaffinity requests (per second)
WLM Client Outgoing Requests bar chart, which shows the outgoing requests (per second)
Workload Management Server report, which shows detailed information about the WLM server, such as incoming requests and clients served
Workload Management Client report, which shows information about the clients that initiate workload requests, such as outgoing requests and response times

Access the Workload Management workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Workload Management entry.

78. Workplace Mail workspace

This workspace provides aggregated statistics of the usage information about the incoming message traffic.
This workspace displays data provided by the Workplace Mail Service attributes.

This workspace reports blanks for resource data on the first invocation if PMI data collection is configured for on-demand sampling (that is, if your site set configuration value Resource Data Collection Method to On Demand) or if you have not yet run applications that generate PMI resource data. To report resource data in this workspace after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
Because of high processor usage, the monitoring agent provides on-demand sampling by default. To activate PMI monitoring, you must first select this workspace and then select it again later. Each time you select the workspace, it displays the data collected during the interval between selections.

This workspace does not support linking to ITCAM for Application Diagnostics Managing Server visualization engine.
Predefined workspace contains the following items:

Connections bar chart, which displays the number of connections to the SMTP server, SMTP client connections, and the maximum number of concurrent LDAP connections during the sampling interval
Workplace Mail report, which displays detailed information about the workplace mail connections

Access the Workplace Mail workspace

To access this workspace, complete the following steps:

Within the Navigator, expand Windows Systems, Linux Systems, or UNIX Systems, as appropriate for the node you are monitoring.
Within the node list, expand the entry that corresponds to the node to select.
Within that node list of monitored applications, expand the list of WebSphere agents.
Within the list of available agents, expand the WebSphere application server of your choice.
Within that server list of available WebSphere application server workspaces, click the Workplace Mail entry.

79. Region workspaces in a z/OS environment

For z/OS installations, workspace tables report data at both a region and server instance level.

monitoring agent for WebSphere Application Server on z/OS is available in separate product packages.
Note: monitoring agent for WebSphere Application Server 7.2 is not available on z/OS The advantage is that you can view metrics collected at both levels and switch between server instance level and region level. The following table lists the workspaces that show information at both a region and server level.
All workspaces except the Garbage Collection Analysis workspace report data on both levels. The Garbage collection analysis workspace does not have links to the top-level workspaces.

Workspaces and the Servant and Selected Regions in a z/OS environment

Workspace Table Name Link Name Description
WebSphere App Server - application server Summary
WebSphere App Server - application server Summary - Selected Region - application server Summary
Selected Region - Application Health Status
Selected Region - Request Analysis
Selected Region - Log Analysis
Selected Region - Data Sources
Selected Region - JMS - Summary

This workspace displays data at regional level. Click the Selected Region links to access region-specific links to other top-level workspaces. When a workspace is linked from the application server summary you can view specific drill-down metrics. To view a report for an individual region, see ..."> Access a Region workspace
Application Health - Application Health Summary
Selected Application - Servant regions
Selected Application - Health History
Selected Application- Web Tier Analysis
Selected Application - EJB Tier Analysis
Selected Application - Backend Tier Analysis
Selected Application - Request Analysis
Selected Application - Configuration

In an z/OS environment, the Application Health Summary report displays the total results for the server instances. To view report results by region, click the WebSphere App Server - application server Summary table and right-click a link icon in the table to view the available options.
Request Analysis - Requests Current Interval
Selected Request - Datasource
Selected Request - JMS Queues
Selected Request - Resource Adaptors
Selected Request - History
Selected Request - Servant Regions
In an z/OS environment, when you select Request Analysis - Requests Current Interval, this report displays the total results for the server instances. To view a report for an individual Request Analysis region, see ..."> Access a Region workspace.
Garbage Collection Analysis - Garbage Collection Analysis
Selected Region - History
Garbage Collection Analysis - Servant Region (only available when you click a [Summary] row)

For Garbage Collection Analysis, there is a summary report of all regions and there are also reports by individual region.
Log Analysis - Log Analysis
Selected Region - Log Analysis

Log Analysis workspace. In a z/OS environment, the log analysis workspace reports data in two ways. When you select the Log analysis workspace the report displays JVM Log Analysis and DC message events from all regions. To view a report for an individual log analysis region, see ..."> Access a Region workspace.
Data sources - Data sources - Current Interval
Selected Datasource
Selected Datasource - History
In an z/OS environment, this report displays the total results for the server instances. To view a report for an individual Data source region, see ..."> Access a Region workspace.
JMS Summary - JMS Summary - Current Interval JMS
Selected JMS - Servant Regions
In an z/OS environment, this report displays the total results for the server instances. To view a report for an individual JMS Summary region, see..."> Access a Region workspace.
WebSphere Portal Server
Selected Region - Portal Server Summary
In an z/OS environment, this report displays the total results for the server instances. To view a report for an individual Portal Server summary, see ..."> Access a Region workspace
Portal Summary
Selected Region - Portal Summary
Selected Region - Portlet Summary
Selected Portal Page - History
Selected Portlet - History
Selected Region - Portal Page Summary
In an z/OS environment report displays the total results for the server instances. To view a report for an individual region see ..."> Access a Region workspace

Access a Region workspace

To access this workspace, complete the following steps:

In the Navigator, expand z/OS system, as appropriate for the node you are monitoring.
In the node list, expand the entry that corresponds to the node to select.
In that node list of monitored agents, expand the list of the servers.
In the list of available servers, click the WebSphere agent of your choice.
In the list of available servers, select the Server of your choice.
Right-click the selected Server node and select WebSphere App Server workspace.
Right-click a link icon in the application server Summary table to display workspaces connected with the current region.
Select the workspace of your choice from the following list:

Selected Region application server Summary
Selected Region - Application Health Status
Selected Region - Request Analysis
Selected Region - Log Analysis
Selected Region - Data Sources
Selected Region - JMS - Summary

Attributes

Contents

1. Attribute groups used by the predefined workspaces
2. Alarm Manager attributes
3. Allocation Failure attributes
4. Application Health Status attributes
5. Application Monitoring Configuration attributes
6. Application server status attributes
7. Application server attributes
8. Baseline attributes
9. Client Communications attributes
10. Container Object Pools attributes
11. Container Transactions attributes
12. Data sources attributes
13. DB Connection Pools attributes
14. DC Messages attributes
15. DCS Stack attributes
16. Durable Subscriptions attributes
17. Dynamic Cache attributes
18. Dynamic Cache Templates attributes
19. EJB Containers attributes
20. Enterprise Java Beans attributes
21. Garbage Collection Analysis attributes
22. Garbage Collection Cycle attributes
23. High Availability Manager attributes
24. J2C Connection Pools attributes
25. JMS Summary attributes
26. Log Analysis attributes
27. Listener Port attributes
28. Messaging Engine Communications attributes
29. Messaging Engines attributes
30. Portal Page Summary attributes
31. Portal Summary attributes
32. Portlet Summary attributes
33. Queue attributes
34. Remote Configuration Requests attributes
35. Request Analysis attributes
36. Requests Monitoring Configuration attributes
37. Request Times and Rates attributes
38. Selected Request attributes
39. Servlet Sessions attributes
40. Servlets JSPs attributes
41. Scheduler attributes
42. Service Component Elements attributes
43. Service Components attributes
44. Thread Pools attributes
45. Topic Spaces attributes
46. Web Applications attributes
47. Web Services attributes
48. Web Services Gate Way attributes
49. WebSphere Agent Events attributes
50. WMQ Client Link Communications attributes
51. WMQ Link Communications attributes
52. Workload Management Client attributes
53. Workload Management Server attributes
54. Workplace Mail IMAP/POP attributes
55. Workplace Mail Queues attributes
56. Workplace Mail Service attributes
57. Agent Configuration attributes
58. KYN Command attributes
59. Server Configuration attributes

Attributes

The monitoring agent for WebSphere Application Server is a monitoring agent that resides within your distributed systems. This agent gathers data about running WebSphere Application Server processes that have been collected and stored by the ITCAM Data Collector for WebSphere, and stores those data in elements called attributes. Each attribute is a characteristic of an object. For example, the Receive Count attribute in the JMS Summary attribute group counts the number of messages your applications have retrieved from JMS messages queues.

Attribute groups

The monitoring agent for WebSphere Application Server attributes are organized into groups of related items. These attribute groups comprise the attribute tables for this agent. For example, the Garbage Collection Analysis attribute group provides information about the frequency with which the Java. Virtual Machine (JVM) invokes its garbage collector.

Attributes and workspaces

Within the monitoring portal workspaces, these attributes are displayed in, and correspond to, the columns in the reports and the items in the graphic displays for charts and graphs. You can use the collected data to analyze and monitor the performance of your WebSphere Application Server servers and the applications running within them. For an overview of the correlations between the predefined workspaces and the attribute groups, see Attribute Groups Used by the Predefined Workspaces.

Attributes and situations

Various attributes are referenced by the predefined situations of the product. You can also use the monitoring agent for WebSphere Application Server attributes to create your own situations to monitor the performance of your WebSphere Application Server servers and their applications. These situations can monitor your WebSphere Application Server resources or correlate multiple conditions to alert you to problems that might have occurred when attribute values exceed defined thresholds.

Attribute groups used by the predefined workspaces

A workspace contains graphical data or report columns that correspond directly to particular attributes in an attribute group. The following table shows the correlations between the predefined workspaces and the attribute groups. The primary and secondary workspaces, are listed alphabetically, not in the order in which they appear in the Navigator.

Workspaces and the attribute groups they reference

Workspace Related Attribute Groups
Application Health Summary Application Health Status
Application Registry Application Monitoring Configuration
Allocation Failures Allocation Failure
Cache Analysis Dynamic Cache
Dynamic Cache Templates
Client Communications Client Communications
Container Object Pools Container Object Pools
Container Transactions Container Transactions
Datasources
Selected Datasource - History Datasources
DB Connection Pools
Selected DB Connection Pool - History DB Connection Pools
DCS Stacks DCS Stack Counter
Destinations Topic Spaces
Queue
Durable Subscriptions Durable Subscriptions
EJB Containers EJB Containers
Enterprise Java Beans Enterprise Java Beans
Garbage Collections - Selected Allocation Failure Garbage Collection Cycle
Garbage Collector Analysis Garbage Collection Analysis
High Availability Manager High Availability Manager
IMAP/POP Workplace Mail IMAP/POP
J2C Connection Pools J2C Connection Pools
JMS Summary JMS Summary
Log Analysis Log Analysis
Lotus application server
Request Times and Rates
Garbage Collection Analysis
Messages Queues Workplace Mail Queues
Messaging Engine Communications Messaging Engine Communications
Platform Messaging Messaging Engines
Pool Analysis Thread Pools
DB Connection Pools
J2C Connection Pools
application server
Portal Pages Summary
Selected Portal Page - History Portal Page Summary
Portal Summary Portal Summary
Portlet Summary
Selected Portlet - History Portlet Summary
Request Analysis
Selected Request - History Request Analysis
Selected Request - Baseline Baseline
Selected Request - Service Components workspace Selected Request
Scheduler Scheduler
Selected Application - Application Tier Analysis
Selected Application - Backend Tier Analysis
Selected Application - Health History
Selected Application - Client Tier Analysis Application Health Status
Selected Application - Configuration Application Monitoring Configuration
Selected Request - Datasources Selected Request
Selected Request - JMS Queues Selected Request
Selected Request - Resource Adapters Selected Request
Servlets/JSPs - Selected Web Application Servlets JSPs
Sessions Servlet Sessions
Thread Pools Thread Pools
Web Applications Web Applications
Web Services
Selected Web Services - History Web Services Counters
Web Services Gateway Counters
WebSphere Agent WebSphere Agent Events
application server Status
Remote Configuration Requests attributes
WebSphere App Server application server
Request Times and Rates
Garbage Collection Analysis
WebSphere ESB Server application server
Request Times and Rates
Garbage Collection Analysis
WebSphere Portal Server application server
Request Times and Rates
Garbage Collection Analysis
WebSphere Process Server application server
Request Times and Rates
Garbage Collection Analysis
WMQ Client Link Communications WMQ Client Link Communications
WMQ Link Communications WMQ Link Communications
Workload Management Workload Management Client
Workload Management Server
Workplace Mail Workplace Mail Service

Alarm Manager attributes

The Alarm Manager attributes provide information for the alarm management. Use these attributes to manage alarms fired by the application for each work manager.
The attributes within this group are used to build the Alarm Manager workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and then select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Alarms Canceled The number of alarms canceled by the application. The valid format is a positive integer.

Alarms Created The total number of alarms created by all asynchronous scopes for the current Work Manager. The valid format is a positive integer.

Alarms Fired The number of alarms fired. The valid format is a decimal (formatted to three decimal places).

Alarms Latency Duration The latency of alarms fired in milliseconds. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Alarms Pending Size The number of alarms waiting to fire. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Alarms Rate The number of alarms firing per second. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Instrumentation Level For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Row Number The row number. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Whether this row is a summary row of statistical totals for all rows. Valid values are No and Yes.

Work Manager Name The name of the work manager. The value format is an alphanumeric string, with a maximum of 256 characters.

Allocation Failure attributes

The Allocation Failure attribute group provides information about the heap-allocation failure that caused the Java. Virtual Machine hosting the application server to start its garbage-collection routine.
You can use the Allocation Failure attributes in situations to determine the events that caused the JVM to start garbage collection. The attributes within this group are used to build the Allocation Failures workspace.

Allocation Failure Number The identifier assigned to the current allocation-failure block, which is associated with a bar in the Heap Usage - History bar chart. The valid format is a positive integer.

ASID The identifier (decimal) assigned to the address space running this servant region.

Bytes Needed The number of bytes needed on the heap when this allocation failure occurred. The valid format is a positive integer.

GC Cycle Count The number of garbage-collection cycles caused by this allocation failure. The valid format is a positive integer.

Heap Expanded The total number of kilobytes by which the heap expanded or contracted as a result of garbage collection. The valid format is a positive integer.

Heap Free (%) after GC The percentage of heap space that is available after garbage collection. The valid format is a positive integer.

Heap Status Whether the out-of-heap-space alert has been raised. Valid values are Normal and Out_of_heap_space.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Kbytes Free at Start of GC The number of kilobytes available in the heap before garbage collection began in response to this allocation failure. The valid format is a positive integer.

Kbytes Freed by GC The number of kilobytes freed by the garbage collector for this allocation failure. The valid format is a positive integer.

Kbytes Used The number of kilobytes in the heap that were in use when this allocation failure occurred. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Objects Moved The number of objects the garbage collector moved during compaction. The valid format is a positive integer.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Process ID The unique identifier of the JVM process (the class ID of the JVM). The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Time since Last Failure (ms) The time (in milliseconds) since the previous allocation failure. The valid format is a positive integer.

Time to Complete (ms) The time (in milliseconds) required to complete the action that resulted from this allocation failure. The valid format is a positive integer.

Total Kbytes Freed by GC The total number of kilobytes freed by the garbage collector in response to this allocation failure. The valid format is a positive integer.

Application Health Status attributes

The Application Health Status attributes provide information for real-time and historical application health status.
The attributes within this group are used to build the Application Health Summary workspace.

Application Health The combined application health level. Valid values are Unknown, Good, Fair, and Bad.

Application ID The unique identifier that is assigned automatically when the application is first configured and is preserved during the whole application life cycle. The valid format is a positive integer or -1 which means that Application ID is an aggregated statistic for all applications.

Application Name The name of the application to which the request belongs. The valid format is an alphanumeric string, with a maximum of 256 characters.

Application Status The status of the monitored application. Valid values are Standby, Discovered, Unknown, Starting, Running, Stopping, Stopped, and Failed.

Application Tier Health The health level of the application tier. Valid values are Unknown, Good, Fair, and Bad. Application tier health indicator is determined from EJB or custom request delays collected on the interval and compared against thresholds configured for application requests.

ASID The identifier (decimal) assigned to the address space running this servant region.

Backend Tier Health The health level of the backend tier. Backend tier health indicator is determined from JDBC, JCA, JNDI, JMS delays collected on the interval and compared against thresholds configured for application requests. Valid values are Unknown, Good, Fair, and Bad.

Client Tier Health The health level of the client tier. Valid values are Unknown, Good, Fair, and Bad. Client tier health indicator is determined from servlet/JSP or portal delays collected on the interval and compared against thresholds configured for application requests.

Completion Level The completion level of the requests during the interval. Valid values are Unknown, Good, Fair, and Bad. This attribute is determined from request data as the percentage of number of failed requests to the total number of application requests on the interval.

Custom Requests The availability indicator of the custom requests. Valid values are Unknown, Good, Fair, and Bad.

EJB Container The health level of the EJB container. Valid values are Unknown, Good, Fair, and Bad. This attribute is determined from EJB delay types collected during the interval and compared against application thresholds.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

JCA The overall health status of J2EE Connector Architecture (JCA) resources used by applications. Valid values are Unknown, Good, Fair, and Bad. This attribute is determined from JCA delay types collected during the interval and compared against application thresholds.

JDBC The overall health status of Java DataBase Connectivity (JDBC) resources used by applications. Valid values are Unknown, Good, Fair, and Bad. This attribute is determined from JDBC delay types collected during the interval and compared against application thresholds.

JNDI The overall health status of JNDI resources used by applications. Valid values are Unknown, Good, Fair, and Bad. This attribute is determined from JNDI delay types collected during the interval and compared against application thresholds.

JMS The overall health status of Java Message Service (JMS) resources used by applications. Valid values are Unknown, Good, Fair, and Bad. This attribute is determined from JMS delay types collected during the interval and compared against application thresholds.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Portal Container The health level of the portal container. Valid values are Unknown, Good, Fair, and Bad. This attribute is determined from portal delay types collected during the interval and compared against application thresholds.

Response Level The health level of the response time for the requests. Valid values are Unknown, Good, Fair, and Bad. This attribute is determined from application requests response times collected during the interval and compared against application thresholds.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Indicates that this row is a summary row of statistical totals for all rows.

Web Container The health level of the web container. Valid values are Unknown, Good, Fair, and Bad.

SCA The health level of application SCA access. Valid values are Unknown, Good, Fair, and Bad.

WAS Node Name The name of the WebSphere Application Server node group to which the application server belongs. The valid format is an alphanumeric string, with a maximum of 64 characters.

WAS Cell Name The name of the WebSphere Application Server cell to which the application server belongs. The valid format is an alphanumeric string, with a maximum of 64 characters.

Process ID The process ID for the application server. The valid format is a 4-byte integer.

Application Monitoring Configuration attributes

The Application Monitoring Configuration attributes provide information for the Application Monitoring Configuration.
Use these attributes to monitor different WebSphere applications running within an application server. The attributes within this group are used to build the Selected Application - Configuration workspace.

Application Alias The alias name that you can optionally assign for the application. In practice, this attribute enables you to combine multiple applications under the same common alias and report their request in the monitoring portal as it would come from same application. This attribute is blank by default. You can assign the value to it from Take Actions at any time in the application monitoring life cycle. The valid format is an alphanumeric string, with a maximum of 256 characters.

App ID The unique identifier that is assigned automatically when the application is first configured and is preserved during the whole application life cycle. The valid format is a positive integer.

Application Name The name of the application to which the request belongs. You can define the pattern of this name in the Application Registry workspace. The valid format is an alphanumeric string, with a maximum of 256 characters.

Bad Completion Rate (%) The bad completion rate threshold for the requests. The valid format is an alphanumeric string, with a maximum of 256 characters.

Baselining Elapsed Time The number of seconds during which the application baselining has been running. The valid format is a positive integer.

Baselining Status The status of the application baselining process. Valid values are Idle, Running, and Standby.

Baselining Scheduled Stop Time The date and time baselining is scheduled to finish. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Baselining Start Time The date and time when the application baselining was started. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Baselining Update Interval The number of seconds that defines how often active baselining data is incrementally updated to the monitoring agent. The valid format is a positive integer.

Fair Completion Rate (%) The fair completion rate threshold for the requests. The valid format is an alphanumeric string, with a maximum of 256 characters.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Monitor Status The current application monitoring status. Valid values are Discovered, Enabled, Disabled, and Standby.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Request Data Monitoring Level The custom request aggregation level for all application requests. Valid values are Default, Disabled, Level1, and Level2. This attribute is set to Default when the application is first discovered.

Request Data Sampling Rate The custom request aggregation rate for all application requests. The valid format is a positive integer.

Reflex Automation Mode When reflex automation mode is enabled, application monitoring level is automatically updated on WASAppHealth* situation event.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Application server status attributes

The application server Status attributes provide status information for all WebSphere Application Server servers (and the WebSphere administrative server) being monitored by the agent.
The attributes within this group are used to build the WebSphere Agent workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and then select it again later. Each time you select the workspace, these attributes are updated with the latest data.

Origin Node The server name subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.
Cluster Name The name of the server group (cluster) that this application server belongs to. The valid format is an alphanumeric string, with a maximum of 128 characters.
Cluster Type Indicates the type of the server group (cluster) the application server belongs to.
Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 128 characters.
Process ID The process identifier of the Java virtual machine. The valid format is a positive integer.
Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.
Server Mode The mode of the WebSphere Application Server.
Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.
Server Origin Node Name Indicates the origin node name of the server subnode.The valid format is an alphanumeric string, with a maximum of 128 characters.
Server Subnode Name The name of the server node in the navigation tree. The valid format is an alphanumeric string, with a maximum of 32 characters.
Server Type The type of server process. The valid values are:

Types of server processes

Server Type Definition
Unknown The server type cannot be determined
AppServer A process that executes applications
AdminServer The administrative server you use when configuring WebSphere Application Server environments
NodeAgent The WebSphere Application Server node agent
JMSServer The WebSphere Application Server JMS server
DeploymentMgr The WebSphere Application Server deployment (cell) manager
ManagedProcess A stand-alone WebSphere Application Server process
UnManagedProcess A WebSphere Application Server process that is managed by a WebSphere Application Server deployment manager through a node agent

Start Date and Time The date and time when the WebSphere Application Server started. The valid format is a timestamp. This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.
Status The status of the WebSphere Application Server. Valid values are Connected and Disconnected.
WAS Cell Name The name of the WebSphere Application Server cell to which this application server belongs. The valid format is an alphanumeric string, with a maximum of 64 characters.
WAS Configuration Repository Directory Name The name of the WebSphere Application Server configuration repository directory, which normally resides in the config subdirectory of the product installation root directory. The valid format is an alphanumeric string, with a maximum of 128 characters.
WAS Node Name The name of the WebSphere Application Server node group to which this application server belongs. The valid format is an alphanumeric string, with a maximum of 64 characters.
VE Host/port The valid format is an alphanumeric string, with a maximum of 256 characters.
Probe ID The valid format is an alphanumeric string, with a maximum of 128 characters.

Application server attributes

The application server attributes provide the status and summary data for a specific WebSphere Application Server instance.
The attributes provide performance data for the WebSphere Application Server runtime (JVM memory), thread pools, HTTP sessions, and configuration parameters. They also provide some information from other attribute groups to give an overall view of the WebSphere Application Server. Use the application server attributes in situations to monitor the health and performance of a WebSphere Application Server.
The attributes within this group are used to build the WebSphere application server and the Pool Analysis Workspace workspaces.

The attributes in this attribute group contain zeros for performance data if your site sets the configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and you have not yet run applications that generate performance data. To report performance data in these attributes when you have installed and configured the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; this means the attributes in this attribute group initially contain zeros until you select the workspace and then select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

ASID The identifier (decimal) assigned to the address space running this servant region.

CPU Used (ms) Indicates the number of milliseconds the JVM CPU used during the interval. The valid format is a positive integer.

CPU Used (%) Indicates the percentage of the JVM CPU used during the interval. For UNIX users, this attribute has a meaningful value only if the monitoring agent is running with superuser authority. The valid format is a decimal (formatted to one decimal place).

Platform CPU Used (ms) Indicates the number of milliseconds the host platform (OS) CPU used during the interval.

Garbage Collection Monitoring The monitoring level for garbage-collection data. Valid values are Disabled and Enabled.

Instrumentation Level The JVM instrumentation level. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Hung Threads Total Total number of detected hung threads. The valid format is a positive integer.

Hung Threads Blocked Number of hung threads detected in the BLOCKED state. The valid format is a positive integer.

Hung Threads Waiting Number of hung threads detected in the WAITING state. The valid format is a positive integer.

Hung Threads Timed Waiting Number of hung threads detected in the TIMED_WAITING state. The valid format is a positive integer.

JVM Memory Free (Kbytes) The JVM free memory size in Kbytes.

JVM Memory Total (Kbytes) The JVM total memory size in Kbytes.

JVM Memory Used (Kbytes) The JVM used memory size in Kbytes.

JVM Memory Free (bytes) The JVM free memory size (in bytes). The valid format is a positive integer.

JVM Memory Total (bytes) The JVM total memory size (in bytes). The valid format is a positive integer.

JVM Memory Used (bytes) The JVM used memory size (in bytes). The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Process ID The process identifier of the Java virtual machine. The valid format is a positive integer.

Probe ID The valid format is an alphanumeric string, with a maximum of 128 characters.

Request Data Monitoring Level The monitoring level for request data stored by the data collector. Valid values are Disabled, Level1 edge request data, such as servlets and JSPs are displayed), and Level2 (nested request data such as JDBC and JMS requests are also displayed).

Request Data Sampling Rate (%) The percentage of Level1 requests (that is, edge requests) being sampled. The valid format is a positive integer.

Resource Data Monitoring The monitoring level for resource (that is, PMI) data stored by the data collector. Valid values are Disabled and Enabled.

Sample Date and Time The date and time the Tivoli Enterprise Monitoring Agent collected the data. The valid format is a 12 character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12 character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Instance Name The name of the WebSphere Application Server. This is a logical grouping of one or more server instances (called a "generic server" or "cluster") any one of which can run an application. The valid format is an alphanumeric string, with a maximum of eight characters.

Server Mode Indicates the mode of the WebSphere Application Server.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Server Type The type of the WebSphere Application Server. Valid values are Unknown, AppServer, AdminServer, NodeAgent, JMSServer, DeploymentManager, ManagedProcess, and UnManagedProcess.

Server Subnode Name Indicates the sub node name of the application server.

Start Date and Time The date and time when the WebSphere Application Server started. The valid format is a timestamp. This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Status The status of the WebSphere Application Server. Valid values are Connected and Disconnected.

Summary Indicates that this row is a summary row of statistical totals for all rows.

System Paging Rate (Kbytes/sec) The system paging rate in kilobytes per second during the interval. The valid format is a positive integer.

WAS Node Name The name of the WebSphere Application Server node group to which the application server belongs. The valid format is an alphanumeric string, with a maximum of 64 characters.

WAS Cell Name The name of the WebSphere Application Server cell to which the application server belongs. The valid format is an alphanumeric string, with a maximum of 64 characters.

Version The version of WebSphere Application Server. The valid format is an alphanumeric string, with a maximum of eight characters.

VE Host/port The valid format is an alphanumeric string, with a maximum of 256 characters.

Baseline attributes

The Baseline attributes provide information for baseline extract data for the given application.
The baselining collects statistical information about an application requests completion times and uses this information to assign fair and bad thresholds on the application requests. The product divides the whole request response times into buckets and collects individual hits into each bucket. Use these attributes to get statistics from individual requests collected during baselining interval.
The attributes within this group are used to build the Selected Request - Baseline workspace.

Application ID The unique identifier that is assigned automatically when the application is first configured and is preserved during the whole application life cycle. The valid format is a positive integer.

Bad Hits Percentage The percentage of bucket hits in the metric bad value zone. The valid format is a positive integer.

Bucket Number The bucket number of the baselining data. The valid format is a positive integer.

EJB Container Percent The average percent of time that bucket requests were executed inside EJB container. The valid format is a positive integer.

Fair Hits Percentage The percentage of bucket hits in the metric fair value zone. The valid format is a positive integer.

Good Hits Percentage The percentage of bucket hits in the metric good value zone. The valid format is a positive integer.

Hits Percentage The percentage of hits for the bucket during the baselining. The valid format is a positive integer.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

JCA Percent The average percent of time that bucket requests spent for JCA access. The valid format is a positive integer.

JDBC Percent The average percent of time that bucket requests spent for JDBC access. The valid format is a positive integer.

JMS Percent The average percent of time that bucket requests spent for JMS access. The valid format is a positive integer.

JNDI Percent The average percent of time that bucket requests spent for JNDI access. The valid format is a positive integer.

Lower Boundary (msec) The lower boundary of bucket response times in milliseconds. The valid format is a positive integer.

Metric ID The metric identifier of the baselining data. The valid format is a positive integer.

Metric Type The metric type of the baselining data. Valid formats are Request, Error, and Resource.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Portal Percent The average percent of time that bucket requests were executed inside portal container. The valid format is a positive integer.

Response Time Mean (msec) The mean time of bucket response times. The valid format is a positive integer.

SCA Percent The average percent of time that bucket requests spent for SCA access. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Hits Percentage The percentage of bucket hits in the metric selection value zone. The valid format is a positive integer.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Servlet Container Percent The average percent of time that bucket requests were executed inside the servlet container. The valid format is a positive integer.

Total Hits The total hits number for the bucket during the baselining. The valid format is a positive integer.

Upper Boundary (msec) The upper boundary of bucket response times. The valid format is a positive integer.

Client Communications attributes

The Client Communications attributes display overall statistics about server-side monitoring and a client-side API to retrieve performance data.
The attributes within this group are used to build the Client Communications workspace.
Restriction: Attributes in this group are only provided for IBM WebSphere application server version 6.0 or later.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

API Connections The number of API sessions being used by clients that are currently network connected to this application server. Some of these API connections might be being used by internal system processes on behalf of a client. The valid format is a positive integer.

Buffered Read (bytes) The number of bytes of data that have been received from the network and are held pending further processing. Large values might indicate that the application server is unable to process data fast enough to keep up with the clients attached. The valid format is a positive integer.

Buffered Write (bytes) The number of bytes of data being held pending transmission. Large values might indicate network congestion or clients which are unable to process data fast enough to keep up with the application server. The valid format is a positive integer.

Clients Attached The number of distinct client processes currently network connected to this application server. The valid format is a positive integer.

Errors The communication errors that have occurred and resulted in a network connection to a client being disconnected. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the client communications. For WebSphere 5, the valid values are None, Low, Medium, High, and Maximum; for WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Message Read (bytes) The number of bytes of message data received from client processes over network connections. This does not include data used to negotiate the transmission of messages. The valid format is a positive integer.

Messages Received at JMS 0 Priority (bytes) The number of messages received at JMS priority 0. The valid format is a positive integer.

Messages Received at JMS 1 Priority (bytes) The number of messages received at JMS priority 1. The valid format is a positive integer.

Messages Received at JMS 2 Priority (bytes) The number of messages received at JMS priority 2. The valid format is a positive integer.

Messages Received at JMS 3 Priority (bytes) The number of messages received at JMS priority 3. The valid format is a positive integer.

Messages Received at JMS 4 Priority (bytes) The number of messages received at JMS priority 4. The valid format is a positive integer.

Messages Received at JMS 5 Priority (bytes) The number of messages received at JMS priority 5. The valid format is a positive integer.

Messages Received at JMS 6 Priority (bytes) The number of messages received at JMS priority 6. The valid format is a positive integer.

Messages Received at JMS 7 Priority (bytes) The number of messages received at JMS priority 7. The valid format is a positive integer.

Messages Received at JMS 8 Priority (bytes) The number of messages received at JMS priority 8. The valid format is a positive integer.

Messages Received at JMS 9 Priority (bytes) The number of messages received at JMS priority 9. The valid format is a positive integer.

Messages Sent at JMS 0 Priority (bytes) The number of messages transmitted at JMS priority 0. The valid format is a positive integer.

Messages Sent at JMS 1 Priority (bytes) The number of messages transmitted at JMS priority 1. The valid format is a positive integer.

Messages Sent at JMS 2 Priority (bytes) The number of messages transmitted at JMS priority 2. The valid format is a positive integer.

Messages Sent at JMS 3 Priority (bytes) The number of messages transmitted at JMS priority 3. The valid format is a positive integer.

Messages Sent at JMS 4 Priority (bytes) The number of messages transmitted at JMS priority 4. The valid format is a positive integer.

Messages Sent at JMS 5 Priority (bytes) The number of messages transmitted at JMS priority 5. The valid format is a positive integer.

Messages Sent at JMS 6 Priority (bytes) The number of messages transmitted at JMS priority 6. The valid format is a positive integer.

Messages Sent at JMS 7 Priority (bytes) The number of messages transmitted at JMS priority 7. The valid format is a positive integer.

Messages Sent at JMS 8 Priority (bytes) The number of messages transmitted at JMS priority 8. The valid format is a positive integer.

Messages Sent at JMS 9 Priority (bytes) The number of messages transmitted at JMS priority 9. The valid format is a positive integer.

Message Written (bytes) The number of bytes of message data sent to client processes over network connections. This does not include data used to negotiate the transmission of messages. The valid format is a positive integer.

Messaging Engine Name The name of the message engine. The value format is an alphanumeric string, with a maximum of 256 characters.

Multicast Send Messages The number of messages transmitted using multicast protocols. The valid format is a positive integer.

Multicast Write The number of bytes transmitted using multicast protocols. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Reads The number of read operations used to receive data from client processes through network connections. The valid format is a positive integer.

Reads Blocked The number of read operations that could not be completed immediately. This number can be used as an indicator of network congestion when communicating with client processes. The valid format is a positive integer.

Received at High Priority (bytes) The number of bytes of data received at a high priority. Message data cannot be transmitted with this priority, so typically these bytes of data comprise control transmissions used to negotiate the flow of messages. The valid format is a positive integer.

Received at Highest Priority (bytes) The number of bytes of data received at the highest possible priority. Message data cannot be transmitted with this priority, so typically these bytes of data comprise control transmissions used to negotiate the flow of messages. The valid format is a positive integer.

Received at JMS 0 Priority (bytes) The number of bytes of data received at the priority used by JMS priority 0 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Received at JMS 1 Priority (bytes) The number of bytes of data received at the priority used by JMS priority 1 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Received at JMS 2 Priority (bytes) The number of bytes of data received at the priority used by JMS priority 2 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Received at JMS 3 Priority (bytes) The number of bytes of data received at the priority used by JMS priority 3 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Received at JMS 4 Priority (bytes) The number of bytes of data received at the priority used by JMS priority 4 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Received at JMS 5 Priority (bytes) The number of bytes of data received at the priority used by JMS priority 5 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Received at JMS 6 Priority (bytes) The number of bytes of data received at the priority used by JMS priority 6 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Received at JMS 7 Priority (bytes) The number of bytes of data received at the priority used by JMS priority 7 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Received at JMS 8 Priority (bytes) The number of bytes of data received at the priority used by JMS priority 8 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Received at JMS 9 Priority (bytes) The number of bytes of data received at the priority used by JMS priority 9 messages. Typically this is an accurate measure of the number of bytes of message data received at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Received at Low Priority (bytes) The number of bytes of data received at a low priority. Message data cannot be transmitted with this priority, so typically these bytes of data comprise control transmissions used to negotiate the flow of messages. The valid format is a positive integer.

Received at Lowest Priority (bytes) The number of bytes of data received at the lowest possible priority. Message data cannot be transmitted with this priority, so typically these bytes of data comprise control transmissions used to negotiate the flow of messages. The valid format is a positive integer.

Received at Very High Priority (bytes) The number of bytes of data received at a high priority. Message data cannot be transmitted with this priority, so typically these bytes of data comprise control transmissions used to negotiate the flow of messages. The valid format is a positive integer.

Received at Very Low Priority (bytes) The number of bytes of data received at a low priority. Message data cannot be transmitted with this priority, so typically these bytes of data comprise control transmissions used to negotiate the flow of messages. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Sent at High Priority (bytes) The number of bytes of data transmitted at a high priority. Message data cannot be transmitted with this priority, so typically these bytes of data comprise control transmissions used to negotiate the flow of messages. The valid format is a positive integer.

Sent at Highest Priority (bytes) The number of bytes of data transmitted at the highest possible priority for transmission. Message data cannot be transmitted with this priority, so typically these bytes of data comprise control transmissions used to negotiate the flow of messages. The valid format is a positive integer.

Sent at JMS 0 Priority (bytes) The number of bytes of data transmitted at the priority used by JMS priority 0 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Sent at JMS 1 Priority (bytes) The number of bytes of data transmitted at the priority used by JMS priority 1 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Sent at JMS 2 Priority (bytes) The number of bytes of data transmitted at the priority used by JMS priority 2 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Sent at JMS 3 Priority (bytes) The number of bytes of data transmitted at the priority used by JMS priority 3 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Sent at JMS 4 Priority (bytes) The number of bytes of data transmitted at the priority used by JMS priority 4 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Sent at JMS 5 Priority (bytes) The number of bytes of data transmitted at the priority used by JMS priority 5 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Sent at JMS 6 Priority (bytes) The number of bytes of data transmitted at the priority used by JMS priority 6 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Sent at JMS 7 Priority (bytes) The number of bytes of data transmitted at the priority used by JMS priority 7 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Sent at JMS 8 Priority (bytes) The number of bytes of data transmitted at the priority used by JMS priority 8 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Sent at JMS 9 Priority (bytes) The number of bytes of data transmitted at the priority used by JMS priority 9 messages. Typically this is an accurate measure of the number of bytes of message data transmitted at this priority level. However, from time to time, control transmissions used to negotiate the flow of messages might be transmitted at this priority level. The valid format is a positive integer.

Sent at Low Priority (bytes) The number of bytes of data transmitted at a low priority. Message data cannot be transmitted with this priority, so typically these bytes of data comprise control transmissions used to negotiate the flow of messages. The valid format is a positive integer.

Sent at Lowest Priority (bytes) The number of bytes of data transmitted at the lowest priority. Message data cannot be transmitted with this priority, so typically these bytes of data comprise control transmissions used to negotiate the flow of messages. The valid format is a positive integer.

Sent at Very High Priority (bytes) The number of bytes of data transmitted at a high priority. Message data cannot be transmitted with this priority, so typically these bytes of data comprise control transmissions used to negotiate the flow of messages. The valid format is a positive integer.

Sent at Very Low Priority (bytes) The number of bytes of data transmitted at a low priority. Message data cannot be transmitted with this priority, so typically these bytes of data comprise control transmissions used to negotiate the flow of messages. The valid format is a positive integer.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Whether this row is a summary row of statistical totals for all messaging engines. Valid values are No and Yes.

Total Read (bytes) The number of bytes of data received from client processes. This includes both message data and data used to negotiate the transmission of messages. The valid format is a positive integer.

Total Written (bytes) The number of bytes of data sent to client processes. This includes both message data and data used to negotiate the transmission of messages. The valid format is a positive integer.

Writes The number of write operations used to transmit data to client processes via network connections. The valid format is a positive integer.

Writes Blocked The number of write operations that could not be completed immediately. This number can be used as an indicator of network congestion when communicating with client processes. The valid format is a positive integer.

10. Container Object Pools attributes

Use the Container Object Pools attributes in situations to monitor the effectiveness of the object cache and of resource usage.
These attributes provide aggregated information for each defined EJB container that aggregates bean object pool performance for all Enterprise beans deployed to that container and aggregated information for the application server that aggregates bean object pool performance data for all Enterprise beans deployed to the application server. The attributes within this group are used to build the Container Object Pools workspace.

The attributes within this attribute group contain zeros for performance data if your site set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Average Objects Discarded The average number of objects discarded each time the bean object pool was emptied of idle objects during the interval. The valid format is a decimal (formatted to three decimal places).

Objects Discarded Count The number of objects joined in Average Objects Discarded. The valid format is a 4-byte integer. If the number is too big to be stored, the value -2 is used.

Average Objects in Pool The average number of objects in the bean object pool during the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Discard Count The number of times the object returned to the bean-object pool was discarded because the bean object pool was already full during the interval. The valid format is a positive integer.

Discard Rate (per sec) The bean object pool discard rate (per second) for the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Drain Count The number of times the bean object pool was found idle and an attempt was made to remove idle objects during the interval. The valid format is a positive integer.

Drain Rate (per sec) The number of times (per second) that the bean object pool was found idle during the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Find Count The number of times a retrieval call found an available object in the bean object pool during the interval. The valid format is a positive integer.

Find Rate (per sec) The availability of bean object pool retrievals (per second) for the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Get Count The number of calls retrieving an object from the bean object pool during the interval. The valid format is a positive integer.

Get Rate (per sec) The number of bean objects retrieved (per second) for the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Interval (sec) The length (in seconds) of the interval. The valid format is a positive integer.

Instrumentation Level The instrumentation level for this container. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Container Name The name of the container. The valid format is an alphanumeric string, with a maximum of 64 characters.

Return Count The number of calls returning an object to the bean object pool during the interval. The valid format is a positive integer.

Return Rate (per sec) The bean objects returned (per second) for the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Sample Date and Time The date and time the Tivoli Enterprise Monitoring Agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.

Summary of All Containers Whether this row is a summary row of statistical totals aggregated over all bean object pools in the application server. Valid values are No and Yes.

Container Transactions attributes

The Container Transactions attribute group provides performance information about transactions that run in each defined EJB container and an aggregated value for all transactions that run in the application server.
Use the Container Transactions attributes in situations to monitor transaction activity for each EJB container and for the application server. The attributes within this group are used to build the Container Transactions workspace.

The attributes within this attribute group contain zeros for performance data if your site set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Global Transaction before Completion Duration (ms) The average duration before completion for global transactions during the interval. The valid format is a decimal (formatted to three decimal places).

Global Transaction before Completion Duration Count The count of times that were averaged for Global Transaction before Completion Duration. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Global Transaction Commit Duration (ms) The time (in milliseconds) that the transaction required for its resolution phase during the interval. The valid format is a decimal (formatted to three decimal places).

Global Transaction Commit Duration Count The count of times that were averaged for Global Transaction Commit Duration. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Global Transaction Commit Rate (per sec) The number of times (per second) global transactions were committed during the interval. The valid format is a decimal (formatted to three decimal places).

Global Transaction Duration (ms) The average duration (in milliseconds) for global transactions during the interval. The valid format is a decimal (formatted to three decimal places).

Global Transaction Duration Count The count of times that were averaged for Global Transaction Duration. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Global Transaction Optimize Rate (per sec) The number of times (per second) that global transactions were converted to single phase since the previous sample. The valid format is a decimal (formatted to three decimal places).

Global Transaction Prepare Duration (ms) The average preparation duration (in milliseconds) for global transactions during the interval. The valid format is a decimal (formatted to three decimal places).

Global Transaction Prepare Duration Count The count of times that were averaged for Global Transaction Prepare Duration. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Global Transaction Rollback Rate (per sec) The number of times (per second) that global transactions were undone because they could not complete during the interval. The valid format is a decimal (formatted to three decimal places).

Global Transaction Timeout Rate (per sec) The number of global transaction timeouts (per second) since the previous sample. The valid format is a decimal (formatted to three decimal places).

Global Transaction Timeouts The number of global transactions that timed out during the interval. The valid format is a positive integer.

Global Transactions Active The number of concurrently active global transactions running in the container during the interval. Global transactions involve multiple resource managers. The valid format is a decimal (formatted to three decimal places).

Global Transactions Begin Rate (per sec) The number of times global transactions were started (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Global Transactions Begun The total number of global transactions that the server began during the interval. The valid format is a positive integer.

Global Transactions Committed The number of global transactions that were completed during the interval. The valid format is a positive integer.

Global Transactions Involve Rate (per sec) The number of times (per second) global transactions were involved during the interval. The valid format is a positive integer.

Global Transactions Involved The number of global transactions that were involved at the server during the interval, including transactions that were begun or imported. The valid format is a positive integer.

Global Transactions Rolled Back The total number of global transactions that were undone because they could not complete during the interval. The valid format is a positive integer.

Global Transactions Optimized The number of global transactions converted to single phase for optimization since the previous sample. The valid format is a positive integer.

Instrumentation Level The instrumentation level for this container. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the interval. The valid format is a positive integer.

Local Transaction before Completion Duration (ms) The average duration before completion for local transactions during the interval. The valid format is a decimal (formatted to three decimal places).

Local Transaction before Completion Duration Count The count of times that were averaged for Local Transaction before Completion Duration. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Local Transaction Commit Duration (ms) The average duration for commit for local transactions during the interval. The valid format is a decimal (formatted to three decimal places).

Local Transaction Commit Duration Count The count of times that were averaged for Local Transaction Commit Duration. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Local Transaction Commit Rate (per sec) The number of local transactions (per second) committed during the interval. The valid format is a decimal (formatted to three decimal places).

Local Transaction Duration (ms) The average duration (in milliseconds) of local transactions during the interval. The valid format is a decimal (formatted to three decimal places).

Local Transaction Duration Count The count of times that were averaged for Local Transaction Duration. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Local Transaction Rollback Rate (per sec) The number of times (per second) that local transactions were undone because they could not be completed during the interval. The valid format is a decimal (formatted to three decimal places).

Local Transaction Timeout Rate (per sec) The number of local transactions that timed out per second during the interval. The valid format is a decimal (formatted to three decimal places).

Local Transaction Timeouts The number of local transactions that timed out during the interval. The valid format is a positive integer.

Local Transactions Active The number of concurrently active local transactions running in the container during the interval. Local transactions involve a single resource manager. The valid format is a decimal (formatted to three decimal places).

Local Transactions Begin Rate (per sec) The number of times (per second) local transactions were started during the interval. The valid format is a positive integer.

Local Transactions Begun The number of local transactions begun at the server since the previous sample. The valid format is a positive integer.

Local Transactions Committed The number of local transactions committed during the interval. The valid format is a positive integer.

Local Transactions Rolled Back The number of local transactions that were undone during the interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.
For more information, see:

Data sources attributes

The Data sources attributes provide database usage information.
These attributes provide traffic information such as, response times for database requests, the frequencies at which database connections are created and destroyed, and how often databases are accessed. The attributes within this group are used to build the Datasources workspace.
The attributes within this attribute group contain meaningful values only if your site has set the request data monitoring level to Level2 to collect data on data source requests.

Application ID The unique identifier that is assigned automatically when the application is first configured and is preserved during the whole application life cycle. The valid format is a positive integer or -1 which means that Application ID is aggregated statistic for all applications.

ASID The identifier (decimal) assigned to the address space running this servant region.

Average Processing Time (ms) The total average processing time (in milliseconds) that the data source is used by an application. The valid format is a decimal (formatted to three decimal places).

Processing Time Count The count of times that were averaged for Average Processing Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Average Query Processing Time (ms) The average time (in milliseconds) per request used by queries to the data source. The valid format is a decimal (formatted to three decimal places).

Average Update Processing Time (ms) The average time (in milliseconds) per request used by updates to the data source. The valid format is a decimal (formatted to three decimal places).

Connection Average Wait Time (ms) The average time (in milliseconds) that applications had to wait for a connection. The valid format is a decimal (formatted to three decimal places).

Connection Count The number of connections to the data source. The valid format is a positive integer.

Connection Max Wait Time (ms) The worst-case time (in milliseconds) that applications had to wait for a connection. The valid format is a positive integer.

Connection Rate (per sec) The number of connection requests (per second) created for the data source. The valid format is a decimal (formatted to three decimal places).

Connection Total Wait Time (ms) The total time (in milliseconds) that applications had to wait for a connection to the data source. The valid format is a positive integer.

Database Product The name of the database product. The valid format is an alphanumeric string, with a maximum of 128 characters.

Database Product Version The version of the database product. The valid format is an alphanumeric string, with a maximum of 128 characters.

Datasource Name The name of the data source. The valid format is an alphanumeric string, with a maximum of 256 characters.

Datasource Label A shortened version of Datasource Name, used to display the data source name in the chart view. The valid format is an alphanumeric string, with a maximum of 12 characters.

Interval (sec) The length (in seconds) of the interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Origin Node The name of the application server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Process ID The unique identifier of the process running the Java Virtual Machine (JVM). The valid format is a positive integer.

Query Count The number of queries performed against the data source. The valid format is a positive integer.

Query Rate (per sec) The number of queries (per second) being made to the data source. The valid format is a decimal (formatted to three decimal places).

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Sampling Rate (%) The percentage of edge requests-such as servlets and JSPs-that were sampled for data source requests during the interval. The valid format is a positive integer.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Indicates that this row is a summary row of statistical totals for all rows.

Total Query Processing Time (ms) The total time (in milliseconds) used to process queries made to the data source. The valid format is a positive integer.

Total Update Processing Time (ms) The total time (in milliseconds) used to update the data source. The valid format is a positive integer.

Total Wait Time (ms) The time (in milliseconds) that applications had to wait for connections to the data source. The valid format is a positive integer.

Update Count The number of updates performed against the data source. The valid format is a positive integer.

Update Rate (per sec) The number of updates (per second) made to the data source. The valid format is a decimal (formatted to three decimal places).

DB Connection Pools attributes

The DB Connection Pools attributes provide information about the database connection pool for each defined data source, and an aggregated value that aggregates over all data sources.
Examples of DB Connection Pools include; the number of threads waiting for a connection and the number of connections created and released. Use the DB Connection Pools attributes to analyze JDBC performance for WebSphere application server applications. The attributes within this group are used to build the DB Connection Pools and the Pool Analysis workspaces.

The attributes within this attribute group contain zeros for performance data if your site set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and then select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Application ID Indicates J2EE application ID.

Average Free Pool Size Indicates the average size of the pool based upon the number of free connections.

Average Pool Size The average size of the pool (based upon the number of connections) during the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Average Usage Time (ms) The average time (in milliseconds) a connection was in use; blank if no transactions are completed during the interval. The valid format is a decimal (formatted to three decimal places).

Usage Time Count The count of times that were averaged for Average Usage Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Average Wait Time (ms) The average time (in milliseconds) a client waited for a connection; blank if no transactions are completed during the interval. The valid format is a decimal (formatted to three decimal places).

Wait Time Count The count of times that were averaged for Average Wait Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Average Waiting Threads The average number of threads waiting for a connection during the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Connection Allocation Rate (per sec) The connections allocated (per second) for the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Connection Creation Rate (per sec) The connections created (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Connection Destruction Rate (per sec) The connections released (per second) during the interval. The valid format is a positive integer.

Connection Handle Indicates the number of Connection objects in use for a particular connection pool.

Connection Used The number of managed connection objects in use for a particular EIS product name. The valid format is a positive integer.

Connections Allocated The number of connections allocated during the interval. The valid format is a positive integer.

Connections Created The number of connections created during the interval. The valid format is a positive integer.

Connections Destroyed The number of connections released during the interval. The valid format is a positive integer.

Connections Granted The sum of connections allocated and connections created during the interval. The valid format is a positive integer.

Datasource Label The abbreviated name of the data source. The valid format is an alphanumeric string, with a maximum of 32 characters.

Datasource Name The name of the data source. The valid format is an alphanumeric string, with a maximum of 256 characters.

Instrumentation Level The instrumentation level for the database connection pool for the data source. For WebSphere 5, the valid values are None, Low, Medium, High, and Maximum; for WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the interval. The valid format is a positive integer.

JDBC Time (ms) Indicates the amount of time spent running in the JDBC driver which includes time spent in the JDBC driver, network, and database.

JDBC Time Count The count of times that were used for JDBC Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Maximum Pool Size The maximum number of connections that can be created in this connection pool. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Pool Size Indicates the size of the connection pool.

Percent of Time Pool at Max The average percentage of time the number of connections in the pool reached the maximum number during the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Percent Used The average percentage of the connection pool in use during the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Percent Used Bad The bad percent of pool usage by application. The valid format is a positive integer.

Percent Used Fair The fair percent of pool usage by application. The valid format is a positive integer.

Percent Used Good The good percent of pool usage by application. The valid format is a positive integer.

Prep Statement Cache Discard Rate (per sec) The cache discards (per second) of prepared statements during the interval. The valid format is a decimal (formatted to three decimal places).

Prep Statement Cache Discards The number of prepared statements discarded from the cache during the interval. The valid format is a positive integer.

Pool Size Indicates the size of the connection pool.

Return Count The number of connections that applications returned to the pool during the interval. The valid format is a positive integer.

Return Rate (per sec) The number of connections (per second) returned since the previous sample. The valid format is a decimal (formatted to three decimal places).

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.

Summary of All DB Connections Whether this row is a summary row of statistical totals collected for all the DB connection pools. Valid values are No and Yes.

Thread Timeout Rate (per sec) The number of threads (per second) that timed out during the interval. The valid format is a decimal (formatted to three decimal places).

Threads Timed Out The number of threads that timed out while waiting for a connection during the interval. The valid format is a positive integer.

Total Usage (ms) The total time (in milliseconds) the connection object used. The valid format is a decimal (formatted to three decimal places).

Total Wait (ms) The total time (in milliseconds) the connection object waited. The valid format is a decimal (formatted to three decimal places).

DC Messages attributes

The DC Messages attributes provide message information from WebSphere data collector.
The attributes within this group are used to build the Log Analysis workspace.

ASID The identifier (decimal) assigned to the address space running this servant region.

Component The name of the component that caused the error. The value format is an alphanumeric string, with a maximum of 32 characters.

Event Date and Time The date and time the event occurred. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

File Name The name of the file. The valid format is an alphanumeric string, with a maximum of 256 characters.

Message Description The description of the message. The valid format is an alphanumeric string, with a maximum of 256 characters.

Message ID The unique identifier of the message. The valid format is an alphanumeric string, with a maximum of eight characters.

Method Name The name of the method. The valid format is an alphanumeric string, with a maximum of 256 characters.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 128 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Process ID Indicates the process ID of the JVM.

Sequence Number The sequence number in the JMX notifications stream. The valid format is a positive integer.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Severity The severity of the message. Valid values are Info, Warning, Error, and Severe.

Thread ID The identifier of the thread where the event occurred. The valid format is an alphanumeric string, with a maximum of 16 characters.

DCS Stack attributes

The DCS Stack attributes reports information about the statistical data within the entire WebSphere application server domain, including multiple nodes and servers.
Examples of DCS Stack attributes include; the incoming and outgoing message size, the number of incoming and outgoing messages, congestion events, and message buffer reallocations. The attributes within this group are used to build the DCS Stacks workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Average Incoming Message Size The average size (in bytes) of the messages that were received by the DCS stack. The valid format is a positive integer.

Average Incoming Message Size Count The count of individual message sizes that were averaged for Average Incoming Message Size. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Average Outgoing Message Size The average size (in bytes) of the messages that were sent through the DCS stack. The valid format is a positive integer.

Average Outgoing Message Size Count The count of individual message sizes that were averaged for Average Outgoing Message Size. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Coalesce Time The amount of time it actually takes to coalesce a view. The valid format is a decimal (formatted to three decimal places).

Coalesce Time Count The count of times that were used for Coalesce Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

DCS Stack Name The name of the Topic Space. The value format is an alphanumeric string, with a maximum of 256 characters.

Group Size The size of the group the local member belongs to. The valid format is a positive integer.

High Severity Congestion Events The number of times that a high severity congestion event for outgoing messages was raised. The valid format is a positive integer.

Incoming Messages The number of messages received by the DCS stack. The valid format is a decimal (formatted to three decimal places).

Instrumentation Level The instrumentation level for the DCS stack. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Join View Change Time The time to do a merge view change. The DCS stack is blocked during this time. The valid format is a decimal (formatted to three decimal places).

Join View Change Time Count The count of times that were used for Join View Change Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Maximum Incoming Message Size The maximal size (in bytes) of the messages that were received by the DCS stack. The valid format is a positive integer.

Maximum Outgoing Message Size The maximal size (in bytes) of the messages that were sent through the DCS stack. The valid format is a positive integer.

Message Buffer Reallocations The number of message buffer reallocations due to inadequate buffer size. If this number is larger than 20 percent of the number of sent messages, contact IBM Support. The valid format is a positive integer.

Minimum Incoming Message Size The minimal size (in bytes) of the messages that were received by the DCS stack. The valid format is a positive integer.

Minimum Outgoing Message Size The minimal size (in bytes) of the messages that were sent through the DCS stack. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Outgoing Messages The number of messages sent through the DCS stack. The valid format is a positive integer.

Remove View Change Time The time to do a split view change. The DCS stack is blocked during this time. The valid format is a decimal (formatted to 3 decimal places).

Remove View Change Time Count The count of times that were used for Remove View Change Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Row Number The row number. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Sent Messages The number of messages sent through the DCS stack. The valid format is a positive integer.

Summary Whether this row is a summary row of statistical totals for all rows. Valid values are No and Yes.

Suspicions The number of times that the local member suspected other members. The valid format is a positive integer.

Synchronization Completion Time The amount of time needed to guarantee that all view members are synchronized. The valid format is a decimal (formatted to three decimal places).

Synchronization Completion Time Count The count of times that were used for Synchronization Completion Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Synchronization Timeouts The number of times that the synchronization procedure timed out. The valid format is a positive integer.

View Changes The number of times that this member underwent view changes. The valid format is a positive integer.

Durable Subscriptions attributes

The Durable Subscriptions attributes display overall statistics about the durable subscriptions of a selected topic.
A durable subscription can be used to preserve messages published on a topic while the subscriber is not active. The attributes within this group are used to build the Durable Subscriptions workspace.

The attributes in this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.
Attributes in this group are only provided for IBM WebSphere application server version 6.0 or later.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Aggregate Message Wait Time The time spent by messages in the bus at consumption. If this time is not what was expected, view the message using the admin console to decide what action needs to be taken. The valid format is a positive integer.

Aggregate Message Wait Time Count The count of times that were used for Aggregate Message Wait Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Assured Persistent Messages Consumed The number of Assured Persistent messages consumed, for the lifetime of this messaging engine. The valid format is a positive integer.

Available Message The number of messages waiting to be consumed. The valid format is a positive integer.

Best Effort Non-persistent Messages Consumed The number of best effort non-persistent messages consumed, for the lifetime of this messaging engine. The valid format is a positive integer.

Express Non-persistent Messages Consumed The number of express non-persistent messages consumed, for the lifetime of this messaging engine. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the Durable Subscriptions. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Local Oldest Message Age The longest time any message has spent on this subscription. If this time is not what was expected, view the message using the admin console to decide what action needs to be taken. The valid format is a positive integer.

Local Oldest Message Age Count The count of individual message ages that were used for Local Oldest Message Age. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Local Message Wait Time The time spent by messages on this durable subscription at consumption. If this time is not what was expected, view the message using the admin console to decide what action needs to be taken. The valid format is a positive integer.

Local Message Wait Time Count The count of times that were used for Local Message Wait Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Messaging Engine Name The name of the message engine. The value format is an alphanumeric string, with a maximum of 256 characters.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Reliable Non-persistent Messages Consumed The number of reliable non-persistent messages consumed, for the lifetime of this messaging engine. The valid format is a positive integer.

Reliable Persistent Messages Consumed The number of Reliable Persistent messages consumed, for the lifetime of this messaging engine. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Subscription Name The name of the subscriptions. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Whether this row is a summary row of statistical totals for all rows. Valid values are No and Yes.

Topic Space Name The name of the topic space. The valid format is an alphanumeric string, with a maximum of 256 characters.

Total Messages Consumed The total number of messages consumed from this durable subscription. The valid format is a positive integer.

Dynamic Cache attributes

The Dynamic Cache attribute group provides information about the dynamic cache.
WebSphere application server consolidates several caching activities, including servlets, web services, and WebSphere commands, into one service called the dynamic cache. These caching activities work together to improve application performance and share many configuration parameters, which are set in an application server dynamic cache service. The dynamic cache works within an application server Java. Virtual Machine (JVM), intercepting calls to cacheable objects, for example, through a servlet service method or an execute method of a command. It either stores the object output to, or serves the object content from, the dynamic cache.
The attributes within this group are used to build the Cache Analysis workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Cache Instance Name Indicates the cache instance name.

Cache Instance Type Indicates Cache instance type.

Current In-Memory Cache Size The number of cache entries currently in memory. The valid format is a positive integer.

In-Memory and Disk Timeout Rate (per sec) The rate (per second) of total in-memory and disk timeouts for the sampling interval. The valid format is a decimal (formatted to three decimal places).

In-Memory and Disk Timeouts The total number of in-memory and disk timeouts during the sampling interval. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the dynamic cache. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Maximum In-Memory Cache Size The maximum number of cache entries in memory. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.

Summary of Cache Indicates that this row is a summary row of statistical totals collected for all the cache object types.

PMI Enable The valid format is a 4-byte integer.

Dynamic Cache Templates attributes

The Dynamic Cache Templates attribute group provides information about the cache template data.
A cache template is an object type defined by a cache policy specified in the WebSphere application server cachespec.xml file. A cache policy specifies the cache rules indicating what is cached, the invalidation, timeout conditions, and other data. The attributes within this group are used to build the Cache Analysis workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Cache Instance Name The cache instance name.

Cache Instance Type The cache instance type.

Cache Miss Rate (per sec) The rate (per second) of requests for this cacheable object type that were not found in the cache during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Cache Misses The number of requests for this cacheable object type that were not found in the cache (in memory, on disk or on other cooperating caches). This would have caused the underlying servlet or command to be executed in order to obtain the results. The valid format is a positive integer.

Cache Object Type The name of the object type specified in the cache policy of the cache spec XML file. The valid format is an alphanumeric string, with a maximum of 256 characters.

Client Request Rate (per sec) The request rate (per second) for this cacheable object type made by clients directly accessing this application server. The valid format is a decimal (formatted to three decimal places).

Client Requests The number of requests for this cacheable object type made by clients directly accessing this application server. The valid format is a positive integer.

Cluster Request Rate (per sec) The request rate (per second) for this cacheable object type made by cooperating caches in this cluster. The valid format is a decimal (formatted to three decimal places).

Cluster Requests The number of requests for this cacheable object type made by cooperating caches in this cluster. The valid format is a positive integer.

Current Cache Size The current number of entries for this cacheable object type present in the dynamic cache. The valid format is a positive integer.

Disk Hit Rate (per sec) The rate (per second) of the requests for this cacheable object type served from disk during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Disk Hits The number of requests for this cacheable object type that were served from disk. This applies only when the disk offload is turned on for the dynamic cache. The valid format is a positive integer.

Explicit Disk Invalidations Rate (per sec) The rate at which the entries of this cacheable object type were removed from disk due to explicit invalidations issued by the clients. The valid format is a decimal (formatted to three decimal places).

Explicit Disk Invalidations The number of entries of this cacheable object type that were removed from disk due to explicit invalidations issued by the clients (directly accessing the application server and by remote JVMs in the cluster). The valid format is a positive integer.

Explicit Local Invalidation Rate (per sec) The rate at which the explicit invalidations were received for this cacheable object type from clients accessing the application server directly, either programmatically or by a cache policy. The valid format is a decimal (formatted to three decimal places).

Explicit Local Invalidations The number of explicit invalidations received for this cacheable object type from clients accessing the application server directly, either programmatically or by a cache policy. The valid format is a positive integer.

Explicit Memory Invalidation Rate (per sec) The rate at which the entries of this cacheable object type were removed from memory due to explicit invalidations issued by the clients. The valid format is a decimal (formatted to three decimal places).

Explicit Memory Invalidations The number of entries of this cacheable object type that were removed from memory due to explicit invalidations issued by the clients (directly accessing the application server and by remote JVMs in the cluster). The valid format is a positive integer.

Explicit Remote Invalidation Rate (per sec) The rate at which explicit invalidations were received for this cacheable object type from cooperating JVMs in the cluster. The valid format is a decimal (formatted to three decimal places).

Explicit Remote Invalidations The number of explicit invalidations received for this cacheable object type from cooperating JVMs in the cluster. The valid format is a positive integer.

Instrumentation Level The PMI instrumentation level set for collecting dynamic cache data. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Least Recently Used Invalidation Rate (per sec) The rate (per second) at which entries of this cacheable object type were evicted from memory by a least-recently used algorithm. The valid format is a decimal (formatted to three decimal places).

Least Recently Used Invalidations The number of entries of this cacheable object type that were evicted from memory by a least-recently-used algorithm. This happens when the in-memory cache becomes full and subsequent requests for new entries must be accommodated. The entries removed from memory are passivated to disk if disk overflow is enabled. If this number is high, consider increasing the in-memory cache size. The valid format is a positive integer.

Memory Hit Rate (per sec) The rate (per second) of the requests for this cacheable object type served from memory during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Memory Hits The number of requests for this cacheable object type served from memory. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Remote Cache Entries Received The number of entries received from cooperating dynamic caches in this cluster. The valid format is a positive integer.

Remote Cache Entry Receive Rate (per sec) The rate (per second) of entries received from cooperating dynamic caches in this cluster for the sampling interval. The valid format is a decimal (formatted to three decimal places).

Remote Hit Rate (per sec) The rate (per second) of the requests for this cacheable object type served from other JVMs in the cluster during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Remote Hits The requests for this cacheable object type served from other JVMs in the cluster. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.

Summary of Cache Templates Whether this row is a summary row of statistical totals collected for all the cache object types. The valid values are No and Yes.

Template Row Number The number of the row in the report that displays in the workspace, which is associated with a bar in the Ten Worst Hits Rate bar chart. The valid format is an integer.

Timeout Invalidation Rate (per sec) The rate (per second) at which entries are removed from the cache (memory or disk) because their timeout has expired. The valid format is a decimal (formatted to three decimal places).

Timeout Invalidations The number of entries of this cacheable object type that were removed from memory or disk because their timeout (as specified in the cache spec XML file) has expired. The valid format is a positive integer.

Total Explicit Invalidation Rate (per sec) The rate at which invalidations were issued for entries for this cacheable object type explicitly by the clients. The valid format is a decimal (formatted to three decimal places).

Total Explicit Invalidations The number of invalidations issued for entries of this cacheable object type explicitly by the clients (directly accessing the application server and by remote JVMs in this cluster). The valid format is a positive integer.

Total Hit Rate (per sec) The total hit rate per second. The valid format is a decimal (formatted to three decimal places).

EJB Containers attributes

The EJB Containers attributes provide aggregated information for each defined EJB container that aggregates bean performance data for all Enterprise beans deployed to that container.
The attributes also provide aggregated information for the application server that aggregates bean performance data for all Enterprise beans deployed to the application server. These attributes provide load values, response times, and lifecycle activities for Enterprise beans. Use the EJB Containers attributes in situations to monitor application server load and resource usage.
The attributes within this group are used to build the EJB Containers workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Activate Count The number of times a bean instance was activated during the interval. The valid format is a positive integer.

Activation Rate (per sec) The bean activations (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Active Method Count The average number of bean methods concurrently active during the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Average Concurrently Live Beans The average number of bean objects concurrently live during the sampling interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Average Concurrently Ready Beans The average number of beans concurrently active during the last interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Container Name The name of the container. The valid format is an alphanumeric string, with a maximum of 64 characters.

Create Average Time (ms) The average method response time for creates during the interval. The valid format is a decimal (formatted to three decimal places).

Create Time Count The count of times that were averaged for Create Average Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Create Count The number of bean create calls during the interval. The valid format is a positive integer.

Creation Rate (per sec) The bean create calls (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Destroy Count The number of times bean objects were destroyed by garbage collection during the interval. The valid format is a positive integer.

Destruction Rate (per sec) The rate at which the beans are destroyed by garbage collection (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Entity Bean Load Count The number of times an entity bean data was loaded during the interval. The valid format is a positive integer.

Entity Bean Load Rate (per sec) The number of entity beans (per second) that were loaded during the interval. The valid format is a decimal (formatted to three decimal places).

Entity Bean Store Count The number of times entity bean data was written to the database during the interval. The valid format is a positive integer.

Entity Bean Store Rate (per sec) The entity bean stores (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Instantiate Count The number of times bean objects were instantiated during the interval. The valid format is a positive integer.

Instantiation Rate (per sec) The number of times bean objects were instantiated (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Instrumentation Level The instrumentation level for this EJB container. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the interval. The valid format is a positive integer.

Method Average Response Time (ms) The average response time (in milliseconds) on remote interface methods for all beans during the interval. The valid format is a decimal (formatted to three decimal places).

Method Response Time Count The count of bean response times averaged for Method Average Response Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Method Invocation Count The number of method invocations during the interval. The valid format is a positive integer.

Method Invocation Rate (per sec) The rate of invocations (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Passivate Count The number of times a bean instance was passivated during the interval. The valid format is a positive integer.

Passivation Rate (per sec) The bean passivations (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Removal Rate (per sec) The bean remove calls (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Remove Average Time (ms) The average method response time for removes during the interval. The valid format is a decimal (formatted to three decimal places).

Remove Time Count The count of times that were averaged for Remove Average Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Remove Count The number of bean remove calls during the interval. The valid format is a positive integer.

Request Count The number of requests during the interval. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.

Summary of All Containers Whether this row is a summary row of statistical totals collected for all EJB containers. The valid values are No and Yes.

Total (ms) The total time used during the interval. The valid format is a decimal (formatted to three decimal places).

Total Create (ms) The total time (in milliseconds) of bean create calls during the interval. The valid format is a decimal (formatted to three decimal places).

Total Method Invocation (ms) The total time (in milliseconds) of method invocations during the interval. The valid format is a decimal (formatted to three decimal places).

Total Remove (ms) The total time (in milliseconds) of bean remove calls during the interval. The valid format is a decimal (formatted to three decimal places).

Enterprise Java Beans attributes

The Enterprise Java. Beans attributes provide performance information about each Enterprise Java Bean (EJB) deployed to the application server.
These attributes provide information about bean activity and bean object pool activity. Use the Enterprise Java Beans attributes in situations to monitor performance and problems for an individual bean. The attributes within this group are used to build the Enterprise Java Beans workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and reselect it later. Each time you reselect the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Activate Count The number of times a bean instance was activated during the interval. The valid format is a positive integer.

Activation Rate (per sec) The bean instance activations (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Active Method Count The average number of invocations being processed concurrently for all the methods during the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Application EJB Module Name The name of the Web Application or EJB Module. The valid format is an alphanumeric string, with a maximum of 64 characters.

Average Concurrently Live Beans The average number of live bean objects during the interval, which include objects that were instantiated but not yet destroyed. This is a load value providing data on the average level as a function of time. It is the average number of bean objects that exist in the run time, whether active or pooled. This is a measure of how many resources the home interface is consuming. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Average Concurrently Ready Beans The average number of active beans during the interval. This is a load value providing data on the average level as a function of time. It is the average number of bean instances of the home that are in the ready state. This is a measure of how busy the server is. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Average Objects Discarded The average number of objects that were discarded each time the bean object pool was emptied of idle objects during the interval. The valid format is a decimal (formatted to three decimal places).

Objects Discarded Count The count of objects used for Average Objects Discarded. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Average Objects in Pool The average number of objects in the bean object pool during the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Bean Name The name of the Enterprise JavaBean (EJB). This name prefixes the application name and the EJB compress name. The valid format is an alphanumeric string, with a maximum of 128 characters.

Bean Type The type of bean. Valid values are Stateless, Stateful, Entity, and Message Driven.

Create Average Time (ms) The average method response time to create bean objects during the interval. The valid format is a decimal (formatted to three decimal places).

Create Time Count The count of times that were averaged for Create Average Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Create Count The number of create calls during the interval. The valid format is a positive integer.

Creation Rate (per sec) The create calls (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Destroy Count The average number of times bean objects were destroyed by garbage collection during the interval. The valid format is a positive integer.

Destruction Rate The rate of destructions (per second) for bean objects by the garbage collector during the interval. The valid format is a decimal (formatted to three decimal places).

Discard Count The number of times the returned object to the bean object pool was discarded because the bean object pool was already full during the interval. The valid format is a positive integer.

Discard Rate (per sec) The bean object pool discards (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Drain Count The number of times the bean object pool was found idle and an attempt was made to remove idle objects during the interval. The valid format is a positive integer.

Drain Rate (per sec) The drain rate (per second) for the bean object pool during the interval. The valid format is a decimal (formatted to three decimal places).

Entity Bean Load Count The number of times bean data was loaded during the interval. The valid format is a positive integer.

Entity Bean Load Rate (per sec) The bean data loads (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Entity Bean Store Count The number of times bean data was written to the database during the interval. The valid format is a positive integer.

Entity Bean Store Rate (per sec) The rate at which data was written (per second) to the database for the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Find Count The number of times a retrieval call found an object available in the bean object pool during the interval. The valid format is a positive integer.

Find Rate (per sec) The bean object pool retrieve availability (per second) for the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Get Count The number of calls that retrieved an object from the bean object pool during the interval. The valid format is a positive integer.

Get Rate (per sec) The number of times bean objects were retrieved (per second) during the interval. The valid format is a decimal (formatted to three decimal places).

Instantiate Count The number of times bean objects were created during the interval. The valid format is a positive integer.

Instantiation Rate (per sec) The bean objects created (per second) for the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Instrumentation Level The instrumentation level of this enterprise bean. The valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Bean Object Pool Instrumentation Level The instrumentation level of the object pool for this enterprise bean. The valid values are None, Low, Medium, High, Basic, Extended, All, Custom, Maximum.

Interval (sec) The length (in seconds) of the interval. The valid format is a positive integer.

Method Average Response Time (ms) The average response time (in milliseconds) for all methods of the remote interface for this bean during the interval. The valid format is a decimal (formatted to three decimal places).

Method Response Time Count The count of times that were averaged for Method Average Response Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Method Invocation Rate (per sec) The invocations (per second) for all methods during the sampling interval. The Method Invocation Rate (per sec) is a load value that provides data on the average level as a function of time. This is a measure of how busy the server is. The valid format is a decimal (formatted to three decimal places).

Method Invocations The total number of remote interface method invocations during the interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Passivate Count The average number of bean objects passivated during the sampling interval. Minimum instrumentation level required to collect these data: Extended. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Passivation Rate (per sec) The number of passivations (per second) during the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Removal Rate (per sec) The remove calls (per second) for the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Remove Average Time (ms) The average method response time to remove bean objects during the interval. The valid format is a decimal (formatted to three decimal places).

Remove Time Count The count of times that were averaged for Remove Average Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Remove Count The number of remove calls during the interval. The valid format is a positive integer.

Return Count The number of calls that returned an object to the bean object pool during the interval. The valid format is a positive integer.

Return Rate (per sec) The bean object pool returns (per second) for the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.

Garbage Collection Analysis attributes

The Garbage Collection Analysis attribute group provides information about the garbage collector in the Java Virtual Machine that is hosting the application server.
The garbage collection attributes report the number of times the collector ran during the interval and the resulting number of objects that the collector freed. Use the Garbage Collection Analysis attributes in situations to monitor garbage-collection performance and possible problems. The attributes within this group are used to build the Garbage Collection Analysis and the WebSphere application server workspaces.

ASID The identifier (decimal) assigned to the address space running this servant region.

GC Rate (per min) The rate (per minute) at which the Java Virtual Machine is invoking its garbage-collection routine. The valid format is a decimal (formatted to three decimal places).

Heap Used (%) The percentage of heap used at the end of the interval. The valid format is a decimal (formatted to one decimal place).

Max Heap KBytes The maximum heap size for the JVM (the -Xmx parameter, if specified) The valid format is a 4-byte integer.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Kbytes Free The total number of free kilobytes in the heap at the end of the last garbage-collection cycle during the interval. The valid format is a positive integer.

Kbytes Total Freed by GC The total number of kilobytes freed by the garbage collector during the interval. The valid format is a positive integer.

Kbytes Used The number of kilobytes in the heap that were in use at the end of the last garbage collection cycle during the interval. The valid format is a positive integer.

Kbytes Used Delta The difference between the Kbytes Used value for this interval and the Kbytes Used value for the prior interval. The valid format is a positive or negative integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 256 characters.

Objects Freed The number of objects the garbage collector freed during the interval (only supported for IBM JDK). The valid format is a positive integer. Not monitored on non-IBM Java Virtual Machines, including objects commonly used on HP-UX and Solaris platforms.

Objects Moved The number of objects the garbage collector moved during the interval (only supported for IBM JDK). The valid format is a positive integer. Not monitored on non-IBM Java Virtual Machines, including objects commonly used on HP-UX and Solaris platforms.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Process ID The unique identifier of the JVM process (the class ID of the JVM). The valid format is a positive integer.

Real Time (ms) The total real time (in milliseconds) the garbage collector required during the most recent cycle. The valid format is a positive integer.

Real Time (%) The percentage of real time that the garbage collector was active during the interval. The valid format is a decimal (formatted to one decimal place).

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Indicates that this row is a summary row of statistical totals for all rows.

Times Run The number of times the garbage collector ran during the interval. The valid format is a positive integer.

Garbage Collection Cycle attributes

The Garbage Collection Cycle attribute group provides information about a single garbage-collection cycle that the Java. Virtual Machine hosting the application server performed.
The Garbage Collection Cycle attributes report the free heap space both before and after garbage collection, the heap space freed, and the number of objects moved during garbage collection. Use the Garbage Collection Cycle attributes in situations to examine the results of a particular garbage collection.
The attributes within this group are used to build the Garbage Collections - Selected Allocation Failure workspace.
This information is only collected for systems using an IBM JVM.

Allocation Failure Number The identifier assigned to the allocation-failure block for which the JVM ran the current garbage-collection cycle, which is associated with a bar in the Heap Usage - History bar chart. If your Java code called System.gc to start garbage collection, this number is 0. The valid format is a positive integer.

ASID The identifier (decimal) assigned to the address space running this servant region.

Compact (ms) The time (in milliseconds) required for the compaction phase of the garbage-collection cycle. The valid format is a positive integer.

Compaction Reason The code describing the reason garbage collection was initiated. The valid format is a positive integer. The compaction codes are:

Reasons for initiating garbage collection

Compaction Code Definition
1 Insufficient free space for the allocation request following the mark and sweep phases.
2 The heap is fragmented and benefits from a compaction.
3 Less than 15% free space available.
4 A call to System.gc requested garbage collection.
5 Less than 5% free space available.
6 Less than 128 K free space available.
7 Parameter Xcompactgc specified.
8 The transient heap has less than 5% free space available.
9 The heap is fragmented (this code marks additional reasons for compaction apart from compaction code 2).

Final References The number of final reference objects collected during this garbage-collection cycle. The valid format is a positive integer.

Garbage Collection Date and Time The date and time the Java Virtual Machine invoked the garbage collector. The valid format is a 16-character timestamp. This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.
Note to Solaris and HP-UX users: Since allocation-failure information is not recorded on these platforms, this column is always empty on these platforms.

Garbage Collection Number The number of this garbage-collection cycle. The valid format is a positive integer.

Heap Capacity (Kbytes) The total number of kilobytes allocated to the main heap after this garbage-collection cycle. The valid format is a positive integer.

Heap Free (%) after GC The percentage of heap space that is available after this garbage-collection cycle. The valid format is a decimal (formatted to one decimal place).

Heap Space Free (Kbytes) The number of kilobytes available within the heap after this garbage-collection cycle. The valid format is a positive integer.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

KBytes Free at Start of GC The number of kilobytes available in the heap before garbage collection began. The valid format is a positive integer.

Kbytes Freed The number of kilobytes freed by the garbage collector. The valid format is a positive integer.

Kbytes Moved The number of kilobytes moved on the heap during this compaction. The valid format is a positive integer.

Kbytes Used The number of kilobytes in the heap that were in use after this garbage-collection cycle. The valid format is a positive integer.

Mark (ms) The time (in milliseconds) required for the mark phase of the garbage-collection cycle. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Objects Moved The number of objects the garbage collector moved during this compaction. The valid format is a positive integer.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Phantom References The number of phantom reference objects collected during this garbage-collection cycle. "Phantom" refers to a specific Java class that defines object reachability. The valid format is a positive integer.

Process ID The unique identifier of the JVM process (the class ID of the JVM). The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Soft References The number of soft reference objects collected during this garbage-collection cycle. "Soft" refers to a specific Java class that defines object reachability. The valid format is a positive integer.

Sweep (ms) The time (in milliseconds) required for the sweep phase of the garbage-collection cycle. The valid format is a positive integer.

Time to Complete (ms) The time (in milliseconds) required to complete this garbage-collection cycle. The valid format is a positive integer.

Weak References The number of weak reference objects collected during this garbage-collection cycle. "Weak" refers to a specific Java class that defines object reachability. The valid format is a positive integer.
For more information, see:

High Availability Manager attributes

The High Availability Manager attributes provide aggregated information about the high availability managers.
The attributes within this group are used to build the High Availability Manager workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and then select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Bulletin-Board Rebuild Time The time taken (in milliseconds) to rebuild the global state of the bulletin-board. During this time no messages are received by the subscribers. If this time is too high, and is unacceptable, you might want to increase the number of coordinators. The valid format is a decimal (formatted to three decimal places).

Bulletin-Board Rebuild Time Count The count of times that were used for Bulletin-Board Rebuild Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Bulletin-Board Subjects The total number of subjects managed. The valid format is a positive integer. This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Bulletin-Board Subscriptions The total number of bulletin-board subscriptions. The valid format is a positive integer. This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Group State Rebuild Time The time taken (in milliseconds) to rebuild the global group state. During the rebuild time, no fail-over can happen. If this time is too high and is unacceptable for the desired availability, you might want to increase the number of coordinators. For proper operation of this counter, you must host the active coordinator in an application server other than the deployment manager. The valid format is a decimal (formatted to three decimal places).

Group State Rebuild Time Count The count of times that were used for Group State Rebuild Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Instrumentation Level The instrumentation level for availability manager counters. For WebSphere 5, the valid values are None, Low, Medium, High, and Maximum; for WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Local Bulletin-Board Subjects The total number of subjects being posted locally. The number includes the proxy postings (if any) done by the core group bridge service on behalf of servers belonging to different WebSphere cells. The valid format is a positive integer. This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Local Bulletin-Board Subscriptions Indicates the total number of bulletin-board subscriptions being posted locally.

Local Groups The total number of local groups. The valid format is a positive integer. This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Row Number The row number. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Whether this row is a summary row of statistical totals for all rows. Valid values are No and Yes.

J2C Connection Pools attributes

The J2C Connection Pools attribute group provides information about connectors that adhere to J2C, the WebSphere application server implementation of the J2C architecture.
Data counters for this category contain usage information about the J2C architecture that enables enterprise beans to connect and interact with procedural backend systems, such as Customer Information Control System (CICS) and Information Management System (IMS.). Examples include the number of managed connections or physical connections and the total number of connections or connection handles.
The attributes within this group are used to build the J2C Connection Pools workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Application ID Indicates J2EE application ID.

Average Free Connections The average number of free Managed Connections for the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Average Pool Size The average number of Managed Connections for the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Average Usage Time (ms) The average time (in milliseconds) that connections are in use (measured from when the connection is allocated to when it is returned). The valid format is a decimal (formatted to three decimal places).

Usage Time Count The count of times that were averaged for Average Usage Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Average Wait Time (ms) The average waiting time (in milliseconds) until a connection is granted for the interval. The valid format is a decimal (formatted to three decimal places).

Wait Time Count The count of times that were averaged for Average Wait Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Concurrent Waiting Threads The average number of threads concurrently waiting for a connection for the interval. The valid format is a positive integer. This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Connection Allocation Rate (per sec) The rate (per second) of application connections allocated from Managed Connections for the sampling interval. The valid format is a decimal (formatted to three decimal places).

Connection Creation Rate (per sec) The rate (per second) of Managed Connections created for the sampling interval. The valid format is a decimal (formatted to three decimal places).

Connection Destruction Rate (per sec) The rate (per second) of Managed Connections destroyed for the sampling interval. The valid format is a decimal (formatted to three decimal places).

Connection Factory Name The name of the connection factory. The valid format is an alphanumeric string, with a maximum of 256 characters.

Connection Handles The number of open application connections that have been allocated from the managed connections. The valid format is a positive integer.

Connection Pool Timeout Rate (per sec) The rate (per second) of connection pool timeouts for the sampling interval. The valid format is a decimal (formatted to three decimal places).

Connection Pool Timeouts The number of faults, such as timeouts, in connection pools for the sampling interval. The valid format is a positive integer.

Connection Return Rate (per sec) The rate (per second) of allocated application connections that have been returned for the sampling interval. The valid format is a decimal (formatted to three decimal places).

Connection Type The J2C connection type. The valid format is an alphanumeric string, with a maximum of 32 characters.

Connections Allocated The number of application connections allocated from Managed Connections. The valid format is a positive integer.

Connections Created The total number of Managed Connections created during the sampling interval. The valid format is a positive integer.

Connections Destroyed The number of Managed Connections destroyed during the sampling interval. The valid format is a positive integer.

Connections Granted The number of Managed Connections granted during the interval. The valid format is a positive integer.

Connections Returned The number of allocated application connections that have been returned (closed) during the sampling interval. The valid format is a positive integer.

Connections Used The number of Managed Connection objects available in a particular connection pool. This number includes all Managed Connection objects that have been created but not destroyed. The valid format is a positive integer.

Factory Label The abbreviated name of the connection factory. The valid format is an alphanumeric string, with a maximum of 32 characters.

Instrumentation Level The instrumentation level for the J2C connection pools. For WebSphere 5, the valid values are None, Low, Medium, High, and Maximum; for WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval Time The length (in seconds) of the sampling interval. The valid format is a positive integer.

Maximum Pool Size The maximum number of managed connections that can be created in this connection pool (blank for each individual managed connection). The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Percent of Time Pool at Max The average percent of the time that all connections are in use for the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Percent Used Bad The bad percent of pool usage by application. The valid format is a positive integer.

Percent Used Fair The fair percent of pool usage by application. The valid format is a positive integer.

Percent Used Good The good percent of pool usage by application. The valid format is a positive integer.

Pool Used (%) The average percent of the pool that is in use for the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Row Number The number of the row within the report, which corresponds to a bar in the Highest Miss Rates bar chart. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.

Summary of J2C Connections Whether this row is a summary row of statistical totals collected for all the J2C connection pools. Valid values are No and Yes.

Total Usage (ms) The total time (in milliseconds) the connection object used. The valid format is a decimal (formatted to three decimal places).

Total Wait (ms) The total time (in milliseconds) the connection object waited. The valid format is a decimal (formatted to three decimal places).
For more information, see:

JMS Summary attributes

The JMS Summary attributes provide information about how WebSphere application server applications are interacting with messaging middleware (WebSphere MQ) using the Java. Messaging Service (JMS). It provides such information as which queue managers and queues are being used and how many messages are being read and written.
The attributes within this group are used to build the JMS Summary workspace.
The attributes within this attribute group contain meaningful values only if your site has set the request data monitoring level to Level2 to collect data on JMS requests.

Application ID The unique identifier that is assigned automatically when the application is first configured and is preserved during the whole application life cycle. The valid format is a positive integer or -1 which means that Application ID is aggregated statistic for all applications.

ASID The identifier (decimal) assigned to the address space running this servant region.

Average Processing Time (ms) The average time (in milliseconds) per request using the JMS. The valid format is a decimal (formatted to three decimal places).

Processing Time Count The count of times that were averaged for Average Processing Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Browse Average Time (ms) The average time (in milliseconds) for each browse request from the queue. The valid format is a decimal (formatted to three decimal places).

Browse Count The number of messages browsed from the queue. The valid format is a positive integer.

Browse Rate (per sec) The number of messages (per second) browsed from a JMS queue. The valid format is a decimal (formatted to three decimal places).

Browse Total Time (ms) The total time (in milliseconds) consumed by browse requests from the queue. The valid format is a positive integer.

Full Name The complete name of the message queue, which consists of the queue manager name concatenated to the queue name and separated by a slash. The valid format is an alphanumeric string, with a maximum of 100 characters.

Interval (sec) The length (in seconds) of the interval. The valid format is a positive integer.

JMS Connection Label A shortened version of the full name. The valid format is an alphanumeric string, with a maximum of 12 characters.

Manager Name The name of the WebSphere MQ queue manager (not available currently). This attribute is blank if WebSphere MQ is not being used. The valid format is an alphanumeric string, with a maximum of 48 characters.

Name The name of the WebSphere MQ queue. The valid format is an alphanumeric string, with a maximum of 48 characters.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Origin Node The name of the application server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Process ID The unique identifier of the JVM process (the class ID of the JVM). The valid format is a positive integer.

Publish Average Time (ms) The average time (in milliseconds) for each publish request to be sent to the queue. The valid format is a decimal (formatted to three decimal places).

Publish Count The number of publish requests sent to the queue. The valid format is a positive integer.

Publish Rate (per sec) The number of publish requests (per second) sent to a JMS queue. The valid format is a decimal (formatted to three decimal places).

Publish Total Time (ms) The total time (in milliseconds) consumed by all publish requests for the queue. The valid format is a positive integer.

Receive Average Time (ms) The average time (in milliseconds) for each get from the queue. The valid format is a decimal (formatted to three decimal places).

Receive Count The number of destructive gets from the queue. The valid format is a positive integer.

Receive Rate (per sec) The number of destructive gets (per second) made from the queue. The valid format is a decimal (formatted to three decimal places).

Receive Total Time (ms) The total time (in milliseconds) consumed by gets from the queue. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Send Average Time (ms) The average time (in milliseconds) for each put to the queue. The valid format is a decimal (formatted to three decimal places).

Send Count The number of messages put to the queue. The valid format is a positive integer.

Send Rate (per sec) The number of messages (per second) put to the queue. The valid format is a decimal (formatted to three decimal places).

Send Total Time (ms) The total time (in milliseconds) consumed by puts to the queue. The valid format is a positive integer.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Indicates that this row is a summary row of statistical totals for all rows.

Total Time (ms) The total time (in milliseconds) spent accessing the queue. The valid format is a positive integer.

Type The type of message manager. The valid values are Queue and Topic.
For more information, see:

Log Analysis attributes

The Log Analysis attributes provide application server error and exception conditions which are recorded in the application server log files.
The log files are SystemOut.log and SystemErr.log. Use the Log Analysis attributes in situations to monitor errors and exception conditions and their severity.
The attributes within this group are used to build the Log Analysis workspace.

ASID The identifier (decimal) assigned to the address space running this servant region.

Component The name of the component that caused the error. The valid format is an alphanumeric string, with a maximum of 32 characters.

Error Date and Time The date and time the event occurred. The valid format is a timestamp. This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Job ASID The identifier (hexadecimal) assigned to the address space running this servant region. The valid format is an alphanumeric string, with a maximum of four characters.

Job Name The job name assigned to this servant region. The valid format is an alphanumeric string, with a maximum of eight characters.

Message ID The identifier assigned to the message. The valid format is an alphanumeric string, with a maximum of 12 characters.

Message Origin Where the message originates; that is, the log file name and line number. The valid format is an alphanumeric string, with a maximum of 32 characters. This field is not empty only on the z/OS system.

Message Text The text of the message. The valid format is alphanumeric string, with a maximum of 256 characters. All error message text data that goes beyond 256 characters are truncated and are not shown in the portal.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Process ID The process identifier of the Java virtual machine. The valid format is an alphanumeric string, with a maximum of eight characters. In a z/OS system, this field displays in hexadecimal format.

Sequence Number The sequence number in the JMX notifications stream. The valid format is positive integer.

Server Instance Name The name of the application server instance. This is the name of a single address space that can run application code (called a "specific server" or simply a "server"). The valid format is an alphanumeric string, with a maximum of eight characters.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Severity The severity of the message. The valid values are:

Message severities and their meanings

Severity Definition
Informational A message intended to convey only user information
Unconditional A message of type Unconditional
Dump A message of type Dump
SystemOut A message written directly to System.out by the user application or internal components
SystemError A message written directly to System.err by the user application or internal components
User A message of type User
EntryMethod A message written upon entry to a method
ExitMethod A message written upon exit from a method
Event A message of type Event
Debug A message of type Debug
Audit An audit message
Warning A warning message
Error An error message
Terminate A message of type Terminate (exit process)
Fatal A fatal message
Unknown A placeholder that indicates the message type was not recognized

Thread ID The unique identifier of the thread where the event occurred. The valid format is an alphanumeric string, with a maximum of 16 characters.

Listener Port attributes

Origin Node The server name subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 256 characters.

Sample Date and Time The date and time at which the agent has collected data.

Interval Time Indicates the length of the interval in seconds. The valid format is a 4-byte integer.

Name Name of the Listener Port. The valid format is an alphanumeric string, with a maximum of 256 characters.

Status The status of the Listener Port: Started or Stopped.

JMS Connection Factory The JNDI name for the JMS ConnectionFactory in use by this Listener Port. The valid format is an alphanumeric string, with a maximum of 256 characters.

JMS Destination The JNDI name for the JMS Queue or Topic in use by this Listener Port. The valid format is an alphanumeric string, with a maximum of 256 characters.

Max Sessions The value of max sessions in use by this Listener Port. The valid format is a 4-byte integer.

Max Retries The value of max retries in use by this Listener Port. The valid format is a 4-byte integer.

Max Messages The value of max messages in use by this Listener Port. The valid format is a 4-byte integer.

Messaging Engine Communications attributes

The Messaging Engine Communications attributes display statistics for all the messaging engines being hosted by the current application server.
The attributes within this group are used to build the Messaging Engine Communications workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.
Attributes in this group are only provided for IBM WebSphere application server version 6.0 or later.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

API Connections The number of sessions being used by messaging engines that are currently network connected to this application server. The valid format is a positive integer.

Buffered Reads (bytes) The number of bytes of data that have been received from the network and are held pending further processing. Large values might indicate that the application server is unable to process data fast enough to keep up with the other application server processes hosting messaging engines. The valid format is a positive integer.

Buffered Writes (bytes) The number of bytes of data being held pending transmission. Large values might indicate network congestion or application server processes hosting messaging engines which are unable to process data fast enough to keep up with the application server. The valid format is a positive integer.

Errors The communication errors that have occurred and resulted in a network connection to a messaging engine being disconnected. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the Messaging Engine Communications. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Message Read (bytes) The number of bytes of message data received from application server processes hosting messaging engines over network connections. This does not include data used to negotiate the transmission of messages. The valid format is a positive integer.

Message Written (bytes) The number of bytes of message data sent to application server processes hosting messaging engines over network connections. This does not include data used to negotiate the transmission of messages. The valid format is a positive integer.

Messaging Engine Attached The number of distinct application server processes hosting messaging engines currently network connected to this application server. The valid format is a positive integer.

Messaging Engine Name The name of the message engine. The value format is an alphanumeric string, with a maximum of 256 characters.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Reads The number of read operations used to receive data from application server processes hosting messaging engines via network connections. The valid format is a positive integer.

Reads Blocked The number of read operations that could not be completed immediately. This number can be used as an indicator of network congestion when communicating with application server processes hosting messaging engines. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Whether this row is a summary row of statistical totals for all messaging engine communications. Valid values are No and Yes.

Total Read (bytes) The Number of bytes of data received from application server processes hosting messaging engines. The valid format is a positive integer.

Total Written (bytes) The Number of bytes of data sent to application server processes hosting messaging engines. The valid format is a positive integer.

Writes The number of write operations used to transmit data to application server processes hosting messaging engines via network connections. The valid format is a positive integer.

Writes Blocked The number of write operations that could not be completed immediately. This number can be used as an indicator of network congestion when communicating with application server processes hosting messaging engines. The valid format is a positive integer.

Messaging Engines attributes

The Messaging Engines attributes display aggregated information about the performance of the messaging engines supported by WebSphere server.
The attributes within this group are used to build the Messaging Engines workspace.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.
Attributes in this group are only provided for IBM WebSphere application server version 6.0 or later.

Average Local Wait Time (ms) The time spent by messages on this durable subscription at consumption. If this time is not what was expected, view the message using the admin console to decide what action needs to be taken. The valid format is a positive integer.

Local Wait Time Count The count of times that were averaged for Average Local Wait Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Expired Messages The number of report enabled messages that expired while on this queue. The valid format is a positive integer.

Incomplete Topic Publications The number of publications not yet received by all current subscribers. If this number is unexpected, view the publication using the admin console to take action. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the messaging engines. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Messaging Engine Name The name of the messaging engine. The valid format is an alphanumeric string, with a maximum of 256 characters.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Status The status of the messaging engine. The valid format is a positive integer.

Summary of All Applications Whether this row is a summary row of statistical totals for all messaging engines. Valid values are No and Yes.

Total Published The total number of publications to the messaging engines. The valid format is a positive integer.
For more information, see:

Portal Page Summary attributes

The Portal Page Summary attributes provide information about response times statistics for all portal page requests that completed on monitored WebSphere Portal server during the interval.
The attributes within this group are used to build the Portal Pages Summary workspace.

ASID The identifier (decimal) assigned to the address space running this servant region.

Average Response Time (ms) The average response time (in milliseconds) of requests are processed by the portal pages during the current interval. The valid format is a decimal (formatted to three decimal places).

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Process ID The unique identifier of the JVM process (the class ID of the JVM). The valid format is a positive integer.

Portal Page Name The name of the portal page. The value format is an alphanumeric string, with a maximum of 128 characters.

Request Count The count of requests processed by the portlet page during the current interval. The valid format is a positive integer.

Row Number The number of the row. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Indicates that this row is a summary row of statistical totals for all rows.

Total Response (ms) The total time (in milliseconds) of responses. The valid format is a decimal (formatted to three decimal places).
For more information, see:

Portal Summary attributes

The Portal Summary attributes provide aggregated response times statistics about all portal pages and portlet requests that completed on monitored WebSphere Portal server during the interval.
The attributes within this group are used to build the Portal Summary workspace.

ASID The identifier (decimal) assigned to the address space running this servant region.

Authentication Request Count The number of authentication requests during the interval. The valid format is a positive integer.

Authentication Total (ms) The total time (in milliseconds) of authentication requests completed during the interval. The valid format is a decimal (formatted to three decimal places).

Authorization Request Count The number of authorization requests during the interval. The valid format is a positive integer.

Authorization Total (ms) The total time (in milliseconds) of authorization requests completed during the interval. The valid format is a decimal (formatted to three decimal places).

Average Response Time of Portal Pages (ms) The average response time (in milliseconds) of all portal pages/Gateway Servlet requests completed during the interval. The valid format is a decimal (formatted to three decimal places).

Average Response Time of Portlets (ms) The average response time (in milliseconds) of all portlets requests completed during the interval. The valid format is a decimal (formatted to three decimal places).

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Model Building Request Count The number of model building requests during the interval. The valid format is a positive integer.

Model Building Total (ms) The total time (in milliseconds) of model building requests completed during the interval. The valid format is a decimal (formatted to three decimal places).

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Page Loading Request Count The number of page loading requests during the interval. The valid format is a positive integer.

Page Loading Total (ms) The total time (in milliseconds) of page loading requests completed during the interval. The valid format is a decimal (formatted to three decimal places).

Portal Page Request Count The number of portal page requests during the interval. The valid format is a positive integer.

Portal Pages Total Response (ms) The total response time (in milliseconds) of all portal pages/Gateway Servlet requests completed during the interval. The valid format is a decimal (formatted to three decimal places).

Portlets Request Count The number of portlets requests during the interval. The valid format is a positive integer.

Process ID The unique identifier of the JVM process (the class ID of the JVM). The valid format is a positive integer.

Portlets Total Response(ms) The total response time (in milliseconds) of all portlets requests completed during the interval. The valid format is a decimal (formatted to three decimal places).

Response Time of Authentication (ms) The response time (in milliseconds) of authentication. The valid format is a positive integer.

Response Time of Authorization (ms) The response time (in milliseconds) of authorization. The valid format is a positive integer.

Response Time of Model Building (ms) The response time (in milliseconds) of model building. The valid format is a positive integer.

Response Time of Page loading (ms) The response time (in milliseconds) of page loading. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Indicates that this row is a summary row of statistical totals for all rows.
For more information, see:

Portlet Summary attributes

The Portlet Summary attributes provide information about response times of all portlet requests that completed on monitored WebSphere Portal.
The attributes within this group are used to build the Portlet Summary workspace.

ASID The identifier (decimal) assigned to the address space running this servant region.

Average Response Time (ms) The average response time for portlet during the current interval. The valid format is a decimal (formatted to three decimal places).

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Portlet Name The name of the portlet. The value format is an alphanumeric string, with a maximum of 256 characters.

Process ID The unique identifier of the JVM process (the class ID of the JVM). The valid format is a positive integer.

Request Count The count of requests for portlet during the current interval. The valid format is a positive integer.

Request Rate The rate at which the requests processed by portlet during the current interval. The valid format is a decimal (formatted to three decimal places).

Row Number The number of the row. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Indicates that this row is a summary row of statistical totals for all rows.

Total Response (ms) The total response time for portlet during the current interval. The valid format is a decimal (formatted to three decimal places).
For more information, see:

Queue attributes

The Queue attributes provide aggregated information about the point to point messaging.
The attributes within this group are used to build the Destinations workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.
Attributes in this group are only provided for IBM WebSphere application server version 6.0 or later.

Aggregate Message Wait Time The time spent by messages in the bus at consumption. If this time is not what was expected, view the message using the admin console to decide what action needs to be taken. The valid format is a positive integer.

Aggregate Message Wait Time Count The count of times that were used for Aggregate Message Wait Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Assured Persistent Messages Consumed The number of assured persistent messages consumed, for the lifetime of this messaging engine. The valid format is a positive integer.

Assured Persistent Messages Produced The number of assured persistent messages produced, for the lifetime of this messaging engine. The valid format is a positive integer.

Available Message The number of messages available for a queue for consumption. If this number is close to the destination high messages value, review the high messages value. The valid format is a positive integer.

Best Effort Non-persistent Messages Consumed The number of best effort non-persistent messages consumed, for the lifetime of this messaging engine. The valid format is a positive integer.

Best Effort Non-persistent Messages Produced The number of best effort non-persistent messages produced, for the lifetime of this messaging engine. The valid format is a positive integer.

Express Non-persistent Messages Consumed The number of express non-persistent messages consumed, for the lifetime of this messaging engine. The valid format is a positive integer.

Express Non-persistent Messages Produced The number of express non-persistent messages produced, for the lifetime of this messaging engine. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the database connection pool for the data source. Valid values are None, Low, Medium, High, Basic, Extended, All, Custom, and Maximum. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Local Consumer The number of currently attached local consumers. The valid format is a positive integer.

Local Consumer Attaches The number of times an attachment has been made to this queue by local consumers. The lifetime of this value is the lifetime of the messaging engine. The valid format is a positive integer.

Local Message Wait Time The time spent by messages on this queue at consumption. If this time is not what was expected, view the message using the admin console to decide what action needs to be taken. The valid format is a positive integer.

Local Message Wait Time Count The count of times that were used for Local Message Wait Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Local Oldest Message Age The longest time any message has spent on this queue. If this time is not what was expected, view the message using the admin console to decide what action needs to be taken. The valid format is a positive integer.

Local Producer The number of currently attached local producers. The valid format is a positive integer.

Local Producer Attaches The number of times an attachment has been made to this queue by local producers. The lifetime of this value is the lifetime of the messaging engine. The valid format is a positive integer.

Messaging Engine Name The name of the messaging engine. The value format is an alphanumeric string, with a maximum of 256 characters.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Queue Name The name of the queue. The value format is an alphanumeric string, with a maximum of 256 characters.

Reliable Non-persistent Messages Consumed The number of reliable non-persistent messages consumed, for the lifetime of this messaging engine. The valid format is a positive integer.

Reliable Non-persistent Messages Produced The number of reliable non-persistent messages produced, for the lifetime of this messaging engine. The valid format is a positive integer.

Reliable Persistent Messages Consumed The number of reliable persistent messages consumed, for the lifetime of this messaging engine. The valid format is a positive integer.

Reliable Persistent Messages Produced The number of reliable persistent messages produced, for the lifetime of this messaging engine. The valid format is a positive integer.

Report Enabled Messages Expired The number of report enabled messages that expired while on this queue. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Whether this row is a summary row of statistical totals for all rows. Valid values are No and Yes.

Total Messages Consumed The total number of messages consumed from this queue, for the lifetime of this messaging engine. The valid format is a positive integer.

Total Messages Produced The total number of messages produced to this queue, for the lifetime of this messaging engine. The valid format is a positive integer.

Unavailable Message The number of messages locked or uncommitted. This means messages that have been added or removed but the transaction has not been committed yet. If this number is high, check which messages are locked and why.
For more information, see:

Remote Configuration Requests attributes

The Remote Configuration Requests attributes provide information about remote configuration.
The attributes within this group are used to build the WebSphere Agent workspace.

Command Indicates the Command of the request.

Node Name The system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Origin Node The server name subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Request Identifier The Request ID. The valid format is an alphanumeric string, with a maximum of 48 characters.

Package Count Indicates the package count for this request/response.

Package Index Indicates the current index of the packages.

Request Context Indicates the request context.

Response Context Indicates the response context.

Return Value Indicates the return value of the request.

Target Agent Code Two-letter agent product code that specifies information about the product being configured.
For more information, see:

Request Analysis attributes

The Request Analysis attributes provide response times and functional decomposition information about requests (servlets, JSPs, SCA requests, Portal requests, EJB methods, and web services) that ran on the application server.
The attributes within this group are used to build the Request Analysis workspace.

Application Name The name of the application to which the request belongs. The valid format is an alphanumeric string, with a maximum of 256 characters.
The application name is, in the present version, not provided for SCA requests.

Application Time (ms) On monitoring level 1, the average time (in milliseconds) this request spent processing application requests other than JCA, JMS, JNDI, JDBC, web service, and SCA requests. This field can have a zero value if the total time is less than the number of requests, due to truncation. On monitoring level 2, the average time (in milliseconds) this request spent processing Servlet and EJB requests. The valid format is a positive integer.

Application Time Count The count of times that were averaged for Application Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Application Time Percent The percentage of time this request spent processing application requests other than JCA, JMS, JNDI, JDBC requests, web services, and SCA. The valid format is a decimal (formatted to one decimal place).

Application Time Percent Count The count of individual percentages that were averaged for Application Time Percent. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Application Bad Delay (msec) The delay time (in milliseconds) in the application tier collected during the interval. This column is non-zero value when application delay exceeds the bad threshold configured for it. The valid format is a positive integer.

Application Fair Delay (msec) The delay time (in milliseconds) in the application tier collected during the interval. This column is non-zero value when application delay exceeds the fair threshold configured for it. The valid format is a positive integer.

Application Good Delay (msec) The delay time (in milliseconds) in the application tier collected during the interval. This column is non-zero when application delay is less than fair threshold configured for it. The valid format is a positive integer.

Application Tier Delay Type This attribute defines the request type based on its delay time in the application tier. Valid values are Unknown, Good, Fair, and Bad.

Application Tier Response (msec) The actual response time in milliseconds in the application tier collected during the interval. The valid format is a positive integer.

Average Response (ms) The average time (in milliseconds) required each time this request ran during the interval. The valid format is a positive integer.

ASID The identifier (decimal) assigned to the address space running this servant region.

Backend Bad Delay (msec) The delay time (in milliseconds) in the backend tier collected during the interval. This column is non-zero value when backend delay exceeds the bad threshold configured for it. The valid format is a positive integer.

Backend Fair Delay (msec) The delay time (in milliseconds) in the backend tier collected during the interval. This column is non-zero value when backend delay exceeds the fair threshold configured for it. The valid format is a positive integer.

Backend Good Delay (msec) The delay time (in milliseconds) in the backend tier collected during the interval. This column is non-zero when backend delay is less than fair threshold configured for it. The valid format is a positive integer.

Backend Tier Delay Type This attribute defines the request type based on its delay time in the backend tier. Valid values are Unknown, Good, Fair, and Bad.

Backend Tier Response (msec) The actual response time in milliseconds in the backend tier collected during the interval. The valid format is a positive integer.

Client Bad Delay (msec) The delay time (in milliseconds) in the client tier collected during the interval. This column is non-zero value when client delay exceeds the bad threshold configured for it. The valid format is a positive integer.

Client Fair Delay (msec) The delay time (in milliseconds) in the client tier collected during the interval. This column is non-zero value when client delay exceeds the fair threshold configured for it. The valid format is a positive integer.

Client Good Delay (msec) The delay time (in milliseconds) in the client tier collected during the interval. This column is non-zero when client delay is less than fair threshold configured for it. The valid format is a positive integer.

Client Tier Delay Type This attribute defines the request type based on its delay time in the client tier. Valid values are Unknown, Good, Fair, and Bad.

Client Tier Response (msec) The actual response time in milliseconds in the client tier collected during the interval. The valid format is a positive integer.

Completion Count The number of requests that successfully completed during the interval. The valid format is a positive integer.

Custom Request Count The number of custom requests. The valid format is a positive integer.

Custom Request Time (ms) The average time (in milliseconds) the custom requests spent. The valid format is a positive integer.

Custom Request Time (%) The percentage of time the custom requests spent. The valid format is a decimal (formatted to one decimal place).

EJB Count The number of times this request invoked an Enterprise Java Bean (EJB) request. The valid format is a positive integer.

EJB Time (ms) The average time (in milliseconds) this request spent processing Enterprise Java Bean (EJB) requests. This field can have a zero value if the total time is less than the number of requests, due to truncation. The valid format is a positive integer.

EJB Time (%) The percentage of time this request spent processing Enterprise Java Bean (EJB) requests. The valid format is a decimal (formatted to one decimal place).

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

JCA Count The number of times this request invoked a J2EE Connector Architecture (JCA) request. The valid format is a positive integer.

JCA Time (ms) The average time (in milliseconds) this request spent processing J2EE Connector Architecture (JCA) requests. This field can have a zero value if the total time is less than the number of requests, due to truncation. The valid format is a positive integer.

JCA Time (%) The percentage of time this request spent processing J2EE Connector Architecture (JCA) requests. The valid format is a decimal (formatted to one decimal place).

JMS Count The number of times this request invoked a Java Message Service (JMS) request. The valid format is a positive integer.

JMS Time (ms) The average time (in milliseconds) this request spent processing Java Message Service (JMS) requests. This field can have a zero value if the total time is less than the number of requests, due to truncation. The valid format is a positive integer.

JMS Time (%) The percentage of time this request spent processing Java Message Service (JMS) requests. The valid format is a decimal (formatted to one decimal place).

JNDI Count The number of times this request invoked a JNDI request. The valid format is a positive integer.

JNDI Time (ms) The average time (in milliseconds) this request spent processing JNDI requests. This field can have a zero value if the total time is less than the number of requests, due to truncation. The valid format is a positive integer.

JNDI Time (%) The percentage of time this request spent processing JNDI requests. The valid format is a decimal (formatted to one decimal place).

Level 2 Request Count The number of times this request was run with Mod Level 2 turned on. The valid format is a positive integer.

Level 2 Total Time (ms) The total time (in milliseconds) this request was run with Mod Level 2 turned on. The valid format is a positive integer.

Longest Response (ms) The maximum time (in milliseconds) it took this request to run during the interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Origin Node The name of the application server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Portal Processing Count The number of times the request invoked a WebSphere Portal page or portlet request. The valid format is a positive integer.

Portal Processing Time (ms) The average time (in milliseconds) the request spent in processing WebSphere Portal page or portlet requests. This field can have a zero value if the total time is less than the number of requests. The valid format is a positive integer.

Portal Processing Time (%) The percentage of time the request spent in processing WebSphere Portal page or portlet requests. The valid format is a decimal (formatted to one decimal place).

Process ID The process identifier of the Java virtual machine. The valid format is a positive integer.

Request Bad Response Threshold (msec) The threshold that defines the bad requests. A request that spends more time to complete than this threshold to complete is a bad request. The valid format is a positive integer.

Request Completion (%) The percentage of the requests that completed successfully during the interval. The valid format is a positive integer.

Request Completion Level The completion level of the requests during the interval. Valid values are Unknown, Good, Fair, and Bad.

Request Count The number of times this request ran during the interval. The valid format is a positive integer.

Request Detail The URI for servlet requests, or the method name for EJBs. The valid format is an alphanumeric string, with a maximum of 128 characters.

Request Fair Response Threshold (msec) The threshold that defines the fair requests. A request that spends more time than this threshold and less time than the Request Bad Response Threshold (msec) attribute to complete is a fair request. The valid format is a positive integer.

Request Bad Delay (msec) The delay time (in milliseconds) collected during the interval. This column is non-zero value when the whole request response time exceeds the bad threshold configured for it. The valid format is a positive integer.

Request Fair Delay (msec) The delay time (in milliseconds) collected during the interval. This column is non-zero value when the whole request response time exceeds the fair threshold configured for it. The valid format is a positive integer.

Request Good Delay (msec) The delay time (in milliseconds) collected during the interval. This column is non-zero value when the whole request response time is less than fair threshold configured for it. The valid format is a positive integer.

Request Delay Type The type of the request delay. Valid values are Unknown, Good, Fair, and Bad.

Request Label A shortened version of Request Name, used to display the request name in the chart view. The valid format is an alphanumeric string, with a maximum of 32 characters.

Request Name The URL for servlet requests, or the fully qualified class name for EJBs. The valid format is an alphanumeric string, with a maximum of 128 characters.

Request Rate (per sec) The number of requests completed per second during the interval. If the sampling rate is less than 100%, this number is extrapolated to estimate 100% of completed requests. The valid format is a decimal (formatted to three decimal places).

Request Type The type of request being run. Valid values are Servlet, EJB_Method, Custom, All_Workloads, Unknown, Portlet, SCA, web service provider, and web service client.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Sampling Rate (%) The percentage of requests being sampled. The valid format is a positive integer.

SCA Count The number of times this request invoked a Service Component Architecture (SCA) request. The valid format is a positive integer.

SCA Time (ms) The average time (in milliseconds) this request spent processing Service Component Architecture (SCA) requests. This field can have a zero value if the total time is less than the number of requests, due to truncation. The valid format is a positive integer.

SCA Time (%) The percentage of time this request spent processing Service Component Architecture (SCA) requests. The valid format is a decimal (formatted to one decimal place).

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Servlet Count The number of times this request invoked a Servlet request. The valid format is a positive integer.

Servlet Time (ms) The average time (in milliseconds) this request spent processing Servlet requests. This field can have a zero value if the total time is less than the number of requests, due to truncation. The valid format is a positive integer.

Servlet Time (%) The percentage of time this request spent processing Servlet requests. The valid format is a decimal (formatted to one decimal place).

SQL Connect Count The number of times this request connected to a JDBC database. The valid format is a positive integer.

SQL Connect Time (ms) The average time (in milliseconds) this request spent connecting to a JDBC database. This field can have a zero value if the total time is less than the number of requests, due to truncation. The valid format is a positive integer.

SQL Connect Time (%) The percentage of time this request spent connecting to a JDBC database. The valid format is a decimal (formatted to one decimal place).

SQL Execute Count The number of times this request executed a JDBC database. The valid format is a positive integer.

SQL Execute Time (ms) The average time (in milliseconds) this request spent executing a JDBC database. This field can have a zero value if the total time is less than the number of requests, due to truncation. The valid format is a positive integer.

SQL Execute Time (%) The percentage of time this request spent executing a JDBC database. The valid format is a decimal (formatted to one decimal place).

SQL Query Count The number of times this request queried a JDBC database. The valid format is a positive integer.

SQL Query Time (ms) The average time (in milliseconds) this request spent querying a JDBC database. This field can have a zero value if the total time is less than the number of requests, due to truncation. The valid format is a positive integer.

SQL Query Time (%) The percentage of time this request spent querying a JDBC database. The valid format is a decimal (formatted to one decimal place).

SQL Update Count The number of times this request updated a JDBC database. The valid format is a positive integer.

SQL Update Time (ms) The average time (in milliseconds) this request spent updating a JDBC database. This field can have a zero value if the total time is less than the number of requests, due to truncation. The valid format is a positive integer.

SQL Update Time (%) The percentage of time this request spent updating a JDBC database. The valid format is a decimal (formatted to one decimal place).

Summary Indicates that this row is a summary row of statistical totals for all rows.

Total Time (ms) The total CPU time (in milliseconds) this request consumed during the interval. The valid format is a positive integer.

Web Service Count The number of times this request invoked a Web Service request. The valid format is a positive integer.

Web Service Time (ms) The average time (in milliseconds) this request spent processing Web Service requests. This field can have a zero value if the total time is less than the number of requests. The valid format is a positive integer.

Web Service Time (%) The percentage of time this request spent processing Web Service requests. The valid format is a decimal (formatted to one decimal place).

36. Requests Monitoring Configuration attributes

The Requests Monitoring Configuration attributes provide information for all requests monitored in application. Use these attributes to monitor application edge requests. The agent supports three types of edge requests, Servlet/JSP, EJB, and Portal.
The attributes within this group are used to build the Request Baseline workspace.

Application Name The name of the application to which the request belongs. The valid format is an alphanumeric string, with a maximum of 256 characters.

Application ID The unique identifier that is assigned automatically when the application is first configured and is preserved during the whole application life cycle. The valid format is a positive integer.

Application Tier Threshold (msec) The response time threshold in the application tier in milliseconds. The valid format is a positive integer.

Auto Threshold Bad Projection (%) The bad response time projection used for auto threshold. The valid format is a positive integer.

Auto Threshold Fair Ratio The percentage to derive the fair response time threshold from the baseline selection. The valid format is a positive integer.

Auto Threshold Fair Projection (%) The fair response time projection used for auto threshold. The valid format is a positive integer.

Auto Threshold Mode The request auto threshold mode. Valid values are Default, Custom, and Disabled.

Auto Threshold Deviation (%) The maximum allowed deviation of requests baseline data used for auto threshold. The valid format is a positive integer.

Auto Threshold Percent (%) The minimum percent of requests baseline data used for auto threshold. The valid format is a positive integer.

Backend Tier Threshold (msec) The response time threshold in the backend tier in milliseconds. The valid format is a positive integer.

Bad Response Threshold (msec) The time (in milliseconds) that defines the bad requests. A request that spends more time than this threshold to complete is a bad request. Use this attribute with Fair Response Threshold (msec) attribute and Fair Response Zone (msec) attribute. The valid format is a positive integer.

Bad Errors Rate Threshold The value of bad error rate percentage. The valid format is a positive integer.

Baselined Request Count The total number of requests accumulated in the baseline. This counter shows the data since the baseline starts. The valid format is a positive integer.

Client Tier Threshold (msec) The response time threshold in the client tier in milliseconds. The valid format is a positive integer.

Fair Response Threshold (msec) The time (in milliseconds) that defines the fair requests. A request that spends less time than this threshold to complete is a good request. Use this attribute with Fair Response Zone (msec) attribute and Bad Response Threshold (msec) attribute. The valid format is a positive integer.

Fair Response Zone (msec) The time span (in milliseconds) that defines the fair requests. This time span is between the fair response time threshold and the bad response time threshold. If the response time of a request falls into this time span, the request is a fair request. Use this attribute with Fair Response Threshold (msec) attribute and Bad Response Threshold (msec) attribute. The valid format is a positive integer.

Fair Errors Rate Threshold The value of fair error rate percentage. The valid format is a positive integer.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Request Detail The request detail name. The valid format is an alphanumeric string, with a maximum of 256 characters.

Request ID The unique identifier of the request that belongs to the application. The valid format is a positive integer.

Request Label A shortened version of Request Name, used to display the request name in the chart view. The valid format is an alphanumeric string, with a maximum of 24 characters.

Request Name The URL for servlet requests, or the fully qualified class name for EJBs. The valid format is an alphanumeric string, with a maximum of 256 characters.

Request Type The type of request being run. Valid values are All, Servlet/JSP, EJB, Portal, SCA Target, Web Service Provider, and Web Service Client.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.
For more information, see:

37. Request Times and Rates attributes

The Request Times and Rates attribute group provides information about historical request throughput and average response time for a particular application server.
The attributes within this group are used to build the WebSphere App Server workspace.

Application Name The name of the application to which the request belongs. The valid formats are as follows:

An alphanumeric string, with a maximum of 256 characters.
An empty string means that this sample is aggregated data for all applications

ASID The identifier (decimal) assigned to the address space running this servant region.

Average Load The average number of concurrent requests during the interval. The valid format is a decimal (formatted to three decimal places).

Average Request Completion Rate The average request completion rate (that is, the request throughput). If the sampling rate is less than 100%, this number is extrapolated to estimate 100% of completed requests. The valid format is a positive integer.

Average Request Response Time The average request response time, in milliseconds. The valid format is a positive integer.

Error Rate (%) The error rate of the request during the interval. The valid format is a decimal (formatted to three decimal places).

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Process ID Indicates the process ID of the JVM.

Request Count The number of requests processed during the current interval. The valid format is a positive integer.

Request Data Monitoring Level Indicates request data monitoring level for application.

Request Type The type of request being run. Valid values are Servlet, EJB_Method, Custom, All_Workloads, Unknown, Portlet, SCA Target, Web Service Provider, and Web Service Client.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Sampling Rate (%) The percentage of edge requests-such as servlets and JSPs-that were sampled during the interval. The valid format is a positive integer.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Indicates that this row is a summary row of statistical totals for all rows.

Total (ms) The total time used (in milliseconds) during the interval. The valid format is a decimal (formatted to three decimal places).

38. Selected Request attributes

The Selected Request attribute group provides detailed information about requests for database (that is, JDBC), messaging (that is, JMS), or EIS (that is, J2C) services by transactions.
The attributes within this group are used to build these workspaces:
- Datasources JMS Queues - Resource Adapters
Selected Request - Portal Processing
Selected Request - Service Components workspace

The attributes within this attribute group contain meaningful values only if your site has set the request data monitoring level to Level2 to collect data on nested requests.

Activity Category The type of request. Valid values are n/a (not applicable), JDBC, JMS, JCA, and Unknown.

Activity Detail Detailed information about the activity performed by the selected request, for example, the SQL statement being processed. The valid format is an alphanumeric string, with a maximum of 128 characters.

Activity Label An abbreviated version of Activity Name, used to display the activity name in the chart view. The valid format is an alphanumeric string, with a maximum of 32 characters.

Activity Name The resource that the request is accessing, for example, the data source name. The valid format is an alphanumeric string, with a maximum of 128 characters.

Activity Type The type of the resource being requested. Valid values are:

Activity types

Type Definition
n/a not applicable
Servlet A call to a doGet or doPost methods of a servlet
EJB_Method_Call A call to a business method for an EJB class
Obtain_SQL_Connection_from_Datasource A call to obtain a connection from a JDBC data source
SQL_Query A Query request to a JDBC data source
SQL_Update An Update request to a JDBC data source
SQL_Other Any other request to a JDBC data source
JMS_Message_Browse A call to browse a message from a JMS queue
JMS_Message_Get A call to receive a message from a JMS queue (that is, a destructive get)
JMS_Message_Put A call to put a message from a JMS queue
JMS_Publish_Message A call to publish a publication to a JMS queue
JCA_CCI_Execute_interaction A request by a J2EE application to execute a JCA interaction (a JDBC, JMS, or other JCA-supported operation) against a backend system
JNDI_Lookup A call to JNDI to build an InitialContext or to perform a lookup
Unknown The activity type cannot be determined
Portlet_Processing A call for portlet processing request
Portlet_Authorization A call for portlet authorization request
Portal_Authentication A call for portal authentication request
Portal_Model_Building A call for portal page model building request
Portal_Page_Loading A call for portal page loading request
Portal_Page_Rendering A call for portal page rendering request
Portal_Legacy_Action A call for portal legacy action request
Portal_Standard_Action A call for portal standard action (JSR-88) request
SCA A call for Service Component Architecture (SCA) request
Web Service Provider A call to a web service provide
Web Service Client A call to a web service client

ASID The identifier (decimal) assigned to the address space running this servant region.

Average Response (ms) The average time (in milliseconds) executing this request, per occurrence. The valid format is a decimal (formatted to one decimal place).

Delay Percent The percentage of execution time this activity consumed on average when processing this request. The valid format is a decimal (formatted to one decimal place).

Delay Percent Count The count of individual delays used for Delay Percent. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Interval (sec) The length (in seconds) of the interval. The valid format is a positive integer.

Longest Response (ms) The worst-case response time (in milliseconds) experienced by this request. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Occurrences The number of times this request was executing during the interval. The valid format is a positive integer.

Origin Node The name of the application server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Process ID The unique identifier of the JVM process (the class ID of the JVM). The valid format is a positive integer.

Request Detail The URI for servlet requests, or the method name for EJBs. The valid format is an alphanumeric string, with a maximum of 128 characters.

Request Name The URL for servlet requests, or the fully qualified class name for EJBs. The valid format is an alphanumeric string, with a maximum of 128 characters.

Request Type The type of transaction being run. Valid values are Servlet, EJB_Method, Custom, All_Workloads, Unknown, and Portlet.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Sampling Rate (%) The percentage of edge requests-such as servlets and JSPs-that were sampled for nested requests during the interval. The valid format is a positive integer.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Indicates that this row is a summary row of statistical totals for all rows.

Total Time (ms) The total CPU time (in milliseconds) consumed by this request. The valid format is a positive integer.
For more information, see:

39. Servlet Sessions attributes

The Servlet Sessions attribute group provides information about servlet sessions.
A session is a series of requests to a servlet, originating from the same user at the same browser. Applications running in a Web container use Sessions to monitor the actions of individual users. The attributes within this group are used to build the Sessions workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Average Concurrently Active Sessions The average number of concurrently active sessions during the sampling interval. A session is active if WebSphere application server is currently processing a request that uses the session. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Average Concurrently Live Sessions The average number of sessions cached in memory during the sampling interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Average Serializable Session Object Size (bytes) The average size (in bytes) of the serializable attributes of in-memory sessions. This number is at a session level only and includes only session objects that contain at least one serializable attribute object (a session can contain some attributes that are serializable and some that are not). This value is a measurement of the data at the end of the PMI sampling interval, not of the data in the entire sampling interval. The valid format is a positive integer.

Average Session Lifetime (ms) The average session lifetime (in milliseconds), calculated by subtracting the time the session was created from the time it was invalidated. The valid format is a decimal (formatted to three decimal places).

Session Lifetime Count The count of times that were averaged for Average Session Lifetime . The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Broken Session Affinities The number of HTTP session affinities that broke, not counting WebSphere application server intentional breaks of session affinity. This is the number of requests received for sessions that were last accessed from another web application and can indicate failover processing or a corrupted plug-in configuration. The valid format is a positive integer.

Broken Session Affinity Rate (per sec) The rate (per second) of the number of HTTP session affinities that break, not counting the WebSphere application server intentional breaks of session affinity, during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Cache Discard Rate (per sec) The rate (per second) at which session objects have been forced out of the cache during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Cache Discards The number of session objects that have been forced out of the cache. An LRU algorithm removes old entries to make room for new sessions and cache misses (this applies only to persistent sessions). The valid format is a positive integer.

Enterprise Application Name The name of the Enterprise application running the servlet. The valid format is an alphanumeric string, with a maximum of 256 characters.

External Read Size (bytes) The size (in bytes) of the session data read from the persistent store (applicable only to serialized, persistent sessions). The valid format is a decimal (formatted to three decimal places).

External Read Time (ms) The time (in milliseconds) taken to read the session data from the persistent store (applicable only to persistent sessions). For multirow sessions, the metrics are for the attributes; for single-row sessions, the metrics are for the whole session. When using a JMS persistent store, the user has the choice of whether to serialize the data being replicated; if the data are not serialized, this counter is not available. The valid format is a decimal (formatted to three decimal places).

External Write Size (bytes) The size (in bytes) of session data written to the persistent store (applicable only to serialized, persistent sessions). The valid format is a decimal (formatted to three decimal places).

External Write Time (ms) The time (in milliseconds) taken to write the session data from the persistent store (applicable only to serialized, persistent sessions). The valid format is a decimal (formatted to three decimal places).

Failed Session Request Rate (per sec) The rate (per second) that a request for a new session could not be handled because it would exceed the maximum session count for the sampling interval. The valid format is a decimal (formatted to three decimal places).

Failed Session Requests This attribute collects data from the NoRoomForNewSessionCount metric in the Servlet Sessions Counters PMI module. The number of times a request for a new session could not be handled because it would exceed the maximum session count; this applies only to a session in memory with AllowOverflow=false. The valid format is a positive integer.

Instrumentation Level The web instrumentation level for this web application. For WebSphere 5, the valid values are None, Low, Medium, High, and Maximum; for WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Max Serializable Session Object Size (bytes) The maximum size (in bytes) of the serializable attributes of in-memory sessions. This number is at a session level only and includes only session objects that contain at least one serializable attribute object (a session can contain some attributes that are serializable and some that are not). This value is a measurement of the data at the end of the PMI sampling interval, not of the data in the entire sampling interval. The valid format is a positive integer.

Min Serializable Session Object Size (bytes) The minimum size (in bytes) of the serializable attributes of in-memory sessions. This number is at a session level and includes only session objects that contain at least one serializable attribute object (a session can contain some attributes that are serializable and some that are not). This value is a measurement of the data at the end of the PMI sampling interval, not of the data in the entire sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Nonexistent Session Request Rate (per sec) The rate (per second) of requests for a session that no longer exists (presumably because the session timed out) during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Nonexistent Session Requests The number of requests for a session that no longer exists (presumably because the session timed out). Use this counter to determine if the timeout is too short. The valid format is a positive integer.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Session Creation Rate (per sec) The rate (per second) of sessions created during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Session Invalidation Rate (per sec) The rate (per second) at which sessions were invalidated during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Sessions Created The number of sessions created during the sampling interval. The valid format is a positive integer.

Sessions Invalidated The number of sessions invalidated during the sampling interval. The valid format is a positive integer.

Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.

Summary of Servlet Sessions Whether this row is a summary row of statistical totals collected for the servlet sessions. The valid values are No and Yes.

Time since Last Activated The time difference (in the locale-specific format, for example hh:mm:ss.msecs) between the previous and current access timestamps. Does not include session timeouts. The valid format is a timestamp.

Total Serializable Session Object Size (bytes) The total size (in bytes) of all the in-memory session objects. This includes only the serializable attributes in the session object; at least one such attribute must be present to be included in this total. This value is a measurement of the data at the end of the PMI sampling interval, not of the data in the entire sampling interval. The valid format is a positive integer.

Serializable Session Object Size Count The count of object sizes that were used for Total Serializable Session Object Size. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Web Application Archive The name of the web application WAR file. The valid format is an alphanumeric string, with a maximum of 128 characters.
For more information, see:

40. Servlets JSPs attributes

The Servlets JSPs attributes provide performance information for servlets and Java. server pages (JSPs).
Examples of Servlets JSPs attributes include the average number of concurrent requests for a servlet and the amount of time it takes for a servlet to complete a request. Use the Servlets JSPs attributes in situations to monitor performance and the usage of servlets and JSPs.
The attributes within this group are used to build the Servlets/JSPs - Selected Web Application workspace.

The attributes within this attribute group contain zeros for performance data if your site set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and then select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Average Concurrent Requests The average number of concurrent requests for the servlet or JSP during the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the monitoring agent.

Average Response Time (ms) The time (in milliseconds) it took the servlet to perform a task during the interval. The valid format is a decimal (formatted to three decimal places).

Response Time Count The count of times that were averaged for Average Response Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Enterprise Application Name The name of the Enterprise application. The valid format is an alphanumeric string, with a maximum of 128 characters.

Error Count The number of errors or exceptions that have occurred in the servlet during the interval. The valid format is a positive integer.

Error Rate (per sec) The servlet exceptions or errors (per second) since the previous sample. The valid format is a decimal (formatted to three decimal places).

Instrumentation Level The instrumentation level for this servlet. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Request Count The number of total requests for the servlet during the interval. The valid format is a positive integer.

Request Rate (per sec) The servlet requests (per second) since the previous sample. The valid format is a decimal (formatted to three decimal places).

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Virtual Host Name The name of the virtual host. The valid format is an alphanumeric string, with a maximum of 64 characters.

Servlet/JSP Name The name of the current servlet or JSP. The valid format is an alphanumeric string, with a maximum of 128 characters.

Date and Time the Servlet Was Loaded The date and time when the servlet was loaded.

JSP Path Name The name of the JSP path. The valid format is an alphanumeric string, with a maximum of 128 characters.

Total (ms) The total time (in milliseconds) used during the interval. The valid format is a decimal (formatted to three decimal places).

Type Whether this entry represents a servlet or Java server page (JSP). The valid values are Servlet and JSP.

Web Application Archive The name of the web application WAR file. The valid format is an alphanumeric string, with a maximum of 128 characters.

Set Instrumentation Level Type The WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection. Valid values are: ORBThreadPool, HTTPSession, DBPool, Servlet, Transaction, ObjectPool, EJB, EJBMethod, AllResources, JVMMemory, ThreadPool, WCThreadPool, WebApplicationSubModule, DynamicCache, J2CPool, ORB, WLM, ServletSessions.

41. Scheduler attributes

The Scheduler attributes display data for the Scheduler service.
The attributes within this group are used to build the Scheduler workspace.

Instrumentation Level The instrumentation level for the Scheduler. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Poll Count The number of polls which are collected on the intervals. The valid format is a positive integer.

Poll Duration The average alarms during the latency. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Poll Query Duration The duration of poll query. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Row Number The row number. The valid format is a positive integer.

Run Duration The run duration. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Scheduler Name The name of the scheduler. The valid format is an alphanumeric string, with a maximum of 256 characters.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Whether this row is a summary row of statistical totals for all rows. Valid values are No and Yes.

Task Collision Rate The rate of the task collision. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Task Delay Duration The duration of the task delay. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Task Expiration Rate The rate of the task expiration. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Task Failure Count The number of the failed tasks. The valid format is a positive integer.

Task Finish Count The number of the finished tasks which are collected on the intervals. The valid format is a positive integer.

Task Finish Rate The rate of the finished tasks. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Task Run Rate The rate of the run tasks. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.
For more information, see:

42. Service Component Elements attributes

The Service Component Elements attributes provide aggregated information about the performance data for all the service components and their elements.
The attributes within this group are used to build the Service Component Elements workspace.

The attributes within this attribute group contain zeros for performance data if your site set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and then select it again later. Each time you select the workspace, these attributes are updated with the latest data.
Attributes in this group are only provided for IBM WebSphere application server version 6.0 or later.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Average Response Time (ms) The average response time (in milliseconds) in the current interval. The valid format is a decimal (formatted to three decimal places).

Component The type of the component. The value format is an alphanumeric string, with a maximum of 256 characters.

Component Name The component name of the service. The value format is an alphanumeric string, with a maximum of 256 characters.

Element The type of the element. The valid format is a positive integer.

Element Name The name of the element. The value format is an alphanumeric string, with a maximum of 256 characters.

Error Rate (per sec) The computed error rate. The valid format is a decimal (formatted to three decimal places).

Failed Count The failed invocations. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the service component elements. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Request Count The number of requests during the interval. The valid format is a positive integer.

Request Rate (per sec) The rate of requests during the interval per second. The valid format is a decimal (formatted to three decimal places).

Row Number The row number. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Success Count The successful invocations. The valid format is a positive integer.

Summary Whether this row is a summary row of statistical totals for all rows. Valid values are No and Yes.

Total (ms) The total time used (in milliseconds) during the interval. The valid format is a decimal (formatted to three decimal places).
For more information, see:

43. Service Components attributes

The Service Components attributes provide aggregated information about the overview performance of the key service components.
The attributes within this group are used to build the Service Components workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling. Thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.
Attributes in this group are only provided for IBM WebSphere application server version 6.0 or later.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Count The bad request count. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the service components. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Name The type of the component. Valid values are Service_Component_Architecture, Business Rules, Map, Mediation, Business State Machine, and Selector.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Whether this row is a summary row of statistical totals for all rows. Valid values are No and Yes.

44. Thread Pools attributes

The Thread Pools attribute group provides information about the data source, as well as connection statistics, for database connection pools in a WebSphere application server. Use it to monitor pools activity and to spot potential throttling.
The attributes within this group are used to build the Pool Analysis and Thread Pools workspaces.

The attributes within this attribute group contain zeros for performance data if your site set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and then select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Application ID Indicates J2EE application ID.

Average Active Threads The average number of concurrently active threads during the sampling interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Average Free Threads The average number of free threads in the pool. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Average Pool Size The average number of threads in the pool. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.
This value might exceed Maximum Pool Size in certain configurations where the pool is enabled to grow beyond the specified maximum size.

Instrumentation Level The instrumentation level for the thread pools. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Maximum Pool Size The configured maximum number of threads allowed in the pool. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Percent of Time Pool at Max The average percentage of time that all threads were in use during the sampling interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Percent Used Bad The bad percent of pool usage by application. The valid format is a positive integer.

Percent Used Fair The fair percent of pool usage by application. The valid format is a positive integer.

Percent Used Good The good percent of pool usage by application. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.

Summary of Thread Pools Whether this row is a summary row of statistical totals collected for all thread pools. The valid values are No and Yes.

Thread Creation Rate (per sec) The rate (per second) at which threads were created during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Thread Destruction Rate (per sec) The rate (per second) at which threads were destroyed during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Thread Pool Name The name of the thread pool. The valid format is an alphanumeric string, with a maximum of 256 characters.

Threads Created The number of threads created during the sampling interval. The valid format is a positive integer.

Threads Destroyed The number of threads destroyed during the sampling interval. The valid format is a positive integer.
For more information, see:

45. Topic Spaces attributes

The Topic Spaces attributes provide aggregated information about publish/subscribe messaging.
The attributes within this group are used to build the Destinations workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.
Attributes in this group are only provided for IBM WebSphere application server version 6.0 or later.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Assured Persistent Local Subscription Hits The cumulative total of subscriptions which have matched assured persistent publications. The valid format is a positive integer.

Assured Persistent Messages Published The number of Assured Persistent messages published. The valid format is a positive integer.

Best Effort Non-persistent Local Subscription Hits The cumulative total of subscriptions which have matched best effort non-persistent publications. The valid format is a positive integer.

Best Effort Non-persistent Messages Published The number of best effort non-persistent messages published. The valid format is a positive integer.

Durable Local Subscription The number of durable subscriptions. The valid format is a positive integer.

Express Non-persistent Local Subscription Hits The cumulative total of subscriptions which have matched express non-persistent publications. The valid format is a positive integer.

Express Non-persistent Messages Published The number of express non-persistent messages published. The valid format is a positive integer.

Incomplete Publication The number of publications not yet received by all current subscribers. If this number is unexpected, view the publication using the admin console to take actions. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the topic spaces. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Local Oldest Publication The longest time any publication has spent on this topic space. If this time is not what was expected, view the message using the admin console to decide what action needs to be taken. The valid format is a positive integer.

Local Publisher The number of local publishers to topics in this topic space. The valid format is a positive integer.

Local Publisher Attaches The number of times an attachment has been made to this topic space by local producers. The lifetime of this value is the lifetime of the messaging engine. The valid format is a positive integer.

Messaging Engine Name The name of the message engine. The value format is an alphanumeric string, with a maximum of 256 characters.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Non-Durable Local Subscription The number of non-durable subscriptions. The valid format is a positive integer.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Reliable Non-persistent Local Subscription Hits The cumulative total of subscriptions which have matched reliable non-persistent publications. The valid format is a positive integer.

Reliable Non-persistent Messages Published The number of reliable non-persistent messages published. The valid format is a positive integer.

Reliable Persistent Local Subscription Hits The cumulative total of subscriptions which have matched reliable persistent publications. The valid format is a positive integer.

Reliable Persistent Messages Published The number of reliable persistent messages published. The valid format is a positive integer.

Report Enabled Publication Expired The number of report-enabled incomplete publications that expired while on this topic space. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Whether this row is a summary row of statistical totals for all rows. Valid values are No and Yes.

Topic Space Name The name of the topic space. The valid format is an alphanumeric string, with a maximum of 256 characters.

Total Local Subscription The number of local subscriptions to topics in this topic space. The valid format is a positive integer.

Total Local Subscription Hits The cumulative total of subscriptions which have matched topic space publications. The valid format is a positive integer.

Total Messages Published The total number of publications to this topic space. The valid format is a positive integer.
For more information, see:

46. Web Applications attributes

Use the Web Applications attributes to create situations that monitor web application performance and application server loads.
The Web Applications attributes provide aggregated information for each web application and for the application server running that application. These performance data describe all servlets and JSPs deployed to that web application as well as performance data for all servlets and JSPs running in the application server. Examples include the number of loaded servlets and JSPs and total requests. The attributes within this group are used to build the Web Applications workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Average Concurrent Requests The average number of concurrent requests for servlets and JSPs during the interval. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Average Response Time (ms) The average time (in milliseconds) required for a servlet to perform a task during the interval. Calculated by dividing the total responses by Request Count; if Request Count is zero, this value is set to blank. The valid format is a decimal (formatted to three decimal places).

Virtual Host Name The name of the virtual host. The valid format is an alphanumeric string, with a maximum of 64 characters.

Enterprise Application Name The name of the Enterprise application. The valid format is an alphanumeric string, with a maximum of 128 characters.

Error Count The number of errors or exceptions that have occurred in the servlet. The valid format is a positive integer.

Error Rate (per sec) The servlet exceptions or errors (per second) for the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Instrumentation Level The web instrumentation level for this web application. For WebSphere 5, the valid values are None, Low, Medium, High, and Maximum. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Request Count The number of total requests for the servlet during the interval. The valid format is a positive integer.

Request Rate (per sec) The servlet requests (per second) for the interval since the previous sample. The valid format is a decimal (formatted to three decimal places).

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Servlets Loaded The number of servlets loaded during the interval. The valid format is a positive integer.

Servlets Reloaded The number of servlets reloaded during the interval. The valid format a positive integer.

Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.

Subinstrumentation Level The subinstrumentation level for the web application servlet submodule. For WebSphere application server 5 the valid values are None, Low, Medium, High, and Maximum.
Note: Subinstrumentation Level is not supported in WebSphere application server 6.0 or higher. The Tivoli Enterprise Monitoring agent uses the Instrumentation Level instead.

Summary of All Applications Whether this row is a summary row of statistical totals for all web applications executed during the interval. The valid values are Yes and No.

Total (ms) The total time used during the interval. The valid format is a decimal (formatted to three decimal places).

Response Time Count The number of calls for which the response times are averaged in the Average Response Time field. The valid format is a 4-byte integer. The value -2 is used if the number is very large and can not be provided.

Web Application Archive The name of the web application WAR file. The valid format is an alphanumeric string, with a maximum of 128 characters.

47. Web Services attributes

The Web Services attributes display aggregated information about the web services, including the number of loaded web services, the number of requests delivered and processed, the request response time, and the average size of requests.
The attributes within this group are used to build the Web Services workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling. Thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Dispatched Requests The number of requests the service dispatched or delivered. The valid format is a positive integer.

Dispatch Response Time The average response time, in milliseconds, to dispatch a request. The valid format is a decimal (formatted to three decimal places).

Dispatch Response Time Count The count of times that were averaged for Dispatch Response Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Instrumentation Level The instrumentation level for the web services counters. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Payload Size The average payload size in bytes of a received request or reply. The valid format is a positive integer.

Payload Size Count The count of sizes that were averaged for Payload Size. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Processed Requests The number of requests the service successfully processed. Valid format is a positive integer.

Received Requests The number of requests the service received. The valid format is a positive integer.

Reply Payload Size The average payload size (in bytes) of a reply. The valid format is a positive integer.

Reply Payload Size Count The count of sizes that were averaged for Reply Payload Size. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Reply Response Time The average response time, in milliseconds, to prepare a reply after dispatch. The valid format is a decimal (formatted to three decimal places).

Reply Response Time Count The count of times that were averaged for Reply Response Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Request Payload Size The average payload size, in bytes, of a request. The valid format is a positive integer.

Request Payload Size Count The count of sizes that were averaged for Request Payload Size. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Request Response Time The average response time, in milliseconds, to prepare a request for dispatch. The valid format is a decimal (formatted to three decimal places).

Request Response Time Count The count of times that were averaged for Request Response Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Response Time The average response time (in milliseconds) for a successful request. The valid format is a decimal (formatted to three decimal places).

Response Time Count The count of times that were averaged for Response Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Whether this row is a summary row of statistical totals for all rows. Valid values are No and Yes.

Total Dispatch (ms) The total time (in milliseconds) the service dispatches requests. The valid format is a decimal (formatted to three decimal places).

Total Prepare (ms) The total time (in milliseconds) the service prepares requests. The valid format is a decimal (formatted to three decimal places).

Total Processing (ms) The total time (in milliseconds) the service processes requests. The valid format is a decimal (formatted to three decimal places).

Web Service The name of the web service. The valid format is an alphanumeric string, with a maximum of 256 characters.

48. Web Services Gate Way attributes

The Web Services Gate Way attributes display aggregated information about the Web Services Gateway, including synchronous requests, asynchronous requests, synchronous responses, and asynchronous responses.
The attributes within this group are used to build the Web Services workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Asynchronous Requests The number of asynchronous requests made. The valid format is a positive integer.

Asynchronous Responses The number of asynchronous responses made. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the Web Services Gateway counters. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Summary Whether this row is a summary row of statistical totals for all rows. Valid values are No and Yes.

Synchronous Requests The number of synchronous requests made. The valid format is a positive integer.

Synchronous Responses The number of synchronous responses made. The valid format is a positive integer.

Web Service The name of the web service. The valid format is an alphanumeric string, with a maximum of 256 characters.
For more information, see:

49. WebSphere Agent Events attributes

The WebSphere Agent Events attributes provide information about agent-level events that affect the ability of the monitoring agent to collect data about WebSphere application server. These attributes provide exception and error messages, their IDs, and their severities.
The attributes within this group are used to build the WebSphere Agent workspace.

Event Date and Time The date and time the event occurred. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Message Description The message description. The valid format is an alphanumeric string, with a maximum of 256 characters.

Message ID The message ID. The valid format is an alphanumeric string, with a maximum of eight characters.

Node Name The system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Sequence Number The sequence number of the message. The valid format is a positive integer.

Severity The severity of the event. Valid values are Info, Warning, Error, and Severe.

Function The valid format is an alphanumeric string, with a maximum of 32 characters.

File Name The name of the file. The valid format is an alphanumeric string, with a maximum of 8 characters.

Line Number The number of the line. The valid format is a 4-byte integer.

50. WMQ Client Link Communications attributes

The WMQ Client Link Communications attributes display aggregated information for all the clients of WMQ Queue Managers that are or have been connected to this application server.
The attributes within this group are used to build the WMQ Client Link Communications workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling. Thus the attributes within this attribute group initially contain zeros until you select the workspace and reselect it later. Each time you reselect the workspace, these attributes are updated with the latest data.
Attributes in this group are only provided for IBM WebSphere application server version 6.0 or later.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

API Calls Serviced The number of MQ API call requests serviced on behalf of WMQ JMS clients. The valid format is a positive integer.

Batches Sent The number of batches of messages sent to network attached WMQ JMS clients. The valid format is a positive integer.

Clients Attached The current number of WMQ JMS clients attached to this application server. The valid format is a positive integer.

Comms Errors The number of errors that have caused connections to WMQ JMS clients to be dropped. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the WMQ client link communications. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Messages Received The number of messages received from network attached WMQ JMS clients. The valid format is a positive integer.

Messages Sent The number of messages sent to network attached WMQ JMS clients. The valid format is a positive integer.

Messaging Engine Name The name of the message engine. The value format is an alphanumeric string, with a maximum of 256 characters.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Reads Blocked The number of read operations that could not be completed immediately. This number can be used as an indicator of network congestion when communicating with WMQ JMS clients. The valid format is a positive integer.

Received (bytes) The number of bytes of data received from network attached WMQ JMS clients. This includes bytes of message data as well as bytes of data used to control the flow of messages. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Sent (bytes) The number of bytes of data sent to network attached WMQ JMS clients. This includes bytes of message data as well as bytes of data used to control the flow of messages. The valid format is a positive integer.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Writes Blocked The number of write operations that could not be completed immediately. This number can be used as an indicator of network congestion when communicating with WMQ JMS clients. The valid format is a positive integer.

51. WMQ Link Communications attributes

The WMQ Link Communications attributes display aggregated information for all the WMQ Queue Managers that are or have been connected to this application server.
The attributes within this group are used to build the WMQ Link Communications workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling. Thus the attributes within this attribute group initially contain zeros until you select the workspace and then select it again later. Each time you select the workspace, these attributes are updated with the latest data.
Attributes in this group are only provided for IBM WebSphere application server version 6.0 or later.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Batches Received The number of batches of messages received from network attached WMQ Queue Managers. The valid format is a positive integer.

Batches Sent The number of batches of messages sent to network attached WMQ Queue Managers. The valid format is a positive integer.

Comms Errors The number of communication errors that resulted in a network connection to a WMQ Queue Manager being disconnected. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the WMQ link communications. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Long Retries The number of long retries. This indicates the number of times channels were disconnected and could not be re-established for longer periods of time. The valid format is a positive integer.

Messages Received The number of messages received from network attached WMQ Queue Managers. The valid format is a positive integer.

Messages Sent The number of messages sent to network attached WMQ Queue Managers. The valid format is a positive integer.

Messaging Engine Name The name of the message engine. The value format is an alphanumeric string, with a maximum of 256 characters.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

QM Attached The total number of WMQ Queue Managers currently network attached to this application server. The valid format is a positive integer.

Reads Blocked The number of read operations that could not be completed immediately. This number can be used as an indicator of network congestion when communicating with WMQ Queue Managers. The valid format is a positive integer.

Receiver Received (bytes) The number of bytes of data received by receiver channels from network attached WMQ Queue Managers. The valid format is a positive integer.

Receiver Sent (bytes) The number of bytes data sent by receiver channels to network attached WMQ Queue Managers. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Sender Received (bytes) The number of bytes of data received by sender channels from network attached WMQ Queue Managers. The valid format is a positive integer.

Sender Sent (bytes) The number of bytes of data sent by sender channels to network attached WMQ Queue Managers. The valid format is a positive integer.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Short Retries The number of short retries. This indicates the number of times channels were disconnected and could not be re-established for short periods of time. The valid format is a positive integer.

Writes Blocked The number of write operations that could not be completed immediately. This number can be used as an indicator of network congestion when communicating with WMQ Queue Managers. The valid format is a positive integer.
For more information, see:

52. Workload Management Client attributes

The Workload Management Client attribute group provides information about the client that initiates workload requests.
Workload management (WLM) optimizes the distribution of client processing tasks. Incoming work requests are distributed to the application servers, enterprise beans, servlets, and other objects that can most effectively process their requests. Workload management also provides failover when servers are not available, improving application availability. In a WebSphere application server environment, you implement workload management by using clusters, transports, and replication domains.
The attributes within this group are used to build the Workload Management workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling. Thus the attributes within this attribute group initially contain zeros until you select the workspace and then select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Client Cluster Update Rate (per sec) The rate (per second) at which times this client has received new server cluster information during the sampling interval. Use this metric to determine how often cluster information is being propagated. The valid format is a decimal (formatted to three decimal places).

Client Cluster Updates The number of times initial or updated server cluster data is sent to a WLM-enabled client from a server cluster member. Use this metric to determine how often cluster information is being propagated. The valid format is a positive integer.

Client Response Time (ms) The response time (in milliseconds) for IIOP requests sent by a client. This response time is calculated based on the time the client sends the request to the time the server sends the reply. The valid format is a decimal (formatted to three decimal places).

Client Response Time Count The count of times that were used for Client Response Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Instrumentation Level The instrumentation level for the WLM client. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Outgoing Request Rate (per sec) The rate (per second) at which outgoing IIOP requests were being sent from this client to an application server during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Outgoing Requests The number of outgoing IIOP requests being sent from this client to an application server. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.

Total Client Response (ms) The total response time (in milliseconds) for IIOP requests sent by a client. The valid format is a decimal (formatted to three decimal places).
For more information, see:

53. Workload Management Server attributes

The Workload Management Server attribute group provides information about the workload management server.
Workload management (WLM) optimizes the distribution of client processing tasks. Incoming work requests are distributed to the application servers, enterprise beans, servlets, and other objects that can most effectively process those requests. Workload management also provides failover when servers are not available, improving application availability. In a WebSphere application server environment, you implement workload management by using clusters, transports, and replication domains.
The attributes within this group are used to build the Workload Management workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling. Thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Concurrent Requests The number of remote IIOP requests being processed by this server. The valid format is a decimal (formatted to three decimal places). This value is an average of several values collected over an interval. The interval can be either between this time and the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the configuration of the Monitoring Agent.

Incoming Non-WLM Object Request Rate (per sec) The rate (per second) of incoming IIOP requests from an application running on a non-WLM client during the sampling interval. This type of client either does not have the WLM runtime present, or the client object reference was flagged not to participate in workload management. The valid format is a decimal (formatted to three decimal places).

Incoming Non-WLM Object Requests The number of incoming IIOP requests to an application from a client that does not have the WLM runtime present or whose object reference was flagged not to participate in workload management. The valid format is a positive integer.

Incoming Nonaffinity Request Rate (per sec) The rate (per second) of incoming IIOP requests to an application server based on no affinity during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Incoming Nonaffinity Requests The number of incoming IIOP requests to an application server based on no affinity. This request was sent to this server based on workload management selection policies that were decided in the client WLM run time. The valid format is a positive integer.

Incoming Request Rate (per sec) The rate (per second) of incoming IIOP requests to an application server during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Incoming Requests The number of incoming IIOP requests to an application server during the sampling interval. The valid format is a positive integer.

Incoming Strong Affinity Request Rate (per sec) The rate (per second) of incoming IIOP requests to an application server based on a strong affinity during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Incoming Strong Affinity Requests The number of incoming IIOP requests to an application server based on a strong affinity. A strong affinity request is one that must be serviced by this application server because of a dependency that resides on the server. This request could not successfully be serviced by another member of the server cluster. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the WLM server. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Cluster Update Rate (per sec) The rate (per second) at which this server received new server cluster information during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Server Cluster Updates The number of times initial or updated server cluster data are sent to a server member from the deployment manager. This metric determines how often cluster information is being propagated. The valid format is a positive integer.

Server Name The name of the WebSphere application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Server Response Time (ms) The response time (in milliseconds) at which IIOP requests were serviced by an application server, calculated based on the time the request is received versus the time the reply is sent. The valid format is a decimal (formatted to three decimal places).

Server Response Time Count The count of times that were used for Server Response Time. The valid format is a 4-byte integer. If the number is too big to be stored, a value of -2 is used.

Total Server Response (ms) The total response time (in milliseconds) at which IIOP requests were serviced by an application server. The valid format is a decimal (formatted to three decimal places).

Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.

WLM Clients Serviced The number of WLM-enabled clients this application server has serviced during the interval. The valid format is a positive integer.

WLM Clients Serviced Rate (per sec) The rate (per second) at which this server has serviced WLM-enabled clients during the sampling interval. The valid format is a decimal (formatted to three decimal places).

WLM Server Weight A control for work directed to the application server. If the server weight value is greater than the weight values assigned to other servers in the cluster, then the server receives a larger share of the cluster workload. The valid format is a positive integer.
For more information, see:

54. Workplace Mail IMAP/POP attributes

The Workplace Mail IMAP/POP attributes displays the usage information for the IMAP service and POP3 service connectivity.
The attributes within this group are used to build the IMAP/POP workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling. Thus the attributes within this attribute group initially contain zeros until you select the workspace and then select it again later. Each time you select the workspace, these attributes are updated with the latest data.

This workspace does not support linking to ITCAM for Application Diagnostics Managing Server visualization engine.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Active Sessions The number of active sessions during the sampling interval. The valid format is a positive integer.

Active SSL Sessions The number of active, secure sessions during the sampling interval. The valid format is a positive integer.

Authentication Failures The number of authentications failures during the sampling interval. The valid format is a positive integer.

Connection (ms) The time (in milliseconds) spent connected to clients during the sampling interval. The valid format is a positive integer.

IMAP Instrumentation Level The instrumentation level for IMAP PMI module. Valid values are None, Low, Medium, High, Basic, Extended, All, Custom, and Maximum. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Peak Session load The maximum number of concurrent sessions during the sampling interval. The valid format is a positive integer.

POP Instrumentation Level The instrumentation level for POP PMI module. Valid values are None, Low, Medium, High, Basic, Extended, All, Custom, and Maximum. Blank if no instrumentation level is set.

Protocol The protocol type of the workplace mail. Valid values are IMAP and POP.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Successful Authentications The number of successful authentications during the sampling interval. The valid format is a positive integer.

Instrumentation Level The Instrumentation Level for this container. Valid fixed values None, Low, Medium, High, Basic, Extended, All, Custom, Maximum.
For more information, see:

55. Workplace Mail Queues attributes

The Workplace Mail Queues attributes display information about the message delivery state, including ready, retry, unprocessed, and dead.
The attributes within this group are used to build the Messages Queues workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling. Thus the attributes within this attribute group initially contain zeros until you select the workspace and select again it later. Each time you select the workspace, these attributes are updated with the latest data.

This workspace does not support linking to ITCAM for Application Diagnostics Managing Server visualization engine.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Dead The number of messages in the dead state in the queue during the sampling interval. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the service components. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Queue The Lotus Workplace Mail queue name. Valid values are A, B, C, D, E, F, G, H, and Summary.

Ready The number of messages in the ready state in the queue during the sampling interval. The valid format is a positive integer.

Retry The number of messages in the retry state in the queue during the sampling interval. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Unprocessed The number of messages in the unprocessed state in the queue during the sampling interval. The valid format is a positive integer.

56. Workplace Mail Service attributes

The Workplace Mail Service attributes display aggregated usage information about the incoming mail message traffic.
The attributes within this group are used to build the Workplace Mail workspace.

The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
The monitoring agent is set by default to provide on-demand sampling. Thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.

This workspace does not support linking to ITCAM for Application Diagnostics Managing Server visualization engine.

For information about WebSphere PMI metrics, see WebSphere PMI Attribute Mapping.

Active LDAP Connections The number of active LDAP connections during the sampling interval. The valid format is a positive integer.

Delivered Messages The total number of delivered messages during the sampling interval. The valid format is a positive integer.

Deliverer Dropped Messages The total number of messages rejected by the SMTP outbound server during the sampling interval. The valid format is a positive integer.

Deliverer Message (ms) The total time in milliseconds taken by SMTP outbound server to process messages during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Dropped SMTP Connections The total number of the dropped SMTP connections during the sampling interval. The valid format is a positive integer.

DSN Failure Messages The total number of failure DSNs sent during the sampling interval. The valid format is a positive integer.

Handled Messages The total number of messages processed by the mail handler server during the sampling interval. The valid format is a positive integer.

Handler Dropped Messages The total number of messages rejected by the mail handler server during the sampling interval. The valid format is a positive integer.

Instrumentation Level The instrumentation level for the service components. For WebSphere 6 or higher, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Live SMTP Server Connections The number of live SMTP server connections during the sampling interval. The valid format is a positive integer.

Live SMTP Client Connections The number of live SMTP client connections during the sampling interval. The valid format is a positive integer.

Lost SMTP Client Connections The total number of lost SMTP client connections during the sampling interval. The valid format is a positive integer.

Lost SMTP Connections The total number of the lost SMTP connections during the sampling interval. The valid format is a positive integer.

Message Delivery (ms) The total time in milliseconds taken to deliver messages during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Messages Handling (ms) The total time in milliseconds taken to handle messages during the sampling interval. The valid format is a decimal (formatted to three decimal places).

Node Name The name of the system on which the server is running. The value format is an alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Peak LDAP Connections The maximum number of concurrent LDAP connections during the sampling interval. The valid format is a positive integer.

Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

Format of the 12-character timestamp

Character String Meaning
MM Month
DD Day
YY Year
HH Hour
MM Minute
SS Second

Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.

Server Name The name of the application server. The valid format is an alphanumeric string, with a maximum of 256 characters.

Smarthost Messages The total number of messages sent to the Smarthost during the sampling interval. The valid format is a positive integer.

SMTP Client Connections The total number of SMTP client connections during the sampling interval. The valid format is a positive integer.

SMTP Client (ms) The total time in milliseconds taken to deliver messages during the sampling interval. The valid format is a decimal (formatted to three decimal places).

SMTP Connections The total number of connections to the SMTP server during the sampling interval. The valid format is a positive integer.

SMTP (ms) The total time in milliseconds that SMTP has conversed during the sampling interval. The valid format is a decimal (formatted to three decimal places).

SMTP Server Threads The number of active SMTP outbound server threads during the sampling interval. The valid format is a positive integer.
For more information, see:

57. Agent Configuration attributes

The attributes in the Agent Configuration table are for internal use only.

Origin Node The server name subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Row Id The row identifier. The valid format is a 2-byte integer.

View Id The view identifier. The valid format is a 2-byte integer.

Act Id The act identifier. The valid format is a 2-byte integer.

Data The data string. The valid format is an alphanumeric string, with a maximum of 4096 characters.

58. KYN Command attributes

The attributes in the KYN command table are for internal use only.

Origin Node The origin node. The valid format is an alphanumeric string, with a maximum of 128 characters.

Command The command string. The valid format is an alphanumeric string, with a maximum of 256 characters.

User ID The user ID. The valid format is an alphanumeric string, with a maximum of 16 characters.

Result Status The result status code. The valid format is a 4-byte integer.

59. Server Configuration attributes

The attributes in the Server Configuration table are for internal use only.

Origin Node The server name subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.

Row Id The row identifier. The valid format is a 2-byte integer.

View Id The view identifier. The valid format is a 2-byte integer.

Act Id The act identifier. The valid format is a 2-byte integer.

Data The data string. The valid format is an alphanumeric string, with a maximum of 4096 characters.

Situations

Contents

1. Predefined situations-descriptions and formulas (that run automatically)
2. Predefined situations descriptions and formulas (that run manually)

Situations

The monitoring agent for WebSphere Application Server has a number of predefined situations that you can use to complete the following tasks:

Monitor your WebSphere Application Server servers.
Monitor and manage widely dispersed WebSphere Application Server resources through localized automation.
Create your own situations using the predefined situations as examples.

These predefined situations display an alert status. When these situations trigger an alert, you can investigate the event by opening its workspace. For example, you can use these situations to monitor a WebSphere Application Server for errors occurring within it or web applications based at your site.

How the situations work

Situations are tests expressed in IF-TRUE format of system conditions to monitor; the tested value is a monitoring agent for WebSphere Application Server attribute expressed in the form attribute-group.attribute-name. If the specified condition occurs or exists, the situation is true, and an alert is issued.

Avoid using negative values

If you define situations that use a counter or a range of numbers, always provide a threshold or use values in a positive range of numbers. For example, use a greater-than-or-equal-to-zero expression as shown in some of the following predefined situations. This practice prevents a situation from falsely tripping. If the monitoring agent for WebSphere Application Server encounters an undefined attribute value, it interprets this value as a negative number and erroneously fires a situation that specifies a negative number.
For the following situations:WASDBConPAvgWaitTimeHigh DB_Connection_Pools,J2C_Connection_Pools and Thread_PoolsApplication the Application ID column is not supported and always displays -1 by default.

Access the situations

Some of the predefined situations run by default from the WebSphere Agent. For the situations that do not run automatically, you must start these situations manually. To start these situations, access the situations in the monitoring portal using one of the following methods:

In the WebSphere agent, right-click the specific server. Right-click Enterprise then, click Manage Situations to display all the managed situations available on the server. If you want to start, stop, edit, or model a situation, right-click the situation and select the option you want.
From the toolbar on the main menu, click the Situation Editor icon and scroll to the situation to view.

For information about predefined situations and formulas see >Predefined situations-descriptions and formulas (that run automatically) and situations descriptions and formulas (that run manually). See also Attributes.

Predefined situations-descriptions and formulas (that run automatically)

The following predefined situations run automatically from the WebSphere Agent and support the following applications servers unless stated otherwise.

WebSphere application server
WebSphere application server portal
WebSphere application server Process
WebSphere application server ESB
Lotus Workplace server

WASAppDiscovered monitors WebSphere applications deployed in the application server and issues an Informational alert when a new application is discovered. The monitoring agent checks for new applications each time it connects to the data collector or when an application is deployed when the data collector is already active. The formula is:
If
Application_Monitoring_Configuration.Monitoring_Status equals Discovered
then
the situation WASAppDiscovered is true.
This situation does not support Lotus Workplace server.
Predefined Take Action command Start_Baselining associated with the WASAppDiscovered situation enables you to automate the baselining of newly discovered applications.

WASAppHealthBad monitors the overall application health and issues a Critical alert when the application health is bad. The formula is:
If
Application_Health_Status.Web_Tier_Health equals Bad
then
the situation WASAppHealthBad is true.
Predefined Take Action command Set_Appliction_Monitoring associated with WASAppHealthBad situation increases the request monitoring rate for applications generated alert. This command enables you to collect more detailed performance data and helps to collect the most precise data about each application tier health level.

WASAppHealthFair monitors the overall application health and issues a warning alert when application health is fair. The formula is:
If
Application_Health_Status.Application_Health equals Fair
then
the situation WASAppHealthFair is true.
Predefined Take Action command Set_Appliction_Monitoring associated with WASAppHealthFair situation raises the request monitoring level for applications generated alert. This command enables you to collect detailed performance data that helps to pinpoint a bottleneck down to particular application tiers.

WASAppHealthGood monitors the overall application health and issues an Informational alert when application health is good. The formula is:
If
Application_Health_Status.Application_Health equals Good
then
the situation WASAppHealthGood is true.
Predefined Take Action command Set_Appliction_Monitoring associated with the WASAppHealthGood situation lowers the request monitoring level for applications generated alert, and reduces the monitoring workload.

WASError monitors the error severity for a single WebSphere application server and issues a Critical condition whenever that severity is greater than 21. Its formula is:
If
Log_Analysis.Severity is greater than Warning
then
the situation WASError is true.

WASHighCPUPercentUsed monitors the percentage of the CPU being consumed and issues a Critical condition whenever that time exceeds 80%. The formula is:
If
Application_Server.CPU_Used_Percent is greater than 80
then
the situation WASHighCPUPercentUsed is true.

WASHighGCTimePercent monitors the percentage of time being spent by the garage collector and issues a Critical condition whenever that time exceeds 80%. The formula is:
If
Garbage_Collection_Analysis.Real_Time_Percent is greater than 80
then
the situation WASHighGCTimePercent is true.

WASHighResponseTime monitors the average request response time and issues a Critical condition whenever that time exceeds 2 seconds. The formula is:
If
Request_Times_and_Rates.Average_Request_Response_Time is greater than 2000
then
the situation WASHighResponseTime is true.

WASNotConnected monitors the connection between the ITCAM for Data Collector WebSphere running in an application server and the monitoring agent for WebSphere Application Server monitoring agent to ensure that the monitoring agent is connected and issues a Critical condition whenever it is not. Its formula is:
If
Application_Server_Status.Status equals Disconnected
then
the situation WASNotConnected is true.

WASOutofHeapSpace monitors the heap allocation status and issues a Critical condition whenever heap space is exhausted. The formula is:
If
Allocation_Failure.Heap_Status equals Out of heap space or Insufficient space
then
the situation WASOutofHeapSpace is true.
This situation is not available when monitoring non-IBM Java. Virtual Machines, including machines commonly used on HP-UX and Solaris platforms.

WASAvgHeapSizeAfterGCHigh monitors the average heap size free percentage after garbage collection. This situation issues a Critical alert if the average heap size free percentage after garbage collection is greater than 80%. Its formula is:
If
Garbage_Collection_Cycle.Heap_Free_Percent_after_GC is greater than 80
then
the situation WASAvgHeapSizeAfterGCHigh is true.
This situation does not support Lotus Workplace server.

WASJ2CConnectionPoolUsageMaxed monitors the J2C pool percentage usage and issues a Warning alert if the pool usage is greater than or equal to 100%. Its formula is:
If
J2C_Connection_Pools.Pool_Used_Percent is greater than or equal to 100%
then
the situation WASJ2CConnectionPoolUsageMaxed is true.
This situation does not support Lotus Workplace server.

WASDBConnectionPoolUsageMaxed monitors the JDBC pool usage and issues a Critical alert if the pool usage is greater than or equal to 100%. Its formula is:
If
DB_Connection_Pools.Percent_Used is greater than or equal to 100%
then
the situation WASDBConnectionPoolUsageMaxed is true.
This situation does not support Lotus Workplace server.

WASHungThreadsDetected monitors hung threads and issues a Critical alert if any thread is hung. Its formula is:
If
Application_Server.Hung_Threads_Total is greater than 0
then
the situation WASHungThreadsDetected is true.

WASListenerPortStarted monitors starting of the WAS listener port. Its formula is:
If
Listener_Port.Status equals Started
then
the situation WASListenerPortStarted is true.

WASListenerPortStopped monitors stopping of the WAS listener port and issues a Critical alert if the port is stopped. Its formula is:
If
Listener_Port.Status equals Stopped
then
the situation WASListenerPortStopped is true.
See also Attributes.

Predefined situations descriptions and formulas (that run manually)

Situations that are run manually

The following situations do not run automatically. To run them you must access them from the Manage Situations view. These situations support the following application servers unless stated otherwise:

WebSphere application server
WebSphere application server portal
WebSphere application server Process
WebSphere application server ESB
Lotus Workplace server

To start, stop, or edit any of these situations, see Access the situations.
For information about situations that run automatically, see >Predefined situations-descriptions and formulas (that run automatically).

WASDBConnectionPoolThrdTimeout monitors the thread timeout count. This situation issues a Critical condition whenever the timeout count is greater than zero. Its formula is:
If
DB_Connection_Pools.Threads_Timed_Out is greater than 0
then
the situation WASDBConnectionPoolThreadTimeout is true.

WASContainerTransactionRollback monitors the rollback count of the WebSphere application server. This situation issues a Critical alert whenever the count becomes nonzero. Its formula is:
If
Container_Transactions.Global_Transactions_Rolled_Back is greater than 0
or
Container_Transactions.Local_Transactions_Rolled_Back is greater than 0
then
the situation WASContainerTransactionRollBack is true.

WASEJBCreateTimeHigh monitors the average time of a bean create call and issues a Critical alert when the time is longer than 2 seconds. Its formula is:
If
Enterprise_Java_Beans.Create_Average_Time is greater than 2000
then
the situation WASEJBCreateTimeHigh is true.
This situation does not support Lotus Workplace server.

WASEJBRemoveTimeHigh monitors the average time of a bean remove call and issues a Critical alert when the time is longer than 2 seconds. Its formula is:
If
Enterprise_Java_Beans.Remove_Average_Time is greater than 2000
then
the situation WASEJBRemoveTimeHigh is true.
This situation does not support Lotus Workplace server.

WASEJBMethodResponseTimeHigh monitors the average response time on remote interface methods for all beans. This situation issues a Critical alert if the response time is longer than 2 seconds. Its formula is:
If
Enterprise_Java_Beans.Method_Average_Response_Time is greater than 2000
then
the situation WASEJBMethodResponseTimeHigh is true.
This situation does not support Lotus Workplace server.

WASThreadFreeLow monitors the average free threads in the pool and issues a Critical alert if the number of threads is less than 200. Its formula is:
If
Thread_Pools.Average_Free_Threads is greater than or equal to 0
and
Thread_Pools.Average_Free_Threads is less than 200
and
Thread_Pools.Average_Active_Threads is greater than or equal to 0
then
the situation WASThreadFreeLow is true.
This situation does not support Lotus Workplace server.

WASDataSrcConWaitTimeHigh monitors the average time an application has to wait for a connection. This situation issues a Critical alert if the wait time is longer than 2 seconds. Its formula is:
If
Datasources_Connection_Average_Wait_Time is greater than 2000
then
the situation WASDataSrcConWaitTimeHigh is true.
This situation does not support Lotus Workplace server.

WASReqSQLExecuteTimePercentHigh monitors the percentage of time the request spends executing a JDBC database. This situation issues a Critical alert if the percentage of time is higher than 80%. Its formula is:
If
Request_Analysis.SQL_Execute_Time_Percent is greater than 80
then
the situation WASReqSQLExecuteTimePercentHigh is true.
This situation does not support Lotus Workplace server.

WASReqSQLQueryTimePercentHigh monitors the percentage of time the request spends querying a JDBC database. This situation issues a Critical Alert if the percentage of time is higher than 80%. Its formula is:
If
Request_Analysis.SQL_Query_Time_Percent is greater than 80
then
the situation WASReqSQLQueryTimePercentHigh is true.
This situation does not support Lotus Workplace server.

WASReqSQLUpdateTimePercentHigh monitors the percentage of time the request spends updating a JDBC database. This situation issues a Critical Alert if the percentage of time is higher than 80%. Its formula is:
If
Request_Analysis.SQL_Update_Time_Percent is greater than 80
then
the situation WASReqSQLUpdateTimePercentHigh is true.
This situation does not support Lotus Workplace server.

WASDBConPAverageUsageTimeHigh monitors the average time that a connection in use is high. This situation issues a Critical alert if the average time the connection in use is longer than 2 seconds. Its formula is:
If
DB_Connection_Pools.Average_Usage_Time is greater than 2000
then
the situation WASDBConPAverageTimeHigh is true.
This situation does not support Lotus Workplace server.
If
DB_Connection_Pools.Percent_Used is greater than 80
then
the situation WASDBConPPercentUsedTimeHigh is true.
This situation does not support Lotus Workplace server.

WASDBConPAvgWaitTimeHigh monitors the average time that a client has to wait for a connection. This situation issues a Critical alert when the time period is longer than 2 seconds. Its formula is:
If
DB_Connection_Pools.Average_Wait_Time is greater than 2000
then
the situation WASDBConPAvgWaitTimeHigh is true.
This situation does not support Lotus Workplace server.

WASJ2CCPAverageUsageTimeHigh monitors the average time that connections are in use (it measures from when the connection is allocated to when it is returned). This situation issues a Critical alert when the combined connection allocation and return time are longer than 2 seconds. Its formula is:
If
J2C_Connection_Pools.Average_Usage_Time is greater than 2000
then
the situation WASJ2CCPAverageUsageTimeHigh is true.
This situation does not support Lotus Workplace server.

WASJ2CCPAvgWaitTimeHigh monitors the average wait time until a connection is granted. This situation issues a Critical alert if the time period is longer than 2 seconds. Its formula is:
If
J2C_Connection_Pools.Average_Wait_Time is greater than 2000
then
the situation WASJ2CCPAvgWaitTimeHigh is true.
This situation does not support Lotus Workplace server.

WASCTGlbTransDurationHigh monitors the average duration of global transactions. This situation issues a Critical alert if the time period is longer than 2 seconds. Its formula is:
If
Container_Transactions.Global_Transaction_Duration is greater than 2000
then
the situation WASCTGlbTransDurationHigh is true.
This situation does not support Lotus Workplace server.

WASCTLclTransDurationHigh monitors the average duration of local transactions. This situation issues a Critical alert if the time period is longer than 2 seconds. Its formula is:
If
Container_Transactions.Local_Transaction_Duration is greater than 2000
then
the situation WASCTLclTransDurationHigh is true.
This situation does not support Lotus Workplace server.

WASPortalPageResponseTime monitors the portal page response time and issues a Critical alert when the average request response time is higher than 2 seconds. The formula is:
If
Portal_Page_Summary.Average_Response_Time is greater than 2000
then
the situation WASPortalPageResponseTime is true.

WASPortletResponseTime monitors the portlet response time and issues a Critical alert when the average request response time is higher than 2 seconds. The formula is:
If
Portlet_Summary.Average_Response_Time is greater than 2000
then
the situation WASPortletResponseTime is true.

WASServletsJSPsError monitors the error count for servlets and JSPs invoked by a WebSphere application server application. This situation issues a Critical condition whenever the count becomes nonzero. Its formula is:
If
Servlets_JSPs.Error_Count is greater than 0
then
the situation WASServletsJSPsError is true.
This situation does not support Lotus Workplace Server.

WASSrvlSessAvgActiveSessionHigh monitors the average number of concurrently active sessions. This situation issues a Critical alert if the average number of concurrently active sessions is greater than 100. Its formula is:
If
Servlet_Sessions.Average_Concurrently_Active_Sessions is greater than 100
then
the situation WASSrvlSessAvgActiveSessionHigh is true.
The following situations are configured to run automatically.
This situation does not support Lotus Workplace server.

WASSrvlSessExtReadTimeHigh monitors the time it takes to read the session data from the persistent store. This situation issues a Critical alert if the time period is longer than 2 seconds. Its formula is:
If
Servlet_Sessions.External_Read_Time is greater than 2000
then
the situation WASSrvlSessExtReadTimeHigh is true.
This situation does not support Lotus Workplace server.

WASSrvlSessExtWriteTimeHigh monitors the time it takes to write session data to persistent store. This situation issues a Critical alert if the time period is longer than 2 seconds. Its formula is:
If
Servlet_Sessions.External_Write_Time is greater than 2000
then
the situation WASSrvlSessExtReadTimeHigh is true.
This situation does not support Lotus Workplace server.

WASThreadPoolPercentMaxed monitors the average usage time of all threads, and issues a Critical condition whenever that time exceeds 100%. The formula is:
If
Thread_Pools.Percent_of_Time_Pool_at_Max is greater than 100
then
the situation WASThreadPoolPercentMaxed is true.

WASWebApplicationError monitors the error log status of the WebSphere server and issues a Critical condition when an error occurs. Its formula is:
If
Web_Applications.Error_Count is greater than 0
then
the situation WASWebApplicationError is true.
This situation does not support Lotus Workplace Server.
See also Attributes.
18. Update_Baseline: trigger a baseline update
19. Threshold calculation detail

Take Action commands

The Take Action feature lets your interactive monitoring portal users enter a command or stop or start a process at any system in your network where one or more monitoring agents are installed. The monitoring agent for WebSphere Application Server Take Action commands enable you use the monitoring portal interface to start, stop, or recycle a WebSphere Application Server or to control the level of monitoring for the current server.
Users can start a Take Action command from a workspace, from the Navigator, from a situation that you create, on demand, or by recalling a saved Take Action command.
Note:
The following take action commands are for internal use only and are not for use in the monitoring portal. The configuration workspaces use these take action commands to communicate internally with the monitoring agent.

Configure
ConfigureCancel
ConfigurePing

Add_XD_Cell: Add an XD Cell to a WebSphere agent

Use the Add_XD_Cell command to add an XD cell to the WebSphere Agent. This take action task is used to configure XD Cell monitoring.

Command syntax

YN:AddXDCell cellName
where cellName is the name of the XD cell.

Enable_Auto_Threshold: set threshold parameters

Use the Enable_Auto_Threshold Take Action to set automatic threshold parameters and remove any overrides of the thresholds.

The baselining process supplies statistical information about request response times. ITCAM interprets this information to set automatic thresholds. Several parameters control this interpretation.
The default values for these parameters are sufficient for most cases. However, if the thresholds are not adequate and the baselining process was run recently, you might have to change these parameters. If there are many false alarms or warnings, you must raise the bad or fair threshold; if alarms or warnings are not triggered when needed, you must lower the bad or fair threshold.
Although you can change the parameters for the entire application or for all requests of a given type, most likely you do this only for an individual request.

To set threshold parameters for all requests in the application, select this application in the Application Health workspace or Application Registry workspace, and select the Enable_Auto_Threshold take action command.
To set threshold parameters for all requests of a given type in the application, select this request type in the Application Request Configuration table of the Application Configuration workspace, and select the Enable_Auto_Threshold take action command.
To set threshold parameters for an individual request, select this request in the Request Baseline workspace, and select the Enable_Auto_Threshold take action command.

In the Request Baseline workspace, when you select a line representing a request, you can see the bar charts representing statistical data for this request. This data was gathered during the baselining process. Colors on the bar charts show the way in which the parameters are applied. You can change the parameters using the Enable_Auto_Threshold take action command, and immediately see the effects on the bar charts.

The Response Times Distribution chart shows the statistical distribution of response times for this request. The height of every bar shows the percentage of requests that had the indicated response time during the baselining period.
Some bars represent bigger time intervals than others; more bars are devoted to most common response times. For example, if the maximum encountered time is 1000 ms but most response times are 300 - 500 ms, then the first bar can be 0 - 50 ms, but there can also be bars of 305 - 310 ms and 400 - 402 ms.
The bars colored blue show the zone into which the "typical" response times for this application fall. The green bars show response times that are not "typical", but are below the fair threshold. Response times above the fair threshold but below the bad threshold are shown as yellow bars; for those above the bad threshold, the bars are red.
Use the Enable_Auto_Threshold take action command to set the parameters that affect both the position of the "typical" zone and the way the thresholds are derived from this zone.
For more information about how the bar chart and parameters work, see Threshold calculation detail.
The Level2 Delays Distribution chart shows the distribution of time spent in "nested requests" within the requests that had this response time range. Each bar represents a response time of the top-level request . Within this bar, colored sections show how much time is spent within nested requests of different types; the color legend is shown on the bar. ITCAM uses this distribution within the selection zone (that is for typical overall request types) to work out the average share of time that each nested request type takes. When an error or warning arises, ITCAM checks which of the request types takes more than its usual share of time; based on this, it displays whether the likely cause is the application, backend, or server.

Command syntax

YN:Enable_Auto_Threshold App_Id Request_Id Auto_Threshold_Percent Auto_Threshold_Deviation Auto_Threshold_Fair_Projection Auto_Threshold_Bad_Projection Use_Default
Parameters:
App_Id

The application ID, automatically assigned in the portal from the selection context when Take Action was invoked.

Request_Id

The request ID, automatically assigned in the portal from the selection context when Take Action was invoked.

Auto_Threshold_Percent

Auto_Threshold_Deviation

ITCAM uses these two parameters to calculate the borders of the "typical zone". See Threshold calculation detail.

Auto_Threshold_Fair_Projection

This determines the position of the fair threshold. Increase this parameter to increase the fair threshold; decrease the parameter to decrease the fair threshold. For details, see Threshold calculation detail. The bad threshold is not affected.

Auto_Threshold_Bad_Projection

This determines the position of the bad threshold. Increase this parameter to increase the bad threshold; decrease the parameter to decrease the bad threshold.For details. The fair threshold is not affected.

Use_Default

If set to 0, the auto threshold settings are modified according to the other parameters in this Take Action. If set to 1, the value of the auto threshold settings for this request are taken from the "parent": the values that have been set for the request type, for the entire application, or the ITCAM default values.

Example: YN:Enable_Auto_Threshold 1 12 50 200 150 300 0

Override_Auto_Threshold: override threshold values

Use the Override_Auto_Threshold Take Action to override fair and bad response time threshold values for any request in the application. In this case, while the baselining statistical data is still preserved, ITCAM does not use automatically calculated thresholds.
Do not override threshold values unless you have analyzed the application performance in detail (or were instructed to override threshold values by IBM Level 3 Support). To adjust threshold values without manually overriding them.
To remove an override, select a request in the Request Baseline workspace, and select the Enable_Auto_Threshold take action command. Leave all parameters as they are, in order to use the same auto threshold parameters as were used before the override.

Command syntax

YN:Override_Auto_Threshold App_Id Request_Id Fair_Response_Threshold Bad_Response_Threshold
Parameters:
App_Id

The application ID, automatically assigned in the portal from the selection context when Take Action was invoked.

Request_Id

The request ID, automatically assigned in the portal from the selection context when Take Action was invoked.

Fair_Response_Threshold

The fair response time threshold, in milliseconds.

Bad_Response_Threshold

The bad response time threshold, in milliseconds.

Remove_WebSphere_SubNode: Remove an inactive WebSphere Application Server

Use the Remove_WebSphere_SubNode command to remove a no-longer-active WebSphere Application Server from the Navigator tree.

Command syntax

If invoked from the Navigator WebSphere Agent entry, the syntax is:
YN:RemSubNode server_name
where server_name is the WebSphere server (subnode-name).
If, however, this command is invoked from a subnode of the Navigator WebSphere Agent entry, the syntax is:
YN:RemSubNode
In this case, server_name is not required because the subnode name (the server name) is already known.

Set_Application_Monitoring: Set monitoring

Use the Set_Application_Monitoring command to set monitoring of the WebSphere application.

Command syntax

YN:Set_Application_Monitoring App_Id Monitoring_Enabled Request_Data_Monitoring_Level Request_Data_Sampling_Rate
where App_Id is the application ID which is automatically assigned in the portal from the selection context when Take Action was invoked.
Monitor_Enabled is a boolean value and the valid values are 0 and 1. It defines whether the monitoring agent application dashboard monitoring feature is enabled for the given application.
Request_Data_Monitoring_Level is an integer value that defines custom request monitoring level for the given application. Valid values are 0 (DISABLE), 1 (LEVEL1), and 2 (LEVEL2). If the Request Monitoring Control Level is set to Application, this level overrides any level that the user might set for the entire monitoring agent.
If the Request Monitoring Control Level is set to Server, this Take Action command has no effect on the actual monitoring level. The new level is recorded, but the server-wide setting is applied. If you change the Request Monitoring Control Level to Application, the recorded application monitoring level takes effect.
Request_Data_Sampling_Rate is an integer value that defines custom request monitoring rate (in percentage) for the given application. Valid values range from 0 to 100.
When this Take Action is selected for a node representing a z/OS servant region, it applies to all servant regions in the same managed system (IBM WebSphere application server instance).
Reflex _Automation_Mode is a boolean value and the valid values are 0 and 1. When you select 1, WR application health monitoring accepts reflex automation commands from WASAppHealthGood/Fair/Bad situations and adjusts the monitoring level automatically based on the current application health status.

Set_Completion_Thresholds: Set completion thresholds

Use the Set_Completion_Thresholds command to define the thresholds of the error rate for the WebSphere application.

Command syntax

YN:Set_Completion_Thresholds App_Id Fair_Completion_Rate Bad_Completion_Rate
where App_Id is the application ID which is automatically assigned in the portal from the selection context when Take Action was invoked.
Fair_Completion_Rate and Bad_Completion_Rate are the values in percentage that define thresholds for fair and bad requests completion rates.

Set_Request_Sampling_Rate: Set the sampling rate for request data

Use the Set_Request_Sampling_Rate command to define the percentage of requests to monitor.

Command syntax

YN:SetRequestSamplingRate percent
where percent is the percentage of requests you want sampled, an integer from 1 to 100.

Start_Baselining: Start the baselining process

ITCAM can run a baselining process for every application. During this process, which runs for a preset period, the data collector collects statistical data on metric values for a given period. Based on this statistical data, the monitoring agent can automatically set the fair and bad thresholds, as well as the typical breakdown of response times for nested requests. Use the Start_Baselining Take Action to start the baselining process.

When ITCAM begins monitoring an application for the first time, it automatically starts this process for the application. However, with time, average response times can change because of configuration, load pattern, database size, and other issues. You can manually start the baselining process again to take these changes into account. You can also use IBM Tivoli Monitoring (ITM) policies and workflow management to run the baselining process every few months.
As soon as you take the Start Baselining action, the baselining process begins. The thresholds are updated when either the Period or the Update Interval passes.
While the baselining process is running, you can trigger a baseline update to immediately set the thresholds based on the information collected so far.

Command syntax

YN:Start_Baselining App_Id Period Update_Interval Run_Clean
Parameters:
App_Id

The application ID, automatically assigned in the portal from the selection context when Take Action was invoked.

Period

The time for which the baselining process runs. The data collector collects the necessary statistical information for this entire period. When ITCAM starts the baselining process automatically, it sets the period to seven days. The format is ddd/hh:mm:ss.

Update_Interval

If you set this parameter to a time interval, ITCAM updates the thresholds according to the information already collected every time this interval passes. For example, when ITCAM starts the baselining process automatically, it sets the update interval to 1 hour. During the seven days that the initial baselining runs, every hour the thresholds are updated according to the statistical data collected so far (for all request types where at least one request was received during the baselining process). The format is ddd/hh:mm:ss.

Run_Clean

Set to either 0 or 1. If set to 0, statistical data collected in any previous baselining for the same requests are kept and "amalgamated" with the new data. If set to 1, only the new data are used for setting the thresholds. Normally, you set this to 1.

Note: When this Take Action command is selected for a node representing a z/OS servant region, it applies to all servant regions in the same managed system (IBM WebSphere application server instance).

Start_GC_Monitoring: Begin reporting garbage-collection data

Use the Start_GC_Monitoring command to activate the display of garbage-collection statistics. This setting is in addition to the WebSphere application server Verbose Garbage Collection value, which must also be active for garbage-collection data to be reported.

Command syntax

YN:StartGCMonitor
When this Take Action command is selected for a node representing a z/OS servant region, it applies to all servant regions in the same managed system (IBM WebSphere application server instance).

10. Start_Request_Monitoring : Begin reporting request data

Use the Start_Request_Monitoring command to activate the display of request data.

Command syntax

YN:StartRequestMonitor level
where level is the resource-data collection level, either Level1 or Level2. When the collection level is set to Level1, only edge request data-such as servlets and JSPs-are collected. When set to Level2, nested request data, such as JDBC and JMS requests, are also collected.
If the Request Monitoring Control Level is set to Server, this level applies to all applications monitored on the server.
If the Request Monitoring Control Level is set to Application, you can set the monitoring level for any operation separately, using the Take Action command. The monitoring level from the Start_Request_Monitoring Take Action command is applied by default to newly discovered applications.
When this Take Action command is selected for a node representing a z/OS servant region, it applies to all servant regions in the same managed system (IBM WebSphere application server instance).

Start_Resource_Monitoring: Begin reporting PMI data

Use the Start_Resource_Monitoring command to activate the display of resource (that is, PMI) data. This setting is in addition to the WebSphere application server PMI instrumentation levels, which must also be set for resource data to be reported.

Command syntax

YN:StartResourceMonitor
When this Take Action command is selected for a node representing a z/OS servant region, it applies to all servant regions in the same managed system (IBM WebSphere application server instance).

Start_WebSphere_Server: Start a WebSphere Application Server

Use the Start_WebSphere_Server command to start an application server.

Command syntax

If invoked from the Navigator WebSphere Agent entry, the syntax is:
YN:StartAppSvr server_name user password
where server_name is the WebSphere server name, and user and password are your own WebSphere Application Server identifiers set via the WebSphere administrative console (required only if WebSphere global security is enabled).
If, however, this command is invoked from a subnode of the Navigator WebSphere Agent entry, the syntax is:
YN:StartAppSvr user password
where user and password are your own WebSphere application server identifiers set via the WebSphere administrative console; these are required only if WebSphere global security is enabled. (In this case, server_name is not required because the subnode name-that is, the server name-is already known.)

Stop_Baselining: stop the baselining process

Use the Stop_Baselining Take Action command to immediately stop the baselining process for an application, and recalculate the thresholds based on the request data available up to this point.

Normally you do not have to complete this action. To recalculate the thresholds based on the request data available up to this point, without stopping the baselining process.

Command syntax

YN:Stop_Baselining App_Id
Parameters:
App_Id

The application ID, automatically assigned in the portal from the selection context when Take Action was invoked.

When this Take Action command is selected for a node representing a z/OS servant region, it applies to all servant regions in the same managed system (IBM WebSphere application server instance).

Stop_GC_Monitoring: Stop reporting garbage-collection data

Use the Stop_GC_Monitoring command to end the display of garbage-collection statistics.

Command syntax

YN:StopGCMonitor
When this Take Action command is selected for a node representing a z/OS servant region, it applies to all servant regions in the same managed system (IBM WebSphere application server instance).

Stop_Request_Monitoring: Stop reporting request data

Use the Stop_Request_Monitoring command to end the display of request data.

Command syntax

YN:StopRequestMonitor
When this Take Action command is selected for a node representing a z/OS servant region, it applies to all servant regions in the same managed system (IBM WebSphere application server instance).

Stop_Resource_Monitoring: Stop reporting PMI data

Use the Stop_Resource_Monitoring command to end the display of resource (that is, PMI) data.

Command syntax

YN:StopResourceMonitor
When this Take Action command is selected for a node representing a z/OS servant region, it applies to all servant regions in the same managed system (IBM WebSphere application server instance).

Stop_WebSphere_Server: Stop a WebSphere Application Server

Use the Stop_WebSphere_Server command to stop an application server.

Command syntax

If invoked from the Navigator WebSphere Agent entry, the syntax is:
YN:StopAppSvr server_name user password
where server_name is the WebSphere server name, and user and password are your own WebSphere Application Server identifiers set through the WebSphere administrative console (required only if WebSphere global security is enabled).
If, however, this command is invoked from a subnode of the Navigator WebSphere Agent entry, the syntax is:
YN:StopAppSvr user password
where user and password are your own WebSphere Application Server identifiers set through the WebSphere administrative console; these are required only if WebSphere global security is enabled. (In this case, server_name is not required because the subnode name-that is, the server name-is already known.)

Update_Baseline: trigger a baseline update

If the baselining process is running, the thresholds are set automatically when either the Period or the Update Interval passes. For the initial baselining process, the first automatic update happens after one hour. With the Update_Baseline Take Action, you can force ITCAM to update the thresholds immediately, based on the information collected so far. This can be useful if you do not want to wait for the periodic automatic update. When the automatic update time comes, the threshold is updated again.

If a baselining process is not running for the application, an error is raised. If no requests of a given request type have been received since the baselining process has started, the update has no effect for this request type.

Command syntax

YN:Update_Baseline App_Id
Parameters:
App_Id

The application ID, automatically assigned in the portal from the selection context when Take Action was invoked.

When this Take Action command is selected for a node representing a z/OS servant region, it applies to all servant regions in the same managed system (IBM WebSphere application server instance).

Threshold calculation detail

If you want to set parameters that affect the calculation of the automatic response time thresholds, you might need to know the details of this calculation.
ITCAM processes the baselining statistical data and applies the auto threshold parameters in the following way. The parameters are set in the Enable_Auto_Threshold take action command.

The response time results are sorted into up to 64 "buckets", from zero to the maximum response time encountered for this request. The buckets do not represent equal time intervals; for response time regions where most of the "hits" fall, the buckets represent smaller intervals. For example, if the maximum encountered time is 1000 ms but most response times are 300 - 500 ms, then the first bucket might be 0 - 50 ms, but there can also be buckets representing response times of 305 - 310 ms and 400 - 402 ms. ITCAM distributes the bucket borders so that the largest number of hits in any one bucket is not more than three times the number of hits in the smallest bucket.
ITCAM calculates the percentage of the total amount of requests that fall into each response time bucket. ITCAM then divides it by the time interval width represented by the bucket. This is shown on the Response Times Distribution bar chart in the Request Baseline workspace.

Each bar represents a bucket, and the bar height shows the percentage of the requests in this bucket. All the subsequent calculations are rounded up to buckets.
ITCAM determines the selection zone, which contains the "typical" response time values. This zone is represented by the bars colored blue on the chart.
ITCAM finds the response time interval (left border L to right border R) where the following statements are true:

The percentage of hits that fall into this interval is no less than the Auto_Threshold_Percent parameter.
The spread of the time interval, calculated as (R/L)*100 - 100, is not greater than the Auto_Threshold_Deviation parameter.
The Auto_Threshold_Deviation parameter does not denote the statistical definition of deviation.
If several zones match these criteria, ITCAM chooses the one where the following value is the greatest: S/(R-L), where S is the total number of hits that fell into this zone.
If a zone where both requirements are true cannot be found at all, ITCAM first determines the interval where the percentage of hits is not less than the Auto_Threshold_Percent parameter while the spread is as little as possible. Then, within this interval, it finds a zone where the spread is not greater than the Auto_Threshold_Deviation parameter and the percentage of hits is as large as possible.
ITCAM determines the typical nested request times from the nested request times in this zone, shown on the Level2 Delays Distribution chart.
Finally, ITCAM calculates the thresholds.
The fair threshold is determined using the left and right borders of the selection zone and the Auto_Threshold_Fair_Projection parameter:
F = L + ((R-L) * Auto_Threshold_Fair_Projection / 100)
The bad threshold is calculated in the same way, using the Auto_Threshold_Bad_Projection parameter:
B = L + ((R-L) * Auto_Threshold_Bad_Projection / 100)

Example: the left border of the selection zone might be L=1450 ms, and the right border R=3000 ms. By default, Auto_Threshold_Fair_Projection=150, and Auto_Threshold_Bad_Projection=300. In this case:

The fair response threshold is F = 1450 + ((3000-1450) * 150 / 100) = 3775 ms
The bad response threshold is B = 1450 + ((3000-1450) * 300 / 100) = 6100 ms

WebSphere PMI Attribute Mapping

Contents

WebSphere PMI Attribute Mapping

The following tables show how the data displayed in the ITCAM for Application Diagnostics resource workspaces map to their corresponding WebSphere PMI categories and their attributes. It also provides the monitoring overhead incurred when turning on these attributes.

By default, ITCAM changes the PMI collection level based on its monitoring level.

TEP Console Workspace Columns to WebSphere PMI Attribute Mapping

TEP Console Workspace Columns to WebSphere PMI Attribute Mapping.
TEP Console Workspace Columns to WebSphere PMI Attribute Mapping

AppServer--High Availability Manager ITM Table Name: KYNHAMGMT
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: HAManager
Local Groups LocalGroupCount LocalGroupCount All High
Group State Rebuild Time GroupStateRebuildTime GroupStateRebuildTime All High
Bulletin-Board Subjects BulletinBoardSubjectCount BulletinBoardSubjectCount All High
Bulletin-Board Subscriptions BulletinBoardSubcriptionCount BulletinBoardSubcriptionCount All High
Bulletin-Board Rebuild Time BulletinBoardRebuildTime BulletinBoardRebuildTime All High
Local Bulletin-Board Subjects LocalBulletinBoardSubjectCount LocalBulletinBoardSubjectCount All High

AppServer-DCS Stacks ITM Table Name: KYNDCSSTK
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: DCS Statistics
Message Buffer Reallocations MessageBufferReallocationCount MessageBufferReallocationCount All Medium
Sent Messages SentMessageCount SentMessageCount All High
Average Outgoing Message Size OutgoingMessageSize OutgoingMessageSize All High
Minimum Outgoing Message Size OutgoingMessageSize OutgoingMessageSize All High
Maximum Outgoing Message Size OutgoingMessageSize OutgoingMessageSize All High
Outgoing Messages SentMessageCount SentMessageCount All High
Average Incoming Message Size IncomingMessageSize IncomingMessageSize All High
Minimum Incoming Message Size IncomingMessageSize IncomingMessageSize All High
Maximum Incoming Message Size IncomingMessageSize IncomingMessageSize All High
Incoming Messages ReceivedMessageCount ReceivedMessageCount All High
Synchronization Completion Time SynchronizationCompleteTime SynchronizationCompleteTime All High
Synchronization Timeouts SynchronizationTimeoutCount SynchronizationTimeoutCount All Medium
High Severity Congestion Events HighSeverityCongestionEventCount HighSeverityCongestionEventCount All Medium
Coalesce Time CoalesceTime CoalesceTime All Medium
Join View Change Time JoinViewChangeTime JoinViewChangeTime All High
Remove View Change Time RemoveViewChangeTime RemoveViewChangeTime All High
Suspicions SuspicionCount SuspicionCount All High
View Changes ViewChangeCount ViewChangeCount All Medium
Group Size ViewGroupSize ViewGroupSize All Medium

Web Applications ITM Table Name: KYNAPP
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Web Applications
Request Count RequestCount (Servlet Info) RequestCount (Servlet Info) Basic Low
Request Rate (per sec) RequestCount RequestCount Basic Low
Error Count ErrorCount (Servlet Info) ErrorCount (Servlet Info) Extended Low
Error Rate (per sec) ErrorCount (Servlet Info) ErrorCount (Servlet Info) Extended Low
Average Response Time (ms) ServiceTime (Servlet Info) ServiceTime (Servlet Info) Basic Medium
Average Concurrent Requests ConcurrentRequests (Servlet Info) ConcurrentRequests (Servlet Info) Extended High
Servlets Loaded LoadedServletCount LoadedServletCount All Low
Servlets Reloaded ReloadCount ReloadCount All Low

WebApplications --ServletSessions ITM Table Name: KYNSERVS
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Servlet Session Manager
Sessions Created CreateCount CreateCount All Low
Session Creation Rate (per sec) CreateCount CreateCount All Low
Sessions Invalidated InvalidateCount InvalidateCount All Low
Session Invalidation Rate (per sec) InvalidateCount InvalidateCount All Low
Average Session Lifetime (ms) LifeTime LifeTime Extended Medium
Average Concurrently Active Sessions ActiveCount ActiveCount All High
Average Concurrently Live Sessions LiveCount LiveCount Basic High
Failed Session Requests NoRoomForNewSessionCount NoRoomForNewSessionCount Extended Low
Failed Session Request Rate (per sec) NoRoomForNewSessionCount NoRoomForNewSessionCount Extended Low
Cache Discards CacheDiscardCount CacheDiscardCount All Low
Cache Discard Rate (per sec) CacheDiscardCount CacheDiscardCount All Low
External Read Time (ms) ExternalReadTime ExternalReadTime Extended Medium
External Read Size (bytes) ExternalReadSize ExternalReadSize Extended Medium
External Write Time (ms) ExternalWriteTime ExternalWriteTime Extended Medium
External Write Size (bytes) ExternalWriteSize ExternalWriteSize Extended Medium
Broken Session Affinities AffinityBreakCount AffinityBreakCount All Low
Broken Session Affinity Rate (per sec) AffinityBreakCount AffinityBreakCount All Low
Time since Last Activated TimeSinceLastActivated TimeSinceLastActivated All Medium
Nonexistent Session Requests ActivateNonExistSessionCount ActivateNonExistSessionCount All Low
Nonexistent Session Request Rate (per sec) ActivateNonExistSessionCount ActivateNonExistSessionCount All Low
Total Serializable Session Object Size (bytes) SessionObjectSize SessionObjectSize All Max
Average Serializable Session Object Size (bytes) SessionObjectSize SessionObjectSize All Max
Min Serializable Session Object Size (bytes) SessionObjectSize SessionObjectSize All Max
Max Serializable Session Object Size (bytes) SessionObjectSize SessionObjectSize All Max

EJB Containers ITM Table Name: KYNCONTNR
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Enterprise Beans
Method Average Response Time (ms) MethodResponseTime MethodResponseTime Basic High
Method Invocation Count MethodCallCount MethodCallCount Basic High
Method Invocation Rate (per sec) MethodCallCount MethodCallCount Basic High
Create Average Time (ms) CreateTime CreateTime All Max
Remove Average Time (ms) RemoveTime RemoveTime All Max
Average Concurrently Ready Beans ReadyCount ReadyCount Basic Low
Average Concurrently Live Beans LiveCount LiveCount Extended High
Active Method Count ActiveMethodCount ActiveMethodCount All High
Create Count CreateCount CreateCount Basic Low
Creation Rate (per sec) CreateCount CreateCount Basic Low
Remove Count RemoveCount RemoveCount Basic Low
Removal Rate per sec) RemoveCount RemoveCount Basic Low
Activate Count ActivateCount ActivateCount All Low
Activation Rate (per sec) ActivateCount ActivateCount All Low
Passivate Count PassivateCount PassivateCount Basic Low
Passivation Rate (per sec) PassivateCount PassivateCount Basic Low
Entity Bean Load Count LoadCount LoadCount All Low
Entity Bean Load Rate (per sec) LoadCount LoadCount All Low
Entity Bean Store Count StoreCount StoreCount All Low
Entity Bean Store Rate (per sec) StoreCount StoreCount All Low
Instantiate Count InstantiateCount InstantiateCount All Low
Instantiation Rate (per sec) InstantiateCount InstantiateCount All Low
Destroy Count FreedCount FreedCount All Low
Destruction Rate (per sec) FreedCount FreedCount All Low

EJB Containers ---Enterprise Java. Beans ITM Table Name: KYNEJB
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Enterprise Beans
Method Invocations MethodCallCount MethodCallCount Basic High
Method Invocation Rate (per sec) MethodCallCount MethodCallCount Basic High
Method Average Response Time (ms) MethodResponseTime MethodResponseTime Basic High
Create Count CreateCount CreateCount Basic Low
Creation Rate (per sec) CreateCount CreateCount Basic Low
Create Average Time (ms) CreateTime CreateTime All Max
Remove Count RemoveCount RemoveCount Basic Low
Removal Rate (per sec) RemoveCount RemoveCount Basic Low
Remove Average Time (ms) RemoveTime RemoveTime All Max
Activate Count ActivateCount ActivateCount All Low
Activation Rate (per sec) ActivateCount ActivateCount All Low
Passivate Count PassivateCount PassivateCount All Low
Passivation Rate PassivateCount PassivateCount All Low
Entity Bean Load Count LoadCount LoadCount All Low
Entity Bean Load Rate (per sec) LoadCount LoadCount All Low
Entity Bean Store Count StoreCount StoreCount All Low
Entity Bean Store Rate (per sec) StoreCount StoreCount All Low
Instantiate Count InstantiateCount InstantiateCount All Low
Destroy Count FreedCount FreedCount All Low
Destruction Rate (per sec) FreedCount FreedCount All Low
Find Count RetrieveFromPoolSuccessCount RetrieveFromPoolSuccessCount All Low
Find Rate (per sec) RetrieveFromPoolSuccessCount RetrieveFromPoolSuccessCount All Low
Get Count RetrieveFromPoolCount RetrieveFromPoolCount All Low
Get Rate (per sec) RetrieveFromPoolCount RetrieveFromPoolCount All Low
Return Count ReturnsToPoolCount ReturnsToPoolCount Extended Low
Return Rate (per sec) ReturnsToPoolCount ReturnsToPoolCount Extended Low
Discard Count ReturnsDiscardCount ReturnsDiscardCount Extended Low
Discard Rate (per sec) ReturnsDiscardCount ReturnsDiscardCount Extended Low
Drain Count DrainsFromPoolCount DrainsFromPoolCount All Low
Drain Rate (per sec) DrainsFromPoolCount DrainsFromPoolCount All Low
Average Concurrently Ready Beans ReadyCount ReadyCount Basic High
Average Concurrently Live Beans LiveCount LiveCount Extended High
Active Method Count ActiveMethodCount ActiveMethodCount All High
Average Objects Discarded DrainSize DrainSize All Medium
Average Objects in Pool PooledCount PooledCount Basic High

EJB Containers ---Container Transactions ITM Table Name: KYNTRANS
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Transaction Manager
Global Transactions Begun GlobalBegunCount GlobalBegunCount Extended Low
Global Transactions Begin Rate (per sec) GlobalBegunCount GlobalBegunCount Extended Low
Local Transactions Begun LocalBegunCount LocalBegunCount Extended Low
Local Transactions Begin Rate (per sec) LocalBegunCount LocalBegunCount Extended Low
Global Transactions Active ActiveCount ActiveCount Basic Low
Local Transactions Active LocalActiveCount LocalActiveCount All Low
Global Transactions Committed CommittedCount CommittedCount Basic Low
Global Transaction Commit Rate (per sec) CommittedCount CommittedCount Basic Low
Local Transactions Committed LocalCommittedCount LocalCommittedCount All Low
Local Transaction Commit Rate (per sec) LocalCommittedCount LocalCommittedCount All Low
Global Transactions Rolled Back RolledbackCount RolledbackCount Basic Low
Global Transaction Rollback Rate (per sec) RolledbackCount RolledbackCount Basic Low
Local Transactions Rolled Back LocalRolledbackCount LocalRolledbackCount All Low
Local Transaction Rollback Rate (per sec) LocalRolledbackCount LocalRolledbackCount All Low
Global Transaction Timeouts GlobalTimeoutCount GlobalTimeoutCount Extended Low
Global Transaction Timeout Rate (per sec) GlobalTimeoutCount GlobalTimeoutCount Extended Low
Local Transaction Timeouts LocalTimeoutCount LocalTimeoutCount Extended Low
Local Transaction Timeout Rate (per sec) LocalTimeoutCount LocalTimeoutCount Extended Low
Global Transactions Optimized OptimizationCount OptimizationCount All Low
Global Transaction Optimize Rate (per sec) CommittedCount CommittedCount Basic Low
Global Transactions Involved GlobalInvolvedCount GlobalInvolvedCount All Low
Global Transactions Involve Rate (per sec) GlobalInvolvedCount GlobalInvolvedCount All Low
Global Transaction Duration (ms) GlobalTranTime GlobalTranTime Extended Medium
Local Transaction Duration (ms) LocalTranTime LocalTranTime Extended Medium
Global Transaction before Completion Duration (ms) GlobalBeforeCompletionTime GlobalBeforeCompletionTime All Medium
Local Transaction before Completion Duration (ms) LocalBeforeCompletionTime LocalBeforeCompletionTime All Medium
Global Transaction Commit Duration (ms) GlobalCommitTime GlobalCommitTime All Medium
Local Transaction Commit Duration (ms) LocalCommitTime LocalCommitTime All Medium
Global Transaction Prepare Duration (ms) GlobalPrepareTime GlobalPrepareTime All Medium

EJB Containers ---Container Object Pools ITM Table Name: KYNCNTROP
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead

Average Objects in Pool PooledCount PooledCount Basic High
Average Objects Discarded DrainSize DrainSize All Medium
Find Count RetrieveFromPoolSuccessCount RetrieveFromPoolSuccessCount All Low
Find Rate RetrieveFromPoolSuccessCount RetrieveFromPoolSuccessCount All Low
Get Count RetrieveFromPoolCount RetrieveFromPoolCount All Low
Get Rate RetrieveFromPoolCount RetrieveFromPoolCount All Low
Return Count ReturnsToPoolCount ReturnsToPoolCount Extended Low
Return Rate ReturnsToPoolCount ReturnsToPoolCount Extended Low
Discard Count ReturnsDiscardCount ReturnsDiscardCount Extended Low
Discard Rate ReturnsDiscardCount ReturnsDiscardCount Extended Low
Drain Count DrainsFromPoolCount DrainsFromPoolCount All Low
Drain Rate DrainsFromPoolCount DrainsFromPoolCount All Low

DB Connection Pools ITM Table Name: KYNDBCONP
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: JDBC Connection Pools
Maximum Pool Size PoolSize PoolSize Basic High
Average Pool Size PoolSize PoolSize Basic High
Average Waiting Threads WaitingThreadCount WaitingThreadCount Basic High
Average Wait Time (ms) WaitTime WaitTime Basic Medium
Average Usage Time (ms) UseTime UseTime Basic Medium
Average Free Pool Size FreePoolSize FreePoolSize Basic High
JDBC Time(ms) JDBCTime JDBCTime Extended Medium
Percent Used PercentUsed PercentUsed Basic High
Percent of Time Pool at Max PercentMaxed PercentMaxed All High
Connections Created CreateCount CreateCount Basic Low
Connection Creation Rate (per sec) CreateCount CreateCount Basic Low
Connections Allocated AllocateCount AllocateCount Extended Low
Connection Allocation Rate (per sec) AllocateCount AllocateCount Extended Low
Connections Destroyed CloseCount CloseCount Basic Low
Connection Destruction Rate (per sec) CloseCount CloseCount Basic Low
Threads Timed Out FaultCount FaultCount Extended Low
Thread Timeout Rate (per sec) FaultCount FaultCount Extended Low
Prep Statement Cache Discards PrepStmtCacheDiscardCount PrepStmtCacheDiscardCount Extended Low
Prep Statement Cache Discard Rate (per sec) PrepStmtCacheDiscardCount PrepStmtCacheDiscardCount Extended Low
Return Count ReturnCount ReturnCount Extended Low
Return Rate(per sec) ReturnCount ReturnCount Extended Low

J2C Connection Pools ITM Table Name: KYNJ2C
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: J2C Connection Pools
Maximum Pool Size PoolSize PoolSize Basic High
Average Pool Size PoolSize PoolSize Basic High
Average Free Connections FreePoolSize FreePoolSize Basic High
Connections Used ManagedConnectionCount ManagedConnectionCount All Low
Connection Handles ConnectionHandleCount ConnectionHandleCount All Low
Average Wait Time (ms) WaitTime WaitTime Basic Medium
Concurrent Waiting Threads WaitingThreadCount WaitingThreadCount Basic High
Average Usage Time (ms) UseTime UseTime Basic Medium
Pool Used (%) PercentUsed PercentUsed All High
Percent of Time Pool at Max PercentMaxed PercentMaxed All High
Connections Created CreateCount CreateCount Basic Low
Connection Creation Rate (per sec) CreateCount CreateCount Basic Low
Connections Allocated AllocateCount AllocateCount All Low
Connection Allocation Rate (per sec) AllocateCount AllocateCount All Low
Connections Returned FreedCount FreedCount All Low
Connection Return Rate (per sec) FreedCount FreedCount All Low
Connections Destroyed CloseCount CloseCount Basic Low
Connection Destruction Rate (per sec) CloseCount CloseCount Basic Low
Connection Pool Timeouts FaultCount FaultCount All Low
Connection Pool Timeout Rate (per sec) FaultCount FaultCount All Low

Thread Pools Table Name: KYNTHRDP
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Thread Pools
Maximum Pool Size PoolSize PoolSize Basic High
Average Pool Size PoolSize PoolSize Basic High
Average Active Threads ActiveCount ActiveCount Extended High
Average Free Threads PoolSize - ActiveCount PoolSize - ActiveCount Extended High
Percent of Time Pool at Max PercentMaxed PercentMaxed All High
Threads Created CreateCount CreateCount All Low
Thread Creation Rate (per sec) CreateCount CreateCount All Low
Threads Destroyed DestroyCount DestroyCount All Low
Thread Destruction Rate (per sec) DestroyCount DestroyCount All Low

Thread Pools ---Alarm Manager ITM Table Name: KYNALARMM
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Alarm Manager
Alarms Cancelled AlarmsCancelledCount AlarmsCancelledCount All High
Alarms Latency Duration AlarmLatencyDuration AlarmLatencyDuration All High
Alarms Rate AlarmRate AlarmRate All High
Alarms Created AlarmsCreatedCount AlarmsCreatedCount All High
Alarms Fired AlarmsFiredCount AlarmsFiredCount All High
Alarms Pending Size AlarmsPendingSize AlarmsPendingSize All High

Dynamic Cache ITM Table Name: KYNCACHE
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Dynamic Caching
Maximum In-Memory Cache Size MaxInMemoryCacheEntryCount MaxInMemoryCacheEntryCount All Low
Current In-Memory Cache Size InMemoryCacheEntryCount InMemoryCacheEntryCount All Low
In-Memory and Disk Timeouts TimeoutInvalidationCount TimeoutInvalidationCount All Low
In-Memory and Disk Timeout Rate (per sec) TimeoutInvalidationCount TimeoutInvalidationCount All Low

Dynamic Cache Templates ITM Table Name: KYNCACHT
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Templates
Current Cache Size InMemoryAndDiskCacheEntry Count InMemoryAndDiskCacheEntry Count All Low
Disk Hits HitsOnDiskCount HitsOnDiskCount All Low
Disk Hit Rate(per sec) HitsOnDiskCount HitsOnDiskCount All Low
Memory Hits HitsInMemoryCount HitsInMemoryCount Extended Low
Memory Hit Rate(per sec) HitsInMemoryCount HitsInMemoryCount Extended Low
Remote Hits RemoteHitCount RemoteHitCount All Low
Remote Hit Rate(per sec) RemoteHitCount RemoteHitCount All Low
Cache Misses MissCount MissCount Extended Low
Cache Miss Rate(per sec) MissCount MissCount Extended Low
Remote Cache Entries Received RemoteCreationCount RemoteCreationCount All Low
Remote Cache Entry Receive Rate(per sec) RemoteCreationCount RemoteCreationCount All Low
Client Requests ClientRequestCount ClientRequestCount All Low
Client Request Rate(per sec) ClientRequestCount ClientRequestCount All Low
Cluster Requests DistributedRequestCount DistributedRequestCount All Low
Cluster Request Rate(per sec) DistributedRequestCount DistributedRequestCount All Low
Total Explicit Invalidations ExplicitInvalidationCount ExplicitInvalidationCount All Low
Total Explicit Invalidation Rate(per sec) ExplicitInvalidationCount ExplicitInvalidationCount All Low
Timeout Invalidations TimeoutInvalidationCount TimeoutInvalidationCount All Low
Timeout Invalidation Rate(per sec) TimeoutInvalidationCount TimeoutInvalidationCount All Low
Least Recently Used Invalidations LruInvalidationCount LruInvalidationCount All Low
Least Recently Used Invalidation Rate(per sec) LruInvalidationCount LruInvalidationCount All Low
Explicit Memory Invalidations ExplicitMemoryInvalidationCount ExplicitMemoryInvalidationCount All Low
Explicit Memory Invalidation Rate(per sec) ExplicitMemoryInvalidationCount ExplicitMemoryInvalidationCount All Low
Explicit Disk Invalidations ExplicitDiskInvalidationCount ExplicitDiskInvalidationCount All Low
Explicit Disk Invalidations Rate(per sec) ExplicitDiskInvalidationCount ExplicitDiskInvalidationCount All Low
Explicit Local Invalidations LocalExplicitInvalidationCount LocalExplicitInvalidationCount All Low
Explicit Local Invalidation Rate(per sec) LocalExplicitInvalidationCount LocalExplicitInvalidationCount All Low
Explicit Remote Invalidations RemoteExplicitInvalidationCount RemoteExplicitInvalidationCount All Low
Explicit Remote Invalidation Rate(per sec) RemoteExplicitInvalidationCount RemoteExplicitInvalidationCount All Low

Workload Management Client ITM Table Name: KYNWLMCL
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Workload Management client
Outgoing Requests OutgoingIIOPRequestCount OutgoingIIOPRequestCount All Low
Outgoing Request Rate (per sec) OutgoingIIOPRequestCount OutgoingIIOPRequestCount All Low
Client Cluster Updates ClientClusterUpdateCount ClientClusterUpdateCount All Low
Client Cluster Update Rate (per sec) ClientClusterUpdateCount ClientClusterUpdateCount All Low
Client Response Time ClientResponseTime ClientResponseTime All Medium

Workload Management Server ITM Table Name: KYNWLMSR
WebSphere PMI Level
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Workload Management server
Incoming Requests IIOPRequestCount IIOPRequestCount Extended Low
Incoming Request Rate (per sec) IIOPRequestCount IIOPRequestCount Extended Low
Incoming Strong Affinity Requests StrongAffinityIIOPRequestCount StrongAffinityIIOPRequestCount All Low
Incoming Strong Affinity Request Rate (per sec) StrongAffinityIIOPRequestCount StrongAffinityIIOPRequestCount All Low
Incoming Nonaffinity Requests NoAffinityIIOPRequestCount NoAffinityIIOPRequestCount All Low
Incoming Nonaffinity Request Rate (per sec) NoAffinityIIOPRequestCount NoAffinityIIOPRequestCount All Low
Incoming Non-WLM Object Requests NonWLMEnabledIIOPRequestCount NonWLMEnabledIIOPRequestCount All Low
Incoming Non-WLM Object Request Rate (per sec) NonWLMEnabledIIOPRequest Count NonWLMEnabledIIOPRequestCount All Low
Server Cluster Updates ServerClusterUpdateCount ServerClusterUpdateCount All Low
Server Cluster Update Rate (per sec) ServerClusterUpdateCount ServerClusterUpdateCount All Low
WLM Clients Serviced WLMClientsServicedCount WLMClientsServicedCount All Low
WLM Clients Serviced Rate (per sec) WLMClientsServicedCount WLMClientsServicedCount All Low
Concurrent Requests ConcurrentRequestCount ConcurrentRequestCount Extended High
Server Response Time (ms) ServerResponseTime ServerResponseTime Extended Medium

Scheduler ITM Table Name: KYNSCHED
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Schedulers
Poll Count PollCount PollCount All High
Poll Duration PollDuration PollDuration All High
Poll Query Duration PollQueryDuration PollQueryDuration All High
Run Duration RunDuration RunDuration All High
Task Collision Rate TaskCollisionRate TaskCollisionRate All High
Task Delay Duration TaskDelayDuration TaskDelayDuration All High
Task Expiration Rate TaskExpirationRate TaskExpirationRate All High
Task Failure Count TaskFailureCount TaskFailureCount All High
Task Finish Count TaskFinishCount TaskFinishCount All High
Task Finish Rate TaskFinishRate TaskFinishRate All High
Task Run Rate TaskRunRate TaskRunRate All High

Web Services ITM Table Name: KYNWEBSVC
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Web services
Received Requests ReceivedRequestCount ReceivedRequestCount All Low
Dispatched Requests DispatchedRequestCount DispatchedRequestCount All Low
Processed Requests ProcessedRequestCount ProcessedRequestCount All Low
Response Time ResponseTime ResponseTime All High
Request Response Time RequestResponseTime RequestResponseTime All Medium
Dispatch Response Time DispatchResponseTime DispatchResponseTime All Medium
Reply Response Time ReplyResponseTime ReplyResponseTime All Medium
Payload Size PayloadSize PayloadSize All Medium
Reply Payload Size ReplyPayloadSize ReplyPayloadSize All Medium
Request Payload Size RequestPayloadSize RequestPayloadSize All Medium

WebServices Gateway ITM Table Name: KYNWEBSGW
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Web services Gateway
Synchronous Requests SynchronousRequestCount SynchronousRequestCount All Low
Synchronous Responses SynchronousResponseCount SynchronousResponseCount All Low
Asynchronous Requests AsynchronousRequestCount AsynchronousRequestCount All Low
Asynchronous Responses AsynchronousResponseCount AsynchronousResponseCount All Low

Messaging Engines ITM Table Name: KYNMSGENG
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: SIB Service > SIB Messaging Engines
Average Local Wait Time (ms) LocalMessageWaitTime LocalMessageWaitTime All Low
Expired Messages ReportEnabledMessagesExpiredCount ReportEnabledMessagesExpiredCount All Low
Incomplete Topic Publications IncompletePublicationCount IncompletePublicationCount All Low
Total Published TotalMessagesPublishedCount TotalMessagesPublishedCount All Low

Client Communications ITM Table Name: KYNCLICOM
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: Standard Statistics
Clients Attached ClientsAttachedCount ClientsAttached All Low
API Connections APIConnectionsCount APIConnections All Low
Errors ErrorsCount Errors All Low
Writes WritesCount Writes All Low
Reads ReadsCount Reads All Low
Writes Blocked WritesBlockedCount WritesBlocked All Low
Reads Blocked ReadsBlockedCount ReadsBlocked All Low
Multicast Write (bytes) MulticastWriteBytesCount MulticastWriteBytes All Low
Multicast Send Messages MulticastSendMessageCount MulticastSendMessage All Low
Buffered Write (bytes) BufferedWriteBytesCount BufferedWriteBytes All Low
Buffered Read (bytes) BufferedReadBytesCount BufferedReadBytes All Low
Message Written (bytes) MessagesBytesWrittenCount ClientStats.MessageBytesWritten All Low
Message Read (bytes) MessageBytesReadCount MessageBytesRead All Low
Total Written (bytes) TotalBytesWrittenCount TotalBytesWritten All Low
Total Read (bytes) TotalBytesReadCount TotalBytesRead All Low
Category: Detailed Statistics
Sent at Highest Priority (bytes) BytesSentAtHighestPriorityCount BytesSentAtHighestPriority All Low
Sent at Very High Priority (bytes) BytesSentAtVeryHighPriorityCount BytesSentAtVeryHighPriority All Low
Sent at High Priority (bytes) BytesSentAtHighPriorityCount BytesSentAtHighPriority All Low
Sent at JMS 9 Priority (bytes) BytesSentAtJMS9PriorityCount BytesSentAtJMS9Priority All Low
Sent at JMS 8 Priority (bytes) BytesSentAtJMS8PriorityCount BytesSentAtJMS8Priority All Low
Sent at JMS 7 Priority (bytes) BytesSentAtJMS7PriorityCount BytesSentAtJMS7Priority All Low
Sent at JMS 6 Priority BytesSentAtJMS6PriorityCount BytesSentAtJMS6Priority All Low
Sent at JMS 5 Priority (bytes) BytesSentAtJMS5PriorityCount BytesSentAtJMS5Priority All Low
Sent at JMS 4 Priority (bytes) BytesSentAtJMS4PriorityCount BytesSentAtJMS4Priority All Low
Sent at JMS 3 Priority (bytes) BytesSentAtJMS3PriorityCount BytesSentAtJMS3Priority All Low
Sent at JMS 2 Priority (bytes) BytesSentAtJMS2PriorityCount BytesSentAtJMS2Priority All Low
Sent at JMS 1 Priority (bytes) BytesSentAtJMS1PriorityCount BytesSentAtJMS1Priority All Low
Sent at JMS 0 Priority (bytes) BytesSentAtJMS0PriorityCount BytesSentAtJMS0Priority All Low
Sent at Low Priority (bytes) BytesSentAtLowPriorityCount BytesSentAtLowPriority All Low
Sent at Very Low Priority (bytes) BytesSentAtVeryLowPriorityCount BytesSentAtVeryLowPriority All Low
Sent at Lowest Priority (bytes) BytesSentAtLowestPriorityCount BytesSentAtLowestPriority All Low
Received at Highest Priority (bytes) BytesReceivedAtHighestPriorityCount BytesReceivedAtHighestPriority All Low
Received at Very High Priority (bytes) BytesReceivedAtVeryHighPriority Count BytesReceivedAtVeryHighPriority All Low
Received at High Priority (bytes) BytesReceivedAtHighPriorityCount BytesReceivedAtHighPriority All Low
Received at JMS 9 Priority (bytes) BytesReceivedAtJMS9PriorityCount BytesReceivedAtJMS9Priority All Low
Received at JMS 8 Priority (bytes) BytesReceivedAtJMS8PriorityCount BytesReceivedAtJMS8Priority All Low
Received at JMS 7 Priority (bytes) BytesReceivedAtJMS7PriorityCount BytesReceivedAtJMS7Priority All Low
Received at JMS 6 Priority (bytes) BytesReceivedAtJMS6PriorityCount BytesReceivedAtJMS6Priority All Low
Received at JMS 5 Priority (bytes) BytesReceivedAtJMS5PriorityCount BytesReceivedAtJMS5Priority All Low
Received at JMS 4 Priority (bytes) BytesReceivedAtJMS4PriorityCount BytesReceivedAtJMS4Priority All Low
Received at JMS 3 Priority (bytes) BytesReceivedAtJMS3PriorityCount BytesReceivedAtJMS3Priority All Low
Received at JMS 2 Priority (bytes) BytesReceivedAtJMS2PriorityCount BytesReceivedAtJMS2Priority All Low
Received at JMS 1 Priority (bytes) BytesReceivedAtJMS1PriorityCount BytesReceivedAtJMS1Priority All Low
Received at JMS 0 Priority (bytes) BytesReceivedAtJMS0PriorityCount BytesReceivedAtJMS0Priority All Low
Received at Low Priority (bytes) BytesReceivedAtLowPriorityCount BytesReceivedAtLowPriority All Low
Received at Very Low Priority (bytes) BytesReceivedAtVeryLowPriority Count BytesReceivedAtVeryLowPriority All Low
Received at Lowest Priority (bytes) BytesReceivedAtLowestPriorityCount BytesReceivedAtLowestPriority All Low
Messages Sent at JMS 9 Priority MessagesSentAtJMS9PriorityCount MessagesSentAtJMS9Priority All Low
Messages Sent at JMS 8 Priority MessagesSentAtJMS8PriorityCount MessagesSentAtJMS8Priority All Low
Messages Sent at JMS 7 Priority MessagesSentAtJMS7PriorityCount MessagesSentAtJMS7Priority All Low
Messages Sent at JMS 6 Priority MessagesSentAtJMS6PriorityCount MessagesSentAtJMS6Priority All Low
Messages Sent at JMS 5 Priority MessagesSentAtJMS5PriorityCount MessagesSentAtJMS5Priority All Low
Messages Sent at JMS 4 Priority MessagesSentAtJMS4PriorityCount MessagesSentAtJMS4Priority All Low
Messages Sent at JMS 3 Priority MessagesSentAtJMS3PriorityCount MessagesSentAtJMS3Priority All Low
Messages Sent at JMS 2 Priority MessagesSentAtJMS2PriorityCount MessagesSentAtJMS2Priority All Low
Messages Sent at JMS 1 Priority MessagesSentAtJMS1PriorityCount MessagesSentAtJMS1Priority All Low
Messages Sent at JMS 0 Priority MessagesSentAtJMS0PriorityCount MessagesSentAtJMS0Priority All Low
Messages Received at JMS 9 Priority MessagesReceivedAtJMS9Priority Count MessagesReceivedAtJMS9Priority All Low
Messages Received at JMS 8 Priority MessagesReceivedAtJMS8Priority Count MessagesReceivedAtJMS8Priority All Low
Messages Received at JMS 7 Priority MessagesReceivedAtJMS7Priority Count MessagesReceivedAtJMS7Priority All Low
Messages Received at JMS 6 Priority MessagesReceivedAtJMS6Priority Count MessagesReceivedAtJMS6Priority All Low
Messages Received at JMS 5 Priority MessagesReceivedAtJMS5Priority Count MessagesReceivedAtJMS5Priority All Low
Messages Received at JMS 4 Priority MessagesReceivedAtJMS4Priority Count MessagesReceivedAtJMS4Priority All Low
Messages Received at JMS 3 Priority MessagesReceivedAtJMS3Priority Count MessagesReceivedAtJMS3Priority All Low
Messages Received at JMS 2 Priority MessagesReceivedAtJMS2Priority Count MessagesReceivedAtJMS2Priority All Low
Messages Received at JMS 1 Priority MessagesReceivedAtJMS1Priority Count MessagesReceivedAtJMS1Priority All Low
Messages Received at JMS 0 Priority MessagesReceivedAtJMS0Priority Count MessagesReceivedAtJMS0Priority All Low

Messaging Engine Communications ITM Table Name: KYNMECOM
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: SIB Communications > Messaging Engines > Standard Statistics
Messaging Engine Attached MEAttachedCount MEAttached All Low
API Connections APIConnectionsCount APIConnections All Low
Errors ErrorsCount Errors All Low
Writes WritesCount Writes All Low
Reads ReadsCount Reads All Low
Writes Blocked WritesBlockedCount WritesBlocked All Low
Reads Blocked ReadsBlockedCount ReadsBlocked All Low
Buffered Write (bytes) BufferedWriteBytesCount BufferedWriteBytes All Low
Buffered Reads (bytes) BufferedReadBytesCount BufferedReadBytes All Low
Message Written (bytes) MessageBytesWrittenCount MessageBytesWritten All Low
Message Read (bytes) MessageBytesReadCount MessageBytesRead All Low
Total Written (bytes) TotalBytesWrittenCount TotalBytesWritten All Low
Total Read (bytes) TotalBytesReadCount TotalBytesRead All Low

Durable Subscriptions ITM Table Name: KYNDURSUB
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: SIB Service > SIB Messaging Engines > Destinations > Topicspaces > Durable Subscriptions
Available Message AvailableMessageCount AvailableMessageCount All Low
Total Messages Consumed TotalMessagesConsumedCount TotalMessagesConsumedCount All Low
Best Effort Non-persistent Messages Consumed BestEffortNonPersistentMessages ConsumedCount BestEffortNonPersistentMessages ConsumedCount All Low
Express Non-persistent Messages Consumed ExpressNonPersistentMessages ConsumedCount ExpressNonPersistentMessages ConsumedCount All Low
Reliable Non-persistent Messages Consumed ReliableNonPersistentMessages ConsumedCount ReliableNonPersistentMessages ConsumedCount All Low
Reliable Persistent Messages Consumed ReliablePersistentMessages ConsumedCount ReliablePersistentMessages ConsumedCount All Low
Assured Persistent Messages Consumed AssuredPersistentMessages ConsumedCount AssuredPersistentMessages ConsumedCount All Low
Aggregate Message Wait Time AggregateMessageWaitTime AggregateMessageWaitTime All High
Local Message Wait Time LocalMessageWaitTime LocalMessageWaitTime All High
Local Oldest Message Age LocalOldestPublicationAge LocalOldestPublicationAge All Max

Queue ITM Table Name: KYNMSGQUE
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: SIB Service > SIB Messaging Engines > Destinations > Queues
Available Message AvailableMessageCount AvailableMessageCount All Low
Unavailable Message UnavailableMessageCount UnavailableMessageCount All Low
Local Producer Attaches LocalProducerAttachesCount LocalProducerAttachesCount All Low
Local Producer LocalProducerCount LocalProducerCount All Low
Local Consumer Attaches LocalConsumerAttachesCount LocalConsumerAttachesCount All Low
Local Consumer LocalConsumerCount LocalConsumerCount All Low
Total Messages Produced TotalMessagesProducedCount TotalMessagesProducedCount All Low
Best Effort Non-persistent Messages Produced BestEffortNonPersistentMessages ProducedCount BestEffortNonPersistentMessages ProducedCount All Low
Express Non-persistent Messages Produced ExpressNonPersistentMessages ProducedCount ExpressNonPersistentMessages ProducedCount All Low
Reliable Non-persistent Messages Produced ReliableNonPersistentMessages ProducedCount ReliableNonPersistentMessages ProducedCount All Low
Reliable Persistent Messages Produced ReliablePersistentMessages ProducedCount ReliablePersistentMessages ProducedCount All Low
Assured Persistent Messages Produced AssuredPersistentMessages ProducedCount AssuredPersistentMessages ProducedCount All Low
Total Messages Consumed TotalMessagesConsumedCount TotalMessagesConsumedCount All Low
Best Effort Non-persistent Messages Consumed BestEffortNonPersistentMessages ConsumedCount BestEffortNonPersistentMessages ConsumedCount All Low
Express Non-persistent Messages Consumed ExpressNonPersistentMessages ConsumedCount ExpressNonPersistentMessages ConsumedCount All Low
Reliable Non-persistent Messages Consumed ReliableNonPersistentMessages ConsumedCount ReliableNonPersistentMessages ConsumedCount All Low
Reliable Persistent Messages Consumed ReliablePersistentMessages ConsumedCount ReliablePersistentMessages ConsumedCount All Low
Assured Persistent Messages Consumed AssuredPersistentMessages ConsumedCount AssuredPersistentMessages ConsumedCount All Low
Report Enabled Messages Expired ReportEnabledMessages ExpiredCount ReportEnabledMessages ExpiredCount All Low
Aggregate Message Wait Time AggregateMessageWaitTime AggregateMessageWaitTime All Low
Local Message Wait Time LocalMessageWaitTime LocalMessageWaitTime All Low
Local Oldest Message Age LocalOldestMessageAge LocalOldestMessageAge All Low

Topic Spaces ITM Table Name: KYNTOPICSP
TEP Console Column Name WebSphere 7 PMI Attribute WebSphere 8 PMI Attribute WebSphere PMI Level Overhead
Category: SIB Service > SIB Messaging Engines > Destinations > Topicspaces
Incomplete Publication IncompletePublicationCount IncompletePublicationCount All Low
Local Publisher Attaches LocalPublisherAttachesCount LocalPublisherAttachesCount All Low
Local Publisher LocalPublisherCount LocalPublisherCount All Low
Total Local Subscription TotalLocalSubscriptionCount TotalLocalSubscriptionCount All Low
Non-durable Local Subscription NonDurableLocalSubscriptionCount NonDurableLocalSubscriptionCount All Low
Durable Local Subscription DurableLocalSubscriptionCount DurableLocalSubscriptionCount All Low
Total Messages Published TotalMessagesPublishedCount TotalMessagesPublishedCount All Low
Best Effort Non-persistent Messages Published BestEffortNonPersistentMessages PublishedCount BestEffortNonPersistentMessages PublishedCount All Low
Express Non-persistent Messages Published ExpressNonPersistentMessages PublishedCount ExpressNonPersistentMessages PublishedCount All Low
Reliable Non-persistent Messages Published ReliableNonPersistentMessages PublishedCount ReliableNonPersistentMessages PublishedCount All Low
Reliable Persistent Messages Published ReliablePersistentMessages PublishedCount ReliablePersistentMessages PublishedCount All Low
Assured Persistent Messages Published AssuredPersistentMessages PublishedCount AssuredPersistentMessages PublishedCount All Low
Total Local Subscription Hits TotalLocalSubscriptionHitCount TotalLocalSubscriptionHitCount All Low
Best Effort Non-persistent Local Subscription Hits BestEffortNonPersistentLocal SubscriptionHitCount BestEffortNonPersistentLocal SubscriptionHitCount All Low
Express Non-persistent Local Subscription Hits ExpressNonPersistentLocal SubscriptionHitCount ExpressNonPersistentLocal SubscriptionHitCount All Low
Reliable Non-persistent Local Subscription Hits ReliableNonPersistentLocal SubscriptionHitCount ReliableNonPersistentLocal SubscriptionHitCount All Low
Reliable Persistent Local Subscription Hits ReliablePersistentLocal SubscriptionHitCount ReliablePersistentLocal SubscriptionHitCount All Low
Assured Persistent Local Subscription Hits AssuredPersistentLocal SubscriptionHitCount AssuredPersistentLocal SubscriptionHitCount All Low
Report Enabled Publication Expired ReportEnabledPublications ExpiredCount ReportEnabledPublications ExpiredCount All Low
Local Oldest Publication Age LocalOldestPublicationAge LocalOldestPublicationAge All Max

Some attributes were renamed between WebSphere Application Server versions 7 and 8. The names for version 8 also apply to version 8.5.

Data sources for workspaces

Contents

Data sources for workspaces

ITCAM Agent for Application Diagnostics collects data from several sources on the application server. Different workspaces use data from different sources.

Types of data

The Agent collects the following four types of data:

Resource data
Request data
Data from WebSphere log files
Process data from the operating system

These four categories are based on the source from which the monitoring data is collected. The workspaces in the monitoring portal display data from these sources. Usually, each workspace displays data from one of the sources. Some workspaces contain summary information collected from one or more sources and processed by the Agent.

Resource Data

ITCAM Agent for WebSphere Applications obtains resource data from the Performance Monitoring Infrastructure (PMI) component that WebSphere Application Server provides. This data mostly contains usage and performance information about a resource in the system. For example, the "DB Connection Pools" workspace provides data about connection pool resources, including how long a connection is checked out, how many threads are waiting for connection, and so on.

Workspaces that display resource data, which is obtained from PMI.

Workspace Description
Web Applications workspace Displays performance data for each web application (.war). This data includes number of requests, average response time, and number of errors. Note that one Web application may have multiple URLs for user requests and the response times for all the requests are aggregated in this window.
Servlets/JSPs - Selected Web Application workspace Breaks down the performance data for a particular Web application into the servlets or JavaServer pages (JSPs) that it contains. Again, each servlet/JSP can contain or be mapped to multiple URLs and all user requests are combined.
Sessions workspace Provides information regarding HTTP sessions created by each Web application. HTTP sessions are used to maintain a user session between multiple invocations and stores user specific data. This workspace also displays the total, average, maximum, and minimum sizes of the user data stored for each Web application.
EJB Containers workspace Provides an overview of the performance of different types of Enterprise JavaBeans (EJBs) deployed in the application server.
Enterprise Java Beans workspace Displays the performance data for each EJB deployed in the application. Based on the Bean type, data is available in the appropriate columns.
Container Transactions workspace Provides performance data regarding Java Transaction API (JTA) transactions the EJBs are involved in.
Container Object Pools workspace Provides information about the behavior of stateless and entity bean pools.
DB Connection Pools workspace Displays the usage data regarding Database connection pools such as the number of connections available, checked out, threads waiting for a connection, and so on. This workspace is useful in understanding the pool usage and identifying potential bottlenecks in application performance when a thread is waiting or getting timed out for a connection from the pool.
J2C Connection Pools workspace Displays the usage data for connection pools set up for Java Connector Architecture (JCA) based resource adapters. The WebSphere Application Server creates connection pools for the resource adapters deployed (some of the adapters are provided by application server installation itself) and this workspace is useful in monitoring performance bottlenecks in terms of wait times to obtain a connection.
Pool Analysis workspace Provides information about the usage of several types of pools associated with each application server, including Web container pools, ORB pools, J2C connection pools, and database connection pools. This workspace helps you detect resource constraints and potential performance congestion.
Thread Pools workspace Displays the usage data for thread pools. The data can be used to determine whether the pool is configured correctly to service user requests. For example, the Web Container thread pool is used to execute servlet requests from the users and if the number of threads in the pool is small compared to the number of incoming requests, there will be a delay in servicing them leading to slower response times.
Thread Pool Trend workspace Displays trend information about thread pool size and usage.
Cache Analysis: Dynamic CacheCache Analysis workspace Provides the usage data of the various dynamic caches that have been configured in the system. In WebSphere Application Server 6.x and later, multiple caches can be configured.
Also provides the usage data for each dynamic cache template. The templates are unique IDs that are specified in the cachespec.xml files to identify different URLs that must be cached.
Workload Management workspace Workload management distributes the user requests made through the Object Request Broker (ORB) to different servers in a cluster. This usually means that this feature will come into play only when remote EJB calls are made over the ORB. This feature is applicable only in the ND (Network Deployment) environment when clusters are set up, so that the workload can be distributed when remote EJB calls are invoked over the ORB.
If the ORB is not used, this feature is not exercised and there will be no data in this workspace. If a server has both Servlets and EJBs on the same server instance, the calls are usually configured to be local calls instead of remote calls for better performance, and hence the ORB will not come into play. The server side data provides information about the number of requests received on the server side (for example, the EJB container receiving the user requests).
Scheduler workspace Scheduler service runs periodic tasks. Schedulers are persistent transactional timer services that run Enterprise JavaBean methods or send Java Message Service messages using any J2EE server application.
Web Services workspace Provides performance data on the Web Services hosted by the application server instance. Web Services provides data regarding number of Web services loaded, number of requests delivered, size of the requests, and so on.
Also includes information on the Web services gateway, which is used to map an existing service - either an inbound or an outbound service - to a new Web service that appears to be provided by the gateway. The gateway acts as a proxy: your gateway service users need not know whether the underlying service is being provided internally or externally. The gateway provides you with a single point of control, access and validation of Web service requests, and allows you to control which Web services are available to different groups of Web service users.
Workplace Mail workspace Provides aggregated statistics of the usage information about the incoming message traffic.
Messages Queues workspace Provides information about message delivery state, including ready retry, unprocessed, and dead.
Messaging workspace The messaging engines defined in various Service Integration Buses in this application server. Provides performance numbers on each messaging engine such as number of messages published. This workspace displays data only when a Service Integration Bus (SIB) is available in the system.
Client Communications workspace Provides communication details with distinct client processes that are currently network-connected to the Service Integration Buses of this application server. The data deals with messages sent and received from and to the various client processes.
Messaging Engine Communications workspace Provides information about other application servers that are hosting messaging engines and are network-connected to this application server. The Service Integration Bus is used to send and receive messages from these messaging engines.
Destinations workspace Provides performance data and counters for the destinations of a selected messaging engine. This includes the numbers of available and unavailable messages, numbers of messages produced and consumed, aggregated wait times and so on.
WMQ Client Link Communications workspace Provides information regarding communication to WebSphere MQ JMS clients that are connected to this application server.
WMQ Link Communications workspace Provides information regarding communication to WebSphere MQ JMS queue managers that are connected to this application server.
Alarm Manager workspace Provides aggregated information about the alarms for each work manager. This includes the number of alarms created, fired, canceled and so on.
DCS Stacks workspace Provides aggregated information about each DCS stack within the entire WebSphere Application Server domain, including multiple nodes and servers. This includes the incoming and outgoing message size, the number of incoming and outgoing messages, congestion events, and message buffer re-allocations.
Durable Subscriptions workspace Provides statistic counters for the durable subscriptions of a selected topic.
High Availability Manager workspace Provides aggregated information about high availability managers.
IMAP/POP workspace Provides aggregated statistics of the usage information about the IMAP service and the POP3 service connectivity, especially for the performance-related connectivity.
Service Components workspace Provides overview performance of the key service components. WebSphere servers feature their own service components, and each of these components has its own set of event points that can be monitored.
Service Component Elements workspace Lists performance metrics for all the service components and their elements. Service components contain one or more elements, which are sets of different steps processed in each service component. In turn, each element has its own set of event natures, which are key points that are reached when processing a service component element.

The availability of data in these workspaces depends on whether PMI is turned on in the WebSphere Application Server, and on the level of PMI data collection that is turned on.
PMI might be enabled at None, Basic, Extended, All, Custom levels. Each of these levels turns on a set of data counters. The higher level is inclusive of all the counters turned on at the lower level. As you go higher, the cost overhead for the collection increases. The "low" level incurs the least cost (usually obtains data that displays various "counts") and the "maximum" level incurs the highest cost (this, for example, returns time average data that requires extra memory and processing).
There is an additional "custom" level where individual data attributes can be turned on in addition to the data collection levels based on cost.
Hence, to view the Resource data in the portal workspaces, you will need to complete the following steps:

Have the appropriate resources defined. For example, JDBC providers and Datasources defined with connection pools to see data in DB Connection pools, Schedulers defined to see any data in the Schedulers workspace, and so on.
Turn on the PMI monitoring in the WebSphere Application Server (either through the admin console, wsadmin, or custom scripts).
Select the appropriate level of PMI data collection based on the desired data that needs to be monitored.

For a list of the PMI categories and attributes that the Agent workspaces and tables use.

Request Data

The Request data traces user transactions and measures the time to perform various activities (such as database access and JMS operations). Depending on the Request Data workspace, this information is grouped into various categories. For example, in the Request Analysis workspace the data is grouped by the request name (either the URL for servlets/JSPs or the EJB name) and in DataSources workspaces by the name of the Datasource.
The monitoring agent for WebSphere Application Server tracks the user transactions by modifying application and WebSphere system Java classes by adding method entry and exit "hooks". These hooks are callback methods into the ITCAM Data collector for WebSphere module that will track a user transaction as it travels through the classes in various modules (servlets, EJBs, Datasources, JMS, and so on). The application and WebSphere Application Server system Java classes are modified when they are loaded by WebSphere classloaders. During this load time, based on the type of class - Servlets, EJB, Datasource, JMS, JCA, JNDI, and so on - different callback methods are injected into the class using "Byte Code Modification" (BCM).

Workspaces that display request data, which is obtained through Byte Code Modification.

Workspace Monitor level Description
Request Analysis workspace Level 1 This workspace displays the number of user requests that were tracked during the sampling interval and their average response times. The requests are grouped by URLs for servlet calls and EJB names for direct EJB calls.
Request Baseline workspace Level 1 This workspace displays aggregated information about the request baseline. In the baselining process, the agent collects statistical information about a request completion times and uses this information to assign "fair" and "bad" thresholds for requests.
Request Analysis workspace Level 2 In addition to Level 1 data, the workspace also shows the breakdown of the response times into application, SQL Query, SQL Update, JCA, JMS, JNDI, SCA, web services processing times. This breakdown can be displayed in milliseconds and as a percentage of average response time.
Selected Request - Datasources workspace Level 2 To access this workspace, clicking the link icon on the row header of each row in the Request Analysis workspace. This workspace provides more details on the resources accessed by the selected user transaction - including the resource names, the average response time, and the longest response time during the sampling interval.
Data sources workspace Level 2 This workspace displays the time spent on various Data source operations. The operations include obtaining a connection, and executing a query or update. The workspace also shows the number of connections used during the sampling interval. The data in this workspace supplements the DB Connection Pools workspace by identifying the reason for long connection checkout times.
JMS Summary workspace Level 2 This workspace provides count and time measurements for JMS operations: send, receive, browse, and publish. It displays data on a queue and topic basis. The data provides a breakdown of the JMS delay shown in the Request Analysis workspace.

The Monitoring Level determines the amount of collected request data. At Level 2 the Agent collects more detailed data and incurs additional overhead in terms of memory and processing time. The default is Level 1. To change the value, use the Start_Request_Monitoring : Begin reporting request data Take Action command.
Another parameter that determines the amount of data collected is the Request Data Sampling Rate. It specifies the percentage of user requests that the Agent tracks and monitors. When the load on the system is very large, tracking every single user request becomes very expensive. Therefore, the Agent uses a sampling approach to monitor the performance of the applications. The default is 2% (i.e. only 2 out of every 100 user requests are tracked).
However, the load on your system might be very low (for example, in a test system you might apply a 10 user load). In this case, you might see no data in the Request Data workspaces with the default setting of 2%, as the probability of tracking one of the 10 requests will be very low. Hence, you need to increase the sampling rate in systems with low load. Use the Set_Request_Sampling_Rate: Set the sampling rate for request data Take Action command to do this.

Log File Data

ITCAM Agent for WebSphere Applications reads the application server log files and analyzes them to display data in several workspaces.

Workspaces that display log file data.

Workspace Log file Description
Garbage Collection Analysis workspace Native error file specified in application server configuration. The file name is set when configuring the Data Collector (the default is gc.log). ITCAM Agent for WebSphere Applications scans the verbose garbage collection (GC) log to provide information about how the GC is performing. This workspace can identify application performance issues when the GC consumes a lot of time. Such issues usually happen when the heap size parameters in the JVM are not set correctly. You can stop and start the collection of GC data using the Start_GC_Monitoring and Stop_GC_Monitoring Take Action commands.
the Take Action command does not turn on and off the verbose GC flag in WebSphere JVM. This flag is required for collection of GC data. You might need to enable or disable it using the application server admin console.
Allocation Failures workspace Same as Garbage Collection Analysis Provides information about heap allocation failures that cause the JVM to invoke garbage collection.
JVM Stack Trend workspace Same as Garbage Collection Analysis Provides trend data regarding JVM CPU usage, JVM garbage collection, and JVM heap usage. Displays Operating System data for CPU usage.
Log Analysis workspace SystemOut.log The Agent scans the application server SystemOut.log file and retrieves the messages for display in this workspace. Use the workspace to be informed about the health of the application server and also to create situations when certain message IDs are encountered.
Log Analysis workspace Data Collector message events Displays the Data Collector diagnostic messages, informing whether the Data Collector has initialized and is working correctly.

Application server process data from the operating system

ITCAM Agent for WebSphere Applications obtains the system CPU usage for the application server process by making operating system calls. This data is displayed in the Application Server Summary and Business Process Manager Summary workspaces in the CPU Used (ms) and CPU Used (%) columns. The JVM Stack Trend workspace also uses this data.
The OS Stack workspace displays detailed operating system performance information for the application server.

WebSphere summary and aggregated information

The following workspaces contain summary or aggregated information for WebSphere Application Server:

Workspaces that display summary and aggregated information.

Workspace Description
Application Server Summary and Business Process Manager Summary workspaces This workspace displays overall statistic information for each application server that is monitored by the agent. The information includes history of heap usage, response times, request rates, and % CPU used.
WebSphere Agent workspace This workspace displays events occurring within the agent and all the application servers on the host. It also displays status information about the agent and the online/offline status of the monitored servers.
EJB Tier Analysis workspace The workspace displays information about the health of a WebSphere application based on response time and completion rates for EJB requests. It also displays ORB thread pool information and PMI information related to EJB requests.
Backend Tier Analysis workspace The workspace displays information about the health of a WebSphere application based on response time for Backend Tier requests. It also displays information about backend tier resources, including Data Sources, JMS resources, JDBC and JCA Pools, and JVM statistics.
Web Tier Analysis workspace The workspace displays information about the health of a WebSphere application based on response time and completion rates for Web Tier requests. It also displays WebContainer thread pool information and PMI information related to HTTP sessions.

z/OS region workspaces

In a z/OS environment, most workspace tables report data at both a region and server instance level. The advantage is that you can view metrics collected at both levels and switch between server instance lever and region level.

Data Display Problems

If you do not see data in the portal workspaces, use the following checklist to verify the settings.

Workspace Checkpoint Comments
All Workspaces The application server is running and the monitoring agent is connected to it Check that the Status column in the Application Server Summary and Business Process Manager Summary workspaces shows Connected.
All Workspaces There is user load applied on the application server The Request data workspaces display data only when user load is applied. The Resource data workspaces still display data rows even if load is not applied, but the columns will either be empty or display zeros. The data rows in this case are created from the application server configuration information about the resource type.
Request Data Workspaces Request Data collection is turned on Verify by checking the Request Data Monitoring Level column in the Application Server Summary workspace is not Disabled. If it is Disabled, start the monitoring by using the Start_Request_Monitoring : Begin reporting request data Take Action command.
Request Data Workspaces Sampling rate is high enough The default sampling rate is 2%. If the load on the application server is low, the Agent might fail to track user transactions. Verify the sampling rate in the Request Data Sampling Rate(%) column in the Application Server Summary and Business Process Manager Summary workspaces. Set the rate higher by using the Set_Request_Sampling_Rate: Set the sampling rate for request data Take Action command.
Data sources workspace Request Data Monitoring Level is set to Level 2 The Request Data Monitoring Level column in Application Server Summary and Business Process Manager Summary workspaces workspace displays the value. To change the monitoring level, use the Start_Request_Monitoring : Begin reporting request data Take Action command.
Data sources workspace Data sources are configured in the application server; user requests are accessing these Data sources To check the presence of Data sources, use the application server admin console. You need to know application logic to verify whether the user requests are accessing the Data sources. Check DB Connection Pools workspace for activity with the Data sources.
JMS Summary workspace JMS resources (queues, topics) are configured and applications are accessing these resources To check the existence of JMS resources, use the admin console. You need to know application logic to verify whether these resources are used.
Resource Data Workspaces Feature is available Verify the application server feature is being used. For example, Dynamic cache data will be available only when the cache feature has been set up. All "Platform Messaging" workspaces will be available only when the Service Integration Bus has been configured and used.
Resource Data Workspaces PMI is enabled in the application server Verify PMI is enabled through the administration console of WebSphere Application Server. Make sure PMI is enabled for the desired modules (for example, WebApplications, ServletSessions, EJBContainer, and so on). To do this, check the Runtime tab of the Performance Monitoring Infrastructure page in the application server admin console.
Resource Data Workspaces Data not available in certain columns Verify PMI level is high enough to capture data for these columns. Check the Instrumentation Level column in the workspace that you need to view.
Change the PMI level through the application server admin console. The contextual help on the data columns in portal workspace specifies the PMI level at which data will be available.
Resource Data Workspaces Resource Data Monitoring is turned on The Resource Data Monitoring column in Application Server Summary and Business Process Manager Summary workspaces must say Enabled. If it is set to Disabled, turn it on using the Start_Resource_Monitoring: Begin reporting PMI data Take Action command.
Garbage Collection Analysis workspace Verbose GC flag is turned on in WAS Verify the Verbose GC box is checked in the Application Server->Process Definition->Java Virtual Machine page of the admin console.
Garbage Collection Analysis workspace Garbage Collection Monitoring is enabled The Garbage Collection Monitoring column in Application Server Summary and Business Process Manager Summary workspaces must be Enabled. If it set to Disabled, use the Start_GC_Monitoring: Begin reporting garbage-collection data Take Action command to start it.
the Take Action command will not enable the verbose GC flag in the application server. You have to do it separately.

WebSphere PMI Attribute Mapping

Contents

WebSphere PMI Attribute Mapping

The tables in this appendix are invaluable in showing how the data displayed in the ITCAM for Application Diagnostics resource workspaces map to their corresponding WebSphere PMI categories and their attributes. It also provides the monitoring overhead incurred when turning on these attributes. By default, ITCAM changes the PMI collection level based on its monitoring level. Go to the ITCAM for Application Diagnostics infocenter and search for "Modifying PMI Settings" to learn more about this behavior and how to turn to turn it off for custom monitoring.

TEP Console Workspace Columns to WebSphere PMI Attribute Mapping

AppServer--High Availability Manager ITM Table Name: KYNHAMGMT
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: HAManager
Local Groups LocalGroupCount All All High
Group State Rebuild Time GroupStateRebuildTime All All High
Bulletin-Board Subjects BulletinBoardSubjectCount All All High
Bulletin-Board Subscriptions BulletinBoardSubcriptionCount All All High
Bulletin-Board Rebuild Time BulletinBoardRebuildTime All All High
Local Bulletin-Board Subjects LocalBulletinBoardSubjectCount All All High

AppServer-DCS Stacks ITM Table Name: KYNDCSSTK
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: DCS Statistics
Message Buffer Reallocations MessageBufferReallocationCount All All Medium
Sent Messages SentMessageCount All All High
Average Outgoing Message Size OutgoingMessageSize All All High
Minimum Outgoing Message Size OutgoingMessageSize All All High
Maximum Outgoing Message Size OutgoingMessageSize All All High
Outgoing Messages SentMessageCount All All High
Average Incoming Message Size IncomingMessageSize All All High
Minimum Incoming Message Size IncomingMessageSize All All High
Maximum Incoming Message Size IncomingMessageSize All All High
Incoming Messages ReceivedMessageCount All All High
Synchronization Completion Time SynchronizationCompleteTime All All High
Synchronization Timeouts SynchronizationTimeoutCount All All Medium
High Severity Congestion Events HighSeverityCongestionEvent Count All All Medium
Coalesce Time CoalesceTime All All Medium
Join View Change Time JoinViewChangeTime All All High
Remove View Change Time RemoveViewChangeTime All All High
Suspicions SuspicionCount All All High
View Changes ViewChangeCount All All Medium
Group Size ViewGroupSize All All Medium

Web Applications ITM Table Name: KYNAPP
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Web Applications
Request Count RequestCount (Servlet Info) Basic Basic Low
Request Rate (per sec) RequestCount Basic Basic Low
Error Count ErrorCount (Servlet Info) Extended Extended Low
Error Rate (per sec) ErrorCount (Servlet Info) Extended Extended Low
Average Response Time (ms) ServiceTime (Servlet Info) Basic Basic Medium
Average Concurrent Requests ConcurrentRequests (Servlet Info) Extended Extended High
Servlets Loaded LoadedServletCount All All Low
Servlets Reloaded ReloadCount All All Low

WebApplications --ServletSessions ITM Table Name: KYNSERVS
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Servlet Session Manager
Sessions Created CreateCount All All Low
Session Creation Rate (per sec) CreateCount All All Low
Sessions Invalidated InvalidateCount All All Low
Session Invalidation Rate (per sec) InvalidateCount All All Low
Average Session Lifetime (ms) LifeTime Extended Extended Medium
Average Concurrently Active Sessions ActiveCount All All High
Average Concurrently Live Sessions LiveCount Basic Basic High
Failed Session Requests NoRoomForNewSessionCount Extended Extended Low
Failed Session Request Rate (per sec) NoRoomForNewSessionCount Extended Extended Low
Cache Discards CacheDiscardCount All All Low
Cache Discard Rate (per sec) CacheDiscardCount All All Low
External Read Time (ms) ExternalReadTime Extended Extended Medium
External Read Size (bytes) ExternalReadSize Extended Extended Medium
External Write Time (ms) ExternalWriteTime Extended Extended Medium
External Write Size (bytes) ExternalWriteSize Extended Extended Medium
Broken Session Affinities AffinityBreakCount All All Low
Broken Session Affinity Rate (per sec) AffinityBreakCount All All Low
Time since Last Activated TimeSinceLastActivated All All Medium
Nonexistent Session Requests ActivateNonExistSessionCount All All Low
Nonexistent Session Request Rate (per sec) ActivateNonExistSessionCount All All Low
Total Serializable Session Object Size (bytes) SessionObjectSize All All Max
Average Serializable Session Object Size (bytes) SessionObjectSize All All Max
Min Serializable Session Object Size (bytes) SessionObjectSize All All Max
Max Serializable Session Object Size (bytes) SessionObjectSize All All Max

EJB Containers ITM Table Name: KYNCONTNR
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Enterprise Beans
Method Average Response Time (ms) MethodResponseTime Basic Basic High
Method Invocation Count MethodCallCount Basic Basic High
Method Invocation Rate (per sec) MethodCallCount Basic Basic High
Create Average Time (ms) CreateTime All All Max
Remove Average Time (ms) RemoveTime All All Max
Average Concurrently Ready Beans ReadyCount Basic Basic Low
Average Concurrently Live Beans LiveCount Extended Extended High
Active Method Count ActiveMethodCount All All High
Create Count CreateCount Basic Basic Low
Creation Rate (per sec) CreateCount Basic Basic Low
Remove Count RemoveCount Basic Basic Low
Removal Rate per sec) RemoveCount Basic Basic Low
Activate Count ActivateCount All All Low
Activation Rate (per sec) ActivateCount All All Low
Passivate Count PassivateCount Basic Basic Low
Passivation Rate (per sec) PassivateCount Basic Basic Low
Entity Bean Load Count LoadCount All All Low
Entity Bean Load Rate (per sec) LoadCount All All Low
Entity Bean Store Count StoreCount All All Low
Entity Bean Store Rate (per sec) StoreCount All All Low
Instantiate Count InstantiateCount All All Low
Instantiation Rate (per sec) InstantiateCount All All Low
Destroy Count FreedCount All All Low
Destruction Rate (per sec) FreedCount All All Low

EJB Containers ---Enterprise Java Beans ITM Table Name: KYNEJB
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Enterprise Beans
Method Invocations MethodCallCount Basic Basic High
Method Invocation Rate (per sec) MethodCallCount Basic Basic High
Method Average Response Time (ms) MethodResponseTime Basic Basic High
Create Count CreateCount Basic Basic Low
Creation Rate (per sec) CreateCount Basic Basic Low
Create Average Time (ms) CreateTime All All Max
Remove Count RemoveCount Basic Basic Low
Removal Rate (per sec) RemoveCount Basic Basic Low
Remove Average Time (ms) RemoveTime All All Max
Activate Count ActivateCount All All Low
Activation Rate (per sec) ActivateCount All All Low
Passivate Count PassivateCount All All Low
Passivation Rate PassivateCount All All Low
Entity Bean Load Count LoadCount All All Low
Entity Bean Load Rate (per sec) LoadCount All All Low
Entity Bean Store Count StoreCount All All Low
Entity Bean Store Rate (per sec) StoreCount All All Low
Instantiate Count InstantiateCount All All Low
Destroy Count FreedCount All All Low
Destruction Rate (per sec) FreedCount All All Low
Find Count RetrieveFromPoolSuccessCount All All Low
Find Rate (per sec) RetrieveFromPoolSuccessCount All All Low
Get Count RetrieveFromPoolCount All All Low
Get Rate (per sec) RetrieveFromPoolCount All All Low
Return Count ReturnsToPoolCount Extended Extended Low
Return Rate (per sec) ReturnsToPoolCount Extended Extended Low
Discard Count ReturnsDiscardCount Extended Extended Low
Discard Rate (per sec) ReturnsDiscardCount Extended Extended Low
Drain Count DrainsFromPoolCount All All Low
Drain Rate (per sec) DrainsFromPoolCount All All Low
Average Concurrently Ready Beans ReadyCount Basic Basic High
Average Concurrently Live Beans LiveCount Extended Extended High
Active Method Count ActiveMethodCount All All High
Average Objects Discarded DrainSize All All Medium
Average Objects in Pool PooledCount Basic Basic High

EJB Containers ---Container Transactions EJB Containers---Container Transactions
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Transaction Manager
Global Transactions Begun GlobalBegunCount Extended Extended Low
Global Transactions Begin Rate (per sec) GlobalBegunCount Extended Extended Low
Local Transactions Begun LocalBegunCount Extended Extended Low
Local Transactions Begin Rate (per sec) LocalBegunCount Extended Extended Low
Global Transactions Active ActiveCount Basic Basic Low
Local Transactions Active LocalActiveCount All All Low
Global Transactions Committed CommittedCount Basic Basic Low
Global Transaction Commit Rate (per sec) CommittedCount Basic Basic Low
Local Transactions Committed LocalCommittedCount All All Low
Local Transaction Commit Rate (per sec) LocalCommittedCount All All Low
Global Transactions Rolled Back RolledbackCount Basic Basic Low
Global Transaction Rollback Rate (per sec) RolledbackCount Basic Basic Low
Local Transactions Rolled Back LocalRolledbackCount All All Low
Local Transaction Rollback Rate (per sec) LocalRolledbackCount All All Low
Global Transaction Timeouts GlobalTimeoutCount Extended Extended Low
Global Transaction Timeout Rate (per sec) GlobalTimeoutCount Extended Extended Low
Local Transaction Timeouts LocalTimeoutCount Extended Extended Low
Local Transaction Timeout Rate (per sec) LocalTimeoutCount Extended Extended Low
Global Transactions Optimized OptimizationCount All All Low
Global Transaction Optimize Rate (per sec) CommittedCount Basic Basic Low
Global Transactions Involved GlobalInvolvedCount All All Low
Global Transactions Involve Rate (per sec) GlobalInvolvedCount All All Low
Global Transaction Duration (ms) GlobalTranTime Extended Extended Medium
Local Transaction Duration (ms) LocalTranTime Extended Extended Medium
Global Transaction before Completion Duration (ms) GlobalBeforeCompletionTime All All Medium
Local Transaction before Completion Duration (ms) LocalBeforeCompletionTime All All Medium
Global Transaction Commit Duration (ms) GlobalCommitTime All All Medium
Local Transaction Commit Duration (ms) LocalCommitTime All All Medium
Global Transaction Prepare Duration (ms) GlobalPrepareTime All All Medium

EJB Containers ---Container Object Pools ITM Table Name: KYNCNTROP
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead

Average Objects in Pool PooledCount Basic Basic High
Average Objects Discarded DrainSize All All Medium
Find Count RetrieveFromPoolSuccessCount All All Low
Find Rate RetrieveFromPoolSuccessCount All All Low
Get Count RetrieveFromPoolCount All All Low
Get Rate RetrieveFromPoolCount All All Low
Return Count ReturnsToPoolCount Extended Extended Low
Return Rate ReturnsToPoolCount Extended Extended Low
Discard Count ReturnsDiscardCount Extended Extended Low
Discard Rate ReturnsDiscardCount Extended Extended Low
Drain Count DrainsFromPoolCount All All Low
Drain Rate DrainsFromPoolCount All All Low

DB Connection Pools ITM Table Name: KYNDBCONP
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: JDBC Connection Pools
Maximum Pool Size PoolSize Basic Basic High
Average Pool Size PoolSize Basic Basic High
Average Waiting Threads WaitingThreadCount Basic Basic High
Average Wait Time (ms) WaitTime Basic Basic Medium
Average Usage Time (ms) UseTime Basic Basic Medium
Average Free Pool Size FreePoolSize Basic Basic High
JDBC Time(ms) JDBCTime Extended Extended Medium
Percent Used PercentUsed Basic Basic High
Percent of Time Pool at Max PercentMaxed All All High
Connections Created CreateCount Basic Basic Low
Connection Creation Rate (per sec) CreateCount Basic Basic Low
Connections Allocated AllocateCount All Extended Low
Connection Allocation Rate (per sec) AllocateCount All Extended Low
Connections Destroyed CloseCount Basic Basic Low
Connection Destruction Rate (per sec) CloseCount Basic Basic Low
Threads Timed Out FaultCount Extended Extended Low
Thread Timeout Rate (per sec) FaultCount Extended Extended Low
Prep Statement Cache Discards PrepStmtCacheDiscardCount Extended Extended Low
Prep Statement Cache Discard Rate (per sec) PrepStmtCacheDiscardCount Extended Extended Low
Return Count ReturnCount All Extended Low
Return Rate(per sec) ReturnCount All Extended Low

J2C Connection Pools ITM Table Name: KYNJ2C
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: J2C Connection Pools
Maximum Pool Size PoolSize Basic Basic High
Average Pool Size PoolSize Basic Basic High
Average Free Connections FreePoolSize Basic Basic High
Connections Used ManagedConnectionCount All All Low
Connection Handles ConnectionHandleCount All All Low
Average Wait Time (ms) WaitTime Basic Basic Medium
Concurrent Waiting Threads WaitingThreadCount Basic Basic High
Average Usage Time (ms) UseTime Basic Basic Medium
Pool Used (%) PercentUsed All All High
Percent of Time Pool at Max PercentMaxed All All High
Connections Created CreateCount Basic Basic Low
Connection Creation Rate (per sec) CreateCount Basic Basic Low
Connections Allocated AllocateCount All All Low
Connection Allocation Rate (per sec) AllocateCount All All Low
Connections Returned FreedCount All All Low
Connection Return Rate (per sec) FreedCount All All Low
Connections Destroyed CloseCount Basic Basic Low
Connection Destruction Rate (per sec) CloseCount Basic Basic Low
Connection Pool Timeouts FaultCount All All Low
Connection Pool Timeout Rate (per sec) FaultCount All All Low

Thread Pools Table Name: KYNTHRDP
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Thread Pools
Maximum Pool Size PoolSize Basic Basic High
Average Pool Size PoolSize Basic Basic High
Average Active Threads ActiveCount Extended Extended High
Average Free Threads PoolSize - ActiveCount Extended Extended High
Percent of Time Pool at Max PercentMaxed All All High
Threads Created CreateCount All All Low
Thread Creation Rate (per sec) CreateCount All All Low
Threads Destroyed DestroyCount All All Low
Thread Destruction Rate (per sec) DestroyCount All All Low

Thread Pools ---Alarm Manager ITM Table Name: KYNALARMM
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Alarm Manager
Alarms Cancelled AlarmsCancelledCount All All High
Alarms Latency Duration AlarmLatencyDuration All All High
Alarms Rate AlarmRate All All High
Alarms Created AlarmsCreatedCount All All High
Alarms Fired AlarmsFiredCount All All High
Alarms Pending Size AlarmsPendingSize All All High

Dynamic Cache ITM Table Name: KYNCACHE
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Dynamic Caching
Maximum In-Memory Cache Size MaxInMemoryCacheEntryCount All All Low
Current In-Memory Cache Size InMemoryCacheEntryCount All All Low
In-Memory and Disk Timeouts TimeoutInvalidationCount All All Low
In-Memory and Disk Timeout Rate (per sec) TimeoutInvalidationCount All All Low

Dynamic Cache Templates ITM Table Name: KYNCACHT
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Templates
Current Cache Size InMemoryAndDiskCacheEntry Count All All Low
Disk Hits HitsOnDiskCount All All Low
Disk Hit Rate(per sec) HitsOnDiskCount All All Low
Memory Hits HitsInMemoryCount Extended Extended Low
Memory Hit Rate(per sec) HitsInMemoryCount Extended Extended Low
Remote Hits RemoteHitCount All All Low
Remote Hit Rate(per sec) RemoteHitCount All All Low
Cache Misses MissCount Extended Extended Low
Cache Miss Rate(per sec) MissCount Extended Extended Low
Remote Cache Entries Received RemoteCreationCount All All Low
Remote Cache Entry Receive Rate(per sec) RemoteCreationCount All All Low
Client Requests ClientRequestCount All All Low
Client Request Rate(per sec) ClientRequestCount All All Low
Cluster Requests DistributedRequestCount All All Low
Cluster Request Rate(per sec) DistributedRequestCount All All Low
Total Explicit Invalidations ExplicitInvalidationCount All All Low
Total Explicit Invalidation Rate(per sec) ExplicitInvalidationCount All All Low
Timeout Invalidations TimeoutInvalidationCount All All Low
Timeout Invalidation Rate(per sec) TimeoutInvalidationCount All All Low
Least Recently Used Invalidations LruInvalidationCount All All Low
Least Recently Used Invalidation Rate(per sec) LruInvalidationCount All All Low
Explicit Memory Invalidations ExplicitMemoryInvalidationCount All All Low
Explicit Memory Invalidation Rate(per sec) ExplicitMemoryInvalidationCount All All Low
Explicit Disk Invalidations ExplicitDiskInvalidationCount All All Low
Explicit Disk Invalidations Rate(per sec) ExplicitDiskInvalidationCount All All Low
Explicit Local Invalidations LocalExplicitInvalidationCount All All Low
Explicit Local Invalidation Rate(per sec) LocalExplicitInvalidationCount All All Low
Explicit Remote Invalidations RemoteExplicitInvalidationCount All All Low
Explicit Remote Invalidation Rate(per sec) RemoteExplicitInvalidationCount All All Low

Workload Management Client ITM Table Name: KYNWLMCL
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Workload Management client
Outgoing Requests OutgoingIIOPRequestCount All All Low
Outgoing Request Rate (per sec) OutgoingIIOPRequestCount All All Low
Client Cluster Updates ClientClusterUpdateCount All All Low
Client Cluster Update Rate (per sec) ClientClusterUpdateCount All All Low
Client Response Time ClientResponseTime All All Medium

Workload Management Server ITM Table Name: KYNWLMSR
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Workload Management server
Incoming Requests IIOPRequestCount Extended Extended Low
Incoming Request Rate (per sec) IIOPRequestCount Extended Extended Low
Incoming Strong Affinity Requests StrongAffinityIIOPRequestCount All All Low
Incoming Strong Affinity Request Rate (per sec) StrongAffinityIIOPRequestCount All All Low
Incoming Nonaffinity Requests NoAffinityIIOPRequestCount All All Low
Incoming Nonaffinity Request Rate (per sec) NoAffinityIIOPRequestCount All All Low
Incoming Non-WLM Object Requests NonWLMEnabledIIOPRequest Count All All Low
Incoming Non-WLM Object Request Rate (per sec) NonWLMEnabledIIOPRequest Count All All Low
Server Cluster Updates ServerClusterUpdateCount All All Low
Server Cluster Update Rate (per sec) ServerClusterUpdateCount All All Low
WLM Clients Serviced WLMClientsServicedCount All All Low
WLM Clients Serviced Rate (per sec) WLMClientsServicedCount All All Low
Concurrent Requests ConcurrentRequestCount Extended Extended High
Server Response Time (ms) ServerResponseTime Extended Extended Medium

Scheduler ITM Table Name: KYNSCHED
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Schedulers
Poll Count PollCount All All High
Poll Duration PollDuration All All High
Poll Query Duration PollQueryDuration All All High
Run Duration RunDuration All All High
Task Collision Rate TaskCollisionRate All All High
Task Delay Duration TaskDelayDuration All All High
Task Expiration Rate TaskExpirationRate All All High
Task Failure Count TaskFailureCount All All High
Task Finish Count TaskFinishCount All All High
Task Finish Rate TaskFinishRate All All High
Task Run Rate TaskRunRate All All High

Web Services ITM Table Name: KYNWEBSVC
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Web services
Received Requests ReceivedRequestCount All All Low
Dispatched Requests DispatchedRequestCount All All Low
Processed Requests ProcessedRequestCount All All Low
Response Time ResponseTime All All High
Request Response Time RequestResponseTime All All Medium
Dispatch Response Time DispatchResponseTime All All Medium
Reply Response Time ReplyResponseTime All All Medium
Payload Size PayloadSize All All Medium
Reply Payload Size ReplyPayloadSize All All Medium
Request Payload Size RequestPayloadSize All All Medium

WebServices Gateway ITM Table Name: KYNWEBSGW
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Web services Gateway
Synchronous Requests SynchronousRequestCount All All Low
Synchronous Responses SynchronousResponseCount All All Low
Asynchronous Requests AsynchronousRequestCount All All Low
Asynchronous Responses AsynchronousResponseCount All All Low

Messaging Engines ITM Table Name: KYNMSGENG
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: SIB Service > SIB Messaging Engines
Average Local Wait Time (ms) LocalMessageWaitTime All All Low
Expired Messages ReportEnabledMessagesExpired Count All All Low
Incomplete Topic Publications IncompletePublicationCount All All Low
Total Published TotalMessagesPublishedCount All All Low

Client Communications ITM Table Name: KYNCLICOM
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: Standard Statistics
Clients Attached ClientsAttachedCount All All Low
API Connections APIConnectionsCount All All Low
Errors ErrorsCount All All Low
Writes WritesCount All All Low
Reads ReadsCount All All Low
Writes Blocked WritesBlockedCount All All Low
Reads Blocked ReadsBlockedCount All All Low
Multicast Write (bytes) MulticastWriteBytesCount All All Low
Multicast Send Messages MulticastSendMessageCount All All Low
Buffered Write (bytes) BufferedWriteBytesCount All All Low
Buffered Read (bytes) BufferedReadBytesCount All All Low
Message Written (bytes) MessagesBytesWrittenCount All All Low
Message Read (bytes) MessageBytesReadCount All All Low
Total Written (bytes) TotalBytesWrittenCount All All Low
Total Read (bytes) TotalBytesReadCount All All Low
Category: Detailed Statistics
Sent at Highest Priority (bytes) BytesSentAtHighestPriorityCount All All Low
Sent at Very High Priority (bytes) BytesSentAtVeryHighPriorityCount All All Low
Sent at High Priority (bytes) BytesSentAtHighPriorityCount All All Low
Sent at JMS 9 Priority (bytes) BytesSentAtJMS9PriorityCount All All Low
Sent at JMS 8 Priority (bytes) BytesSentAtJMS8PriorityCount All All Low
Sent at JMS 7 Priority (bytes) BytesSentAtJMS7PriorityCount All All Low
Sent at JMS 6 Priority BytesSentAtJMS6PriorityCount All All Low
Sent at JMS 5 Priority (bytes) BytesSentAtJMS5PriorityCount All All Low
Sent at JMS 4 Priority (bytes) BytesSentAtJMS4PriorityCount All All Low
Sent at JMS 3 Priority (bytes) BytesSentAtJMS3PriorityCount All All Low
Sent at JMS 2 Priority (bytes) BytesSentAtJMS2PriorityCount All All Low
Sent at JMS 1 Priority (bytes) BytesSentAtJMS1PriorityCount All All Low
Sent at JMS 0 Priority (bytes) BytesSentAtJMS0PriorityCount All All Low
Sent at Low Priority (bytes) BytesSentAtLowPriorityCount All All Low
Sent at Very Low Priority (bytes) BytesSentAtVeryLowPriorityCount All All Low
Sent at Lowest Priority (bytes) BytesSentAtLowestPriorityCount All All Low
Received at Highest Priority (bytes) BytesReceivedAtHighestPriority Count All All Low
Received at Very High Priority (bytes) BytesReceivedAtVeryHighPriority Count All All Low
Received at High Priority (bytes) BytesReceivedAtHighPriorityCount All All Low
Received at JMS 9 Priority (bytes) BytesReceivedAtJMS9PriorityCount All All Low
Received at JMS 8 Priority (bytes) BytesReceivedAtJMS8PriorityCount All All Low
Received at JMS 7 Priority (bytes) BytesReceivedAtJMS7PriorityCount All All Low
Received at JMS 6 Priority (bytes) BytesReceivedAtJMS6PriorityCount All All Low
Received at JMS 5 Priority (bytes) BytesReceivedAtJMS5PriorityCount All All Low
Received at JMS 4 Priority (bytes) BytesReceivedAtJMS4PriorityCount All All Low
Received at JMS 3 Priority (bytes) BytesReceivedAtJMS3PriorityCount All All Low
Received at JMS 2 Priority (bytes) BytesReceivedAtJMS2PriorityCount All All Low
Received at JMS 1 Priority (bytes) BytesReceivedAtJMS1PriorityCount All All Low
Received at JMS 0 Priority (bytes) BytesReceivedAtJMS0PriorityCount All All Low
Received at Low Priority (bytes) BytesReceivedAtLowPriorityCount All All Low
Received at Very Low Priority (bytes) BytesReceivedAtVeryLowPriority Count All All Low
Received at Lowest Priority (bytes) BytesReceivedAtLowestPriority Count All All Low
Messages Sent at JMS 9 Priority MessagesSentAtJMS9PriorityCount All All Low
Messages Sent at JMS 8 Priority MessagesSentAtJMS8PriorityCount All All Low
Messages Sent at JMS 7 Priority MessagesSentAtJMS7PriorityCount All All Low
Messages Sent at JMS 6 Priority MessagesSentAtJMS6PriorityCount All All Low
Messages Sent at JMS 5 Priority MessagesSentAtJMS5PriorityCount All All Low
Messages Sent at JMS 4 Priority MessagesSentAtJMS4PriorityCount All All Low
Messages Sent at JMS 3 Priority MessagesSentAtJMS3PriorityCount All All Low
Messages Sent at JMS 2 Priority MessagesSentAtJMS2PriorityCount All All Low
Messages Sent at JMS 1 Priority MessagesSentAtJMS1PriorityCount All All Low
Messages Sent at JMS 0 Priority MessagesSentAtJMS0PriorityCount All All Low
Messages Received at JMS 9 Priority MessagesReceivedAtJMS9Priority Count All All Low
Messages Received at JMS 8 Priority MessagesReceivedAtJMS8Priority Count All All Low
Messages Received at JMS 7 Priority MessagesReceivedAtJMS7Priority Count All All Low
Messages Received at JMS 6 Priority MessagesReceivedAtJMS6Priority Count All All Low
Messages Received at JMS 5 Priority MessagesReceivedAtJMS5Priority Count All All Low
Messages Received at JMS 4 Priority MessagesReceivedAtJMS4Priority Count All All Low
Messages Received at JMS 3 Priority MessagesReceivedAtJMS3Priority Count All All Low
Messages Received at JMS 2 Priority MessagesReceivedAtJMS2Priority Count All All Low
Messages Received at JMS 1 Priority MessagesReceivedAtJMS1Priority Count All All Low
Messages Received at JMS 0 Priority MessagesReceivedAtJMS0Priority Count All All Low

Messaging Engine Communications ITM Table Name: KYNMECOM
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: SIB Communications > Messaging Engines > Standard Statistics
Messaging Engine Attached MEAttachedCount All All Low
API Connections APIConnectionsCount All All Low
Errors ErrorsCount All All Low
Writes WritesCount All All Low
Reads ReadsCount All All Low
Writes Blocked WritesBlockedCount All All Low
Reads Blocked ReadsBlockedCount All All Low
Buffered Write (bytes) BufferedWriteBytesCount All All Low
Buffered Reads (bytes) BufferedReadBytesCount All All Low
Message Written (bytes) MessageBytesWrittenCount All All Low
Message Read (bytes) MessageBytesReadCount All All Low
Total Written (bytes) TotalBytesWrittenCount All All Low
Total Read (bytes) TotalBytesReadCount All All Low

Durable Subscriptions ITM Table Name: KYNDURSUB
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: SIB Service > SIB Messaging Engines > Destinations > Topicspaces > Durable Subscriptions
Available Message AvailableMessageCount All All Low
Total Messages Consumed TotalMessagesConsumedCount All All Low
Best Effort Non-persistent Messages Consumed BestEffortNonPersistentMessages ConsumedCount All All Low
Express Non-persistent Messages Consumed ExpressNonPersistentMessages ConsumedCount All All Low
Reliable Non-persistent Messages Consumed ReliableNonPersistentMessages ConsumedCount All All Low
Reliable Persistent Messages Consumed ReliablePersistentMessages ConsumedCount All All Low
Assured Persistent Messages Consumed AssuredPersistentMessages ConsumedCount All All Low
Aggregate Message Wait Time AggregateMessageWaitTime All All High
Local Message Wait Time LocalMessageWaitTime All All High
Local Oldest Message Age LocalOldestPublicationAge All All Max

Queue ITM Table Name: KYNMSGQUE
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: SIB Service > SIB Messaging Engines > Destinations > Queues
Available Message AvailableMessageCount All All Low
Unavailable Message UnavailableMessageCount All All Low
Local Producer Attaches LocalProducerAttachesCount All All Low
Local Producer LocalProducerCount All All Low
Local Consumer Attaches LocalConsumerAttachesCount All All Low
Local Consumer LocalConsumerCount All All Low
Total Messages Produced TotalMessagesProducedCount All All Low
Best Effort Non-persistent Messages Produced BestEffortNonPersistentMessages ProducedCount All All Low
Express Non-persistent Messages Produced ExpressNonPersistentMessages ProducedCount All All Low
Reliable Non-persistent Messages Produced ReliableNonPersistentMessages ProducedCount All All Low
Reliable Persistent Messages Produced ReliablePersistentMessages ProducedCount All All Low
Assured Persistent Messages Produced AssuredPersistentMessages ProducedCount All All Low
Total Messages Consumed TotalMessagesConsumedCount All All Low
Best Effort Non-persistent Messages Consumed BestEffortNonPersistentMessages ConsumedCount All All Low
Express Non-persistent Messages Consumed ExpressNonPersistentMessages ConsumedCount All All Low
Reliable Non-persistent Messages Consumed ReliableNonPersistentMessages ConsumedCount All All Low
Reliable Persistent Messages Consumed ReliablePersistentMessages ConsumedCount All All Low
Assured Persistent Messages Consumed AssuredPersistentMessages ConsumedCount All All Low
Report Enabled Messages Expired ReportEnabledMessages ExpiredCount All All Low
Aggregate Message Wait Time AggregateMessageWaitTime All All Low
Local Message Wait Time LocalMessageWaitTime All All Low
Local Oldest Message Age LocalOldestMessageAge All All Low

Topic Spaces ITM Table Name: KYNTOPICSP
WebSphere PMI Level
TEP Console Column Name WebSphere PMI Attribute WAS 6.0 WAS 6.1/7.0 Overhead
Category: SIB Service > SIB Messaging Engines > Destinations > Topicspaces
Incomplete Publication IncompletePublicationCount All All Low
Local Publisher Attaches LocalPublisherAttachesCount All All Low
Local Publisher LocalPublisherCount All All Low
Total Local Subscription TotalLocalSubscriptionCount All All Low
Non-durable Local Subscription NonDurableLocalSubscription Count All All Low
Durable Local Subscription DurableLocalSubscriptionCount All All Low
Total Messages Published TotalMessagesPublishedCount All All Low
Best Effort Non-persistent Messages Published BestEffortNonPersistentMessages PublishedCount All All Low
Express Non-persistent Messages Published ExpressNonPersistentMessages PublishedCount All All Low
Reliable Non-persistent Messages Published ReliableNonPersistentMessages PublishedCount All All Low
Reliable Persistent Messages Published ReliablePersistentMessages PublishedCount All All Low
Assured Persistent Messages Published AssuredPersistentMessages PublishedCount All All Low
Total Local Subscription Hits TotalLocalSubscriptionHitCount All All Low
Best Effort Non-persistent Local Subscription Hits BestEffortNonPersistentLocal SubscriptionHitCount All All Low
Express Non-persistent Local Subscription Hits ExpressNonPersistentLocal SubscriptionHitCount All All Low
Reliable Non-persistent Local Subscription Hits ReliableNonPersistentLocal SubscriptionHitCount All All Low
Reliable Persistent Local Subscription Hits ReliablePersistentLocal SubscriptionHitCount All All Low
Assured Persistent Local Subscription Hits AssuredPersistentLocal SubscriptionHitCount All All Low
Report Enabled Publication Expired ReportEnabledPublications ExpiredCount All All Low
Local Oldest Publication Age LocalOldestPublicationAge All All Max

Monitoring agent for WebSphere applications

Contents

Monitoring agent for WebSphere applications

The monitoring agent for WebSphere applications provides a systems-management solution for the WebSphere Application Server Versions 6, and 7 . Using the WebSphere agent, you can monitor multiple WebSphere application servers running on the same physical node. Each application server must have been configured with its own monitoring agent for WebSphere applications Data Collector.
IBM Tivoli Composite Application Manager Agent for WebSphere is a component of ITCAM for Application Diagnostics, Version 7.1. It is also a component of monitoring agent for WebSphere applications Version 6.2.3. If you are using monitoring agent for WebSphere applicationss the Managing Server (deep dive) functionality is not available; please ignore all references to this functionality in this document.
The monitoring agent collects four types of data through the data collector embedded in the WebSphere Application server process:

Data for application server requests from the monitoring agent for WebSphere applications Data Collector
Resource data from WebSphere Performance Monitoring Infrastructure (PMI)
Data from WebSphere log files
Process data from the operating system

Initiating data collection and reporting of data

Because of high overhead, some data items are not automatically collected and reported. The collection of some data and statistics depends upon the setting of instrumentation levels for certain attributes. If the instrumentation levels are not set appropriately, certain information will not be collected and displayed in the workspaces. Similarly, those attributes that collect request and application trace data require you to complete several configuration steps.

Automatic baselining

To display application health status, ITCAM monitors request response times (averaged over a sampling interval, by default 60 seconds) for every application. Every top level request available in an application is monitored separately.
For every request, two thresholds are set, known as fair and bad. When at least one average request response time for an application rises over the fair threshold, a health warning (yellow) for this application is reported. In the same way, when at least one average request response time rises over the bad threshold, an application health alarm (red) is reported.
ITCAM also monitors the "nested" requests (for example, database calls) within every top level request. In the event of a warning or alarm, it checks which of the nested requests is taking more than its usual share of time. Depending on the type of such nested requests, ITCAM shows whether the client, application, or backend tier is the likely cause of the warning/alarm. Servlet and Portal request types are assigned to the client tier; EJB and User (Custom) request types, to the application tier; all other request types (JNDI, JDBC, JCA, JMS) to the backend tier.
When ITCAM starts to monitor a new application, it automatically starts a baselining process. In this process, which normally runs for 7 days but provides updated information every hour from the beginning, ITCAM collects statistical data for all requests in this application. Once the data is collected, ITCAM sets the thresholds automatically; it also records the typical share of response time for each nested request type.
In most cases, this automatic setting is adequate. When the 7 days are past, the alarms/warnings will correspond to real problems. There is no need to adjust baselining settings when things are working normally. (The automatic thresholds usually become usable earlier, after the application has been observed through its typical load patterns). To acquire thresholds, based on whatever data is available, before the hourly automatic update, you can manually update baselining.
However, in some situations the threshold levels can become inadequate. This results in either too many false alarms/warnings, or in real problems going undetected. Such situations can be broadly split into two categories:

If some time has passed since the baselining process for an application, its response times might have changed because of configuration alteration, database growth, changing load patterns, and so on. In this case, you may need to run the baselining process again. It is good practice to do it after any configuration or infrastructure change.
If the thresholds are incorrect immediately after the baselining process has been completed, you may need to adjust the auto threshold settings.

As a last resort, you can also override the thresholds with fixed values. However, do not do this unless you know a lot about the monitored application, or unless instructed by IBM Level 3 Support.
To have the thresholds set before they are updated automatically for the first time, you can trigger a baseline update. This will immediately set the thresholds based on the request data collected so far.

Monitoring agent for WebSphere applications - workspaces

Monitoring agent for WebSphere applications - workspaces

As part of the monitoring agent for WebSphere applications product's integration with the monitoring portal, workspaces offer views of monitoring data that provide detailed current data about the Version 6 and 7 WebSphere application servers running on your site's Linux, UNIX, and Windows and z/OS platforms. In addition to reports and graphs, a workspace can contain other views (that is, windows), such as a Notepad editor session, a browser session, a telnet session, an event console, or a Take Action view from which you can issue commands.

Several views of high-level information

Several workspaces provide high-level information to help you meet your site's monitoring and administrative needs. These workspaces report current status and availability for both the WebSphere administrative server and its application server instances. They let you easily monitor the availability of your enterprise, the WebSphere Application Server, and application server instances.

Primary and secondary workspaces

The workspaces listed in the Navigator are directly accessible and are thus termed primary workspaces. Some of these also contain secondary workspaces, which are not accessible directly from the Navigator. Instead you must select and display the primary workspace, then use either a menu option or a special link icon in the primary workspace's views to reach the secondary workspaces (sometimes called subsidiary workspaces).

Workspaces with historical data links

Several workspaces provide secondary workspaces that display historical data. You can specify a time span over which to collect historical data, which accumulates and summarizes the data in the primary workspaces that generate them. (The default setting is 15 minutes; you can modify this setting to suit your needs.) The descriptions of the historical workspaces follow the descriptions of the primary workspaces that generate them in the workspace helps.

Workspace Name	Level in TEP	Views Available
WebSphere Agent Summary	Agent level	Application Servers Status Table Application Servers Summary
WebSphere Agent Summary Status	Agent level	Application Servers Status Application Servers Summary
application server Summary	application server Level	application server - Resources application server - Applications
Resources	application server Level	application server - Resources Situation Event Console
Applications	application server Level	application server - Applications Situation Event Console

Tivoli Enterprise Monitoring Agent Attribute Group Name	Icons	Predefined Situations
Applications Monitoring Configuration	N/A	WASAppDiscovered
Requests Monitoring Configuration	N/A
Baseline	N/A
Applications Health Status	Applications	WASApplicationBad, WASApplicationFair, WASApplicationGood
Applications Server Status	JVM
Log Analysis	JVM	WASError
KYN Command	N/A
WebSphere Agent Events	N/A
DC Messages WebSphere	JVM
Dynamic Cache	Services
Dynamic Cache Templates	Services
Workload Management Client	Services
Workload Management Server	Services
DB Connection Pools	Datasources	WASDBConnectionPoolThrdTimeout WASDBConnectionPoolUsageMaxed WASDBConPAverageUsageTimeHigh WASDBConPAvgWaitTimeHigh
Container Object Pools	Threadpools
Enterprise Java. beans	Applications	WASEJBCreateTimeHigh WASEJBMethodResponseTimeHigh WASEJBRemoveTimeHigh
Web Applications	Applications	WASWebApplicationError
Web Applications - Sessions	Applications	WASSrvlSessAvgActiveSessionHigh WASSrvlSessExtReadTimeHigh WASSrvlSessExtWriteTimeHigh
Applications Server	JVM, OS	WASHighCPUPercentUsed
EJB Containers	Applications
Servlets JSPs	Applications	WASServletsJSPError
Servlet Sessions	Applications
Thread Pools	Threadpools	WASThreadPoolPercentMaxed WASThreadFreeLow
Container Transactions	Datasources	WASContainerTransactionRollback WASCTGlbTransDurationHigh WASCTLclTransDurationHigh
J2C Connection Pools	Datasources	WASJ2CConnectionPoolUsageMaxed WASJ2CCPAverageUsageTimeHigh WASJ2CCPAvgWaitTimeHigh
DCS Stack
High Availability Manager
Web Services Gateway
Web Services
Alarm Manager
Scheduler	Services
Client Communications	Services
Durable Subscriptions	Services
Messaging Engine Communications	Services
Messaging Engines	Services
Queue	Services
Service Component Elements	Services
Service Components	Services
Topic Spaces	Services
WMQ Client Link Communications	Services
WMQ Link Communications	Services
Workplace Mail Service	Datasources
Workplace Mail Queues	Datasources
Workplace Mail IMAP/POP	Services
Portal Summary	Services
Portal Page Summary	Services	WASPortalPageResponseTime
Portlet Summary	Services	WASPortletResponseTime
Datasources	Services	WASDataSrcConWaitTimeHigh
Request Times and Rates	Applications	WASHighResponseTime
Request Analysis	Applications	WASReqSQLExecuteTimePercentHigh WASReqSQLQueryTimePercentHigh WASReqSQLUpdateTimePercentHigh
JMS Summary	Datasources
Selected Request	Applications
Garbage Collection Analysis	JVM	WASHighGCTimePercent WASAvgHeapSizeAfterGCHigh
Allocation Failure	JVM	WASOutofHeapSpace
Garbage Collection Cycle	JVM
WebSphere Agent		WASNotConnected
WebSphere App Server		WASHighCPUPercentUsed WASHighResponseTime

Error Message	Explanation
Internal Communication Error	This message indicates a communication problem between the summary workspaces front end and the summary workspaces back-end code (called evaluator) running inside the embedded WebSphere server on the monitoring portal server. This error displays for two reasons: If this error message is displayed for only some of the summary workspaces, turn up tracing and send to IBM support for review.
Invalid Data	This message indicates that data being sent from the summary workspaces back-end code (called evaluator) running inside the embedded WebSphere server on the monitoring portal server is malformed. Turn on the tracing, collect the logs, and send to IBM support for further analysis.
No Applications Configured	This message indicates that no applications are configured on the WebSphere server. This message also displays if the WebSphere server is not connected to the monitoring agent. The message no longer displays when the WebSphere server is back online. No user action is needed.
No Applications Servers Connected	This message indicates that no WebSphere servers are connected to the monitoring agent. The message is no longer displayed when the WebSphere server is back online. No user action is needed.

Workspace	Configuration file
WebSphere Agent Configuration workspace in windows:	CANDLE_HOME\TMAITM6\hostname_productcode.xml
application server Configuration workspace in windows:	CANDLE_HOME\TMAITM6\hostname_productcode_servervendor.servernode.server name.xml
WebSphere Agent Configuration workspace in other platforms:	CANDLE_HOME/config/hostname_productcode.xml
application server Configuration workspace in other platforms:	CANDLE_HOME/config/hostname_productcode_servervendor.servernode.server name.xml

Workspace: Table View Name	Number of links to managing server visualization agent	Link Name	Link Target Pages managing server visualization agent	Pre-populated information in the link page to managing server visualization engine
WebSphere Agent Summary Status > Application Servers WebSphere Agent Summary Status > Application Servers WebSphere Agent Configuration > Application Servers	2	Diagnostic Server Activity Display Diagnostic In-Flight Request Search	Server Activity Display . Active Requests In-Flight Request Search	The Group Server drop-down menu is pre-populated based on data collector information from monitoring portal workspace.
OS Stack >Current OS Stack Summary	3	Diagnostic Server Activity Display Diagnostic In-Flight Request Search <platform OS> <platform> is one of the following operating systems: Linux, UNIX, Windows or z/OS	Server Activity Display . Active Requests In-Flight Request Search Use the dynamic workspace link to the corresponding OS agent workspace. For z/OS, the link is to OMEGAMON XE for z/OS.	The Group Server drop-down menu is pre-populated based on data collector information from Tivoli Enterprise workspace.
JVM Stack Trend >JVM Stack Trend	1	Diagnostic Memory Leak	Memory Leak Analysis	The Group Server drop-down menu is pre-populated based on data collector information from Tivoli Enterprise workspace.
Request Analysis > Requests . Current Interval	3	Diagnostic Recent Completed Requests Diagnostic In-Flight Request Search Diagnostic SMF Data (z/OS only)	Server Activity Display . Recent Requests In-Flight Requests SMF Data (for z/OS data collectors only)	The Group Server drop-down menu is pre-populated based on data collector information from Tivoli Enterprise workspace. Content in Request Detail column of Requests table view in monitoring portal is pre-populated in the following fields: Recent Requests: Client Request In-Flight Request Search: Search Request/Transaction field
Garbage Collection Analysis >Garbage Collection Analysis	1	Diagnostic Memory Leak	Memory Leak Analysis	The Group Server drop-down menu is pre-populated based on data collector information from monitoring portal workspace.
Thread Pools >Thread Pools	1	Diagnostic JVM Thread Display	JVM Thread Display	The Group Server drop-down menu is pre-populated based on data collector information from monitoring portal workspace.
Datasources > Datasources . Current Interval Web Applications >Web Applications EJB Containers >EJB Containers JMS Summary >JMS Summary . Current Interval DB Connection Pools > DB Connection Pools J2C Connection Pools > J2C Connection Pools	1	Diagnostic Server Activity Display	Server Activity Display . Active Requests	The Group Server drop-down menu is pre-populated based on data collector information from monitoring portal workspace.

Workspace Table Name	Link Name	Description
WebSphere App Server - application server Summary	WebSphere App Server - application server Summary - Selected Region - application server Summary Selected Region - Application Health Status Selected Region - Request Analysis Selected Region - Log Analysis Selected Region - Data Sources Selected Region - JMS - Summary	This workspace displays data at regional level. Click the Selected Region links to access region-specific links to other top-level workspaces. When a workspace is linked from the application server summary you can view specific drill-down metrics. To view a report for an individual region, see ..."> Access a Region workspace
Application Health - Application Health Summary	Selected Application - Servant regions Selected Application - Health History Selected Application- Web Tier Analysis Selected Application - EJB Tier Analysis Selected Application - Backend Tier Analysis Selected Application - Request Analysis Selected Application - Configuration	In an z/OS environment, the Application Health Summary report displays the total results for the server instances. To view report results by region, click the WebSphere App Server - application server Summary table and right-click a link icon in the table to view the available options.
Request Analysis - Requests Current Interval	Selected Request - Datasource Selected Request - JMS Queues Selected Request - Resource Adaptors Selected Request - History Selected Request - Servant Regions	In an z/OS environment, when you select Request Analysis - Requests Current Interval, this report displays the total results for the server instances. To view a report for an individual Request Analysis region, see ..."> Access a Region workspace.
Garbage Collection Analysis - Garbage Collection Analysis	Selected Region - History Garbage Collection Analysis - Servant Region (only available when you click a [Summary] row)	For Garbage Collection Analysis, there is a summary report of all regions and there are also reports by individual region.
Log Analysis - Log Analysis	Selected Region - Log Analysis	Log Analysis workspace. In a z/OS environment, the log analysis workspace reports data in two ways. When you select the Log analysis workspace the report displays JVM Log Analysis and DC message events from all regions. To view a report for an individual log analysis region, see ..."> Access a Region workspace.
Data sources - Data sources - Current Interval	Selected Datasource Selected Datasource - History	In an z/OS environment, this report displays the total results for the server instances. To view a report for an individual Data source region, see ..."> Access a Region workspace.
JMS Summary - JMS Summary - Current Interval JMS	Selected JMS - Servant Regions	In an z/OS environment, this report displays the total results for the server instances. To view a report for an individual JMS Summary region, see..."> Access a Region workspace.
WebSphere Portal Server	Selected Region - Portal Server Summary	In an z/OS environment, this report displays the total results for the server instances. To view a report for an individual Portal Server summary, see ..."> Access a Region workspace
Portal Summary	Selected Region - Portal Summary Selected Region - Portlet Summary Selected Portal Page - History Selected Portlet - History Selected Region - Portal Page Summary	In an z/OS environment report displays the total results for the server instances. To view a report for an individual region see ..."> Access a Region workspace

Workspace	Related Attribute Groups
Application Health Summary	Application Health Status
Application Registry	Application Monitoring Configuration
Allocation Failures	Allocation Failure
Cache Analysis	Dynamic Cache Dynamic Cache Templates
Client Communications	Client Communications
Container Object Pools	Container Object Pools
Container Transactions	Container Transactions
Datasources Selected Datasource - History	Datasources
DB Connection Pools Selected DB Connection Pool - History	DB Connection Pools
DCS Stacks	DCS Stack Counter
Destinations	Topic Spaces Queue
Durable Subscriptions	Durable Subscriptions
EJB Containers	EJB Containers
Enterprise Java Beans	Enterprise Java Beans
Garbage Collections - Selected Allocation Failure	Garbage Collection Cycle
Garbage Collector Analysis	Garbage Collection Analysis
High Availability Manager	High Availability Manager
IMAP/POP	Workplace Mail IMAP/POP
J2C Connection Pools	J2C Connection Pools
JMS Summary	JMS Summary
Log Analysis	Log Analysis
Lotus	application server Request Times and Rates Garbage Collection Analysis
Messages Queues	Workplace Mail Queues
Messaging Engine Communications	Messaging Engine Communications
Platform Messaging	Messaging Engines
Pool Analysis	Thread Pools DB Connection Pools J2C Connection Pools application server
Portal Pages Summary Selected Portal Page - History	Portal Page Summary
Portal Summary	Portal Summary
Portlet Summary Selected Portlet - History	Portlet Summary
Request Analysis Selected Request - History	Request Analysis
Selected Request - Baseline	Baseline
Selected Request - Service Components workspace	Selected Request
Scheduler	Scheduler
Selected Application - Application Tier Analysis Selected Application - Backend Tier Analysis Selected Application - Health History Selected Application - Client Tier Analysis	Application Health Status
Selected Application - Configuration	Application Monitoring Configuration
Selected Request - Datasources	Selected Request
Selected Request - JMS Queues	Selected Request
Selected Request - Resource Adapters	Selected Request
Servlets/JSPs - Selected Web Application	Servlets JSPs
Sessions	Servlet Sessions
Thread Pools	Thread Pools
Web Applications	Web Applications
Web Services Selected Web Services - History	Web Services Counters Web Services Gateway Counters
WebSphere Agent	WebSphere Agent Events application server Status Remote Configuration Requests attributes
WebSphere App Server	application server Request Times and Rates Garbage Collection Analysis
WebSphere ESB Server	application server Request Times and Rates Garbage Collection Analysis
WebSphere Portal Server	application server Request Times and Rates Garbage Collection Analysis
WebSphere Process Server	application server Request Times and Rates Garbage Collection Analysis
WMQ Client Link Communications	WMQ Client Link Communications
WMQ Link Communications	WMQ Link Communications
Workload Management	Workload Management Client Workload Management Server
Workplace Mail	Workplace Mail Service

Server Type	Definition
Unknown	The server type cannot be determined
AppServer	A process that executes applications
AdminServer	The administrative server you use when configuring WebSphere Application Server environments
NodeAgent	The WebSphere Application Server node agent
JMSServer	The WebSphere Application Server JMS server
DeploymentMgr	The WebSphere Application Server deployment (cell) manager
ManagedProcess	A stand-alone WebSphere Application Server process
UnManagedProcess	A WebSphere Application Server process that is managed by a WebSphere Application Server deployment manager through a node agent

Compaction Code	Definition
1	Insufficient free space for the allocation request following the mark and sweep phases.
2	The heap is fragmented and benefits from a compaction.
3	Less than 15% free space available.
4	A call to System.gc requested garbage collection.
5	Less than 5% free space available.
6	Less than 128 K free space available.
7	Parameter Xcompactgc specified.
8	The transient heap has less than 5% free space available.
9	The heap is fragmented (this code marks additional reasons for compaction apart from compaction code 2).

Severity	Definition
Informational	A message intended to convey only user information
Unconditional	A message of type Unconditional
Dump	A message of type Dump
SystemOut	A message written directly to System.out by the user application or internal components
SystemError	A message written directly to System.err by the user application or internal components
User	A message of type User
EntryMethod	A message written upon entry to a method
ExitMethod	A message written upon exit from a method
Event	A message of type Event
Debug	A message of type Debug
Audit	An audit message
Warning	A warning message
Error	An error message
Terminate	A message of type Terminate (exit process)
Fatal	A fatal message
Unknown	A placeholder that indicates the message type was not recognized

Type	Definition
n/a	not applicable
Servlet	A call to a doGet or doPost methods of a servlet
EJB_Method_Call	A call to a business method for an EJB class
Obtain_SQL_Connection_from_Datasource	A call to obtain a connection from a JDBC data source
SQL_Query	A Query request to a JDBC data source
SQL_Update	An Update request to a JDBC data source
SQL_Other	Any other request to a JDBC data source
JMS_Message_Browse	A call to browse a message from a JMS queue
JMS_Message_Get	A call to receive a message from a JMS queue (that is, a destructive get)
JMS_Message_Put	A call to put a message from a JMS queue
JMS_Publish_Message	A call to publish a publication to a JMS queue
JCA_CCI_Execute_interaction	A request by a J2EE application to execute a JCA interaction (a JDBC, JMS, or other JCA-supported operation) against a backend system
JNDI_Lookup	A call to JNDI to build an InitialContext or to perform a lookup
Unknown	The activity type cannot be determined
Portlet_Processing	A call for portlet processing request
Portlet_Authorization	A call for portlet authorization request
Portal_Authentication	A call for portal authentication request
Portal_Model_Building	A call for portal page model building request
Portal_Page_Loading	A call for portal page loading request
Portal_Page_Rendering	A call for portal page rendering request
Portal_Legacy_Action	A call for portal legacy action request
Portal_Standard_Action	A call for portal standard action (JSR-88) request
SCA	A call for Service Component Architecture (SCA) request
Web Service Provider	A call to a web service provide
Web Service Client	A call to a web service client

Workspace	Description
Web Applications workspace	Displays performance data for each web application (.war). This data includes number of requests, average response time, and number of errors. Note that one Web application may have multiple URLs for user requests and the response times for all the requests are aggregated in this window.
Servlets/JSPs - Selected Web Application workspace	Breaks down the performance data for a particular Web application into the servlets or JavaServer pages (JSPs) that it contains. Again, each servlet/JSP can contain or be mapped to multiple URLs and all user requests are combined.
Sessions workspace	Provides information regarding HTTP sessions created by each Web application. HTTP sessions are used to maintain a user session between multiple invocations and stores user specific data. This workspace also displays the total, average, maximum, and minimum sizes of the user data stored for each Web application.
EJB Containers workspace	Provides an overview of the performance of different types of Enterprise JavaBeans (EJBs) deployed in the application server.
Enterprise Java Beans workspace	Displays the performance data for each EJB deployed in the application. Based on the Bean type, data is available in the appropriate columns.
Container Transactions workspace	Provides performance data regarding Java Transaction API (JTA) transactions the EJBs are involved in.
Container Object Pools workspace	Provides information about the behavior of stateless and entity bean pools.
DB Connection Pools workspace	Displays the usage data regarding Database connection pools such as the number of connections available, checked out, threads waiting for a connection, and so on. This workspace is useful in understanding the pool usage and identifying potential bottlenecks in application performance when a thread is waiting or getting timed out for a connection from the pool.
J2C Connection Pools workspace	Displays the usage data for connection pools set up for Java Connector Architecture (JCA) based resource adapters. The WebSphere Application Server creates connection pools for the resource adapters deployed (some of the adapters are provided by application server installation itself) and this workspace is useful in monitoring performance bottlenecks in terms of wait times to obtain a connection.
Pool Analysis workspace	Provides information about the usage of several types of pools associated with each application server, including Web container pools, ORB pools, J2C connection pools, and database connection pools. This workspace helps you detect resource constraints and potential performance congestion.
Thread Pools workspace	Displays the usage data for thread pools. The data can be used to determine whether the pool is configured correctly to service user requests. For example, the Web Container thread pool is used to execute servlet requests from the users and if the number of threads in the pool is small compared to the number of incoming requests, there will be a delay in servicing them leading to slower response times.
Thread Pool Trend workspace	Displays trend information about thread pool size and usage.
Cache Analysis: Dynamic CacheCache Analysis workspace	Provides the usage data of the various dynamic caches that have been configured in the system. In WebSphere Application Server 6.x and later, multiple caches can be configured. Also provides the usage data for each dynamic cache template. The templates are unique IDs that are specified in the cachespec.xml files to identify different URLs that must be cached.
Workload Management workspace	Workload management distributes the user requests made through the Object Request Broker (ORB) to different servers in a cluster. This usually means that this feature will come into play only when remote EJB calls are made over the ORB. This feature is applicable only in the ND (Network Deployment) environment when clusters are set up, so that the workload can be distributed when remote EJB calls are invoked over the ORB. If the ORB is not used, this feature is not exercised and there will be no data in this workspace. If a server has both Servlets and EJBs on the same server instance, the calls are usually configured to be local calls instead of remote calls for better performance, and hence the ORB will not come into play. The server side data provides information about the number of requests received on the server side (for example, the EJB container receiving the user requests).
Scheduler workspace	Scheduler service runs periodic tasks. Schedulers are persistent transactional timer services that run Enterprise JavaBean methods or send Java Message Service messages using any J2EE server application.
Web Services workspace	Provides performance data on the Web Services hosted by the application server instance. Web Services provides data regarding number of Web services loaded, number of requests delivered, size of the requests, and so on. Also includes information on the Web services gateway, which is used to map an existing service - either an inbound or an outbound service - to a new Web service that appears to be provided by the gateway. The gateway acts as a proxy: your gateway service users need not know whether the underlying service is being provided internally or externally. The gateway provides you with a single point of control, access and validation of Web service requests, and allows you to control which Web services are available to different groups of Web service users.
Workplace Mail workspace	Provides aggregated statistics of the usage information about the incoming message traffic.
Messages Queues workspace	Provides information about message delivery state, including ready retry, unprocessed, and dead.
Messaging workspace	The messaging engines defined in various Service Integration Buses in this application server. Provides performance numbers on each messaging engine such as number of messages published. This workspace displays data only when a Service Integration Bus (SIB) is available in the system.
Client Communications workspace	Provides communication details with distinct client processes that are currently network-connected to the Service Integration Buses of this application server. The data deals with messages sent and received from and to the various client processes.
Messaging Engine Communications workspace	Provides information about other application servers that are hosting messaging engines and are network-connected to this application server. The Service Integration Bus is used to send and receive messages from these messaging engines.
Destinations workspace	Provides performance data and counters for the destinations of a selected messaging engine. This includes the numbers of available and unavailable messages, numbers of messages produced and consumed, aggregated wait times and so on.
WMQ Client Link Communications workspace	Provides information regarding communication to WebSphere MQ JMS clients that are connected to this application server.
WMQ Link Communications workspace	Provides information regarding communication to WebSphere MQ JMS queue managers that are connected to this application server.
Alarm Manager workspace	Provides aggregated information about the alarms for each work manager. This includes the number of alarms created, fired, canceled and so on.
DCS Stacks workspace	Provides aggregated information about each DCS stack within the entire WebSphere Application Server domain, including multiple nodes and servers. This includes the incoming and outgoing message size, the number of incoming and outgoing messages, congestion events, and message buffer re-allocations.
Durable Subscriptions workspace	Provides statistic counters for the durable subscriptions of a selected topic.
High Availability Manager workspace	Provides aggregated information about high availability managers.
IMAP/POP workspace	Provides aggregated statistics of the usage information about the IMAP service and the POP3 service connectivity, especially for the performance-related connectivity.
Service Components workspace	Provides overview performance of the key service components. WebSphere servers feature their own service components, and each of these components has its own set of event points that can be monitored.
Service Component Elements workspace	Lists performance metrics for all the service components and their elements. Service components contain one or more elements, which are sets of different steps processed in each service component. In turn, each element has its own set of event natures, which are key points that are reached when processing a service component element.

Workspace	Monitor level	Description
Request Analysis workspace	Level 1	This workspace displays the number of user requests that were tracked during the sampling interval and their average response times. The requests are grouped by URLs for servlet calls and EJB names for direct EJB calls.
Request Baseline workspace	Level 1	This workspace displays aggregated information about the request baseline. In the baselining process, the agent collects statistical information about a request completion times and uses this information to assign "fair" and "bad" thresholds for requests.
Request Analysis workspace	Level 2	In addition to Level 1 data, the workspace also shows the breakdown of the response times into application, SQL Query, SQL Update, JCA, JMS, JNDI, SCA, web services processing times. This breakdown can be displayed in milliseconds and as a percentage of average response time.
Selected Request - Datasources workspace	Level 2	To access this workspace, clicking the link icon on the row header of each row in the Request Analysis workspace. This workspace provides more details on the resources accessed by the selected user transaction - including the resource names, the average response time, and the longest response time during the sampling interval.
Data sources workspace	Level 2	This workspace displays the time spent on various Data source operations. The operations include obtaining a connection, and executing a query or update. The workspace also shows the number of connections used during the sampling interval. The data in this workspace supplements the DB Connection Pools workspace by identifying the reason for long connection checkout times.
JMS Summary workspace	Level 2	This workspace provides count and time measurements for JMS operations: send, receive, browse, and publish. It displays data on a queue and topic basis. The data provides a breakdown of the JMS delay shown in the Request Analysis workspace.

Workspace	Log file	Description
Garbage Collection Analysis workspace	Native error file specified in application server configuration. The file name is set when configuring the Data Collector (the default is gc.log).	ITCAM Agent for WebSphere Applications scans the verbose garbage collection (GC) log to provide information about how the GC is performing. This workspace can identify application performance issues when the GC consumes a lot of time. Such issues usually happen when the heap size parameters in the JVM are not set correctly. You can stop and start the collection of GC data using the Start_GC_Monitoring and Stop_GC_Monitoring Take Action commands. the Take Action command does not turn on and off the verbose GC flag in WebSphere JVM. This flag is required for collection of GC data. You might need to enable or disable it using the application server admin console.
Allocation Failures workspace	Same as Garbage Collection Analysis	Provides information about heap allocation failures that cause the JVM to invoke garbage collection.
JVM Stack Trend workspace	Same as Garbage Collection Analysis	Provides trend data regarding JVM CPU usage, JVM garbage collection, and JVM heap usage. Displays Operating System data for CPU usage.
Log Analysis workspace	SystemOut.log	The Agent scans the application server SystemOut.log file and retrieves the messages for display in this workspace. Use the workspace to be informed about the health of the application server and also to create situations when certain message IDs are encountered.
Log Analysis workspace	Data Collector message events	Displays the Data Collector diagnostic messages, informing whether the Data Collector has initialized and is working correctly.

Workspace	Description
Application Server Summary and Business Process Manager Summary workspaces	This workspace displays overall statistic information for each application server that is monitored by the agent. The information includes history of heap usage, response times, request rates, and % CPU used.
WebSphere Agent workspace	This workspace displays events occurring within the agent and all the application servers on the host. It also displays status information about the agent and the online/offline status of the monitored servers.
EJB Tier Analysis workspace	The workspace displays information about the health of a WebSphere application based on response time and completion rates for EJB requests. It also displays ORB thread pool information and PMI information related to EJB requests.
Backend Tier Analysis workspace	The workspace displays information about the health of a WebSphere application based on response time for Backend Tier requests. It also displays information about backend tier resources, including Data Sources, JMS resources, JDBC and JCA Pools, and JVM statistics.
Web Tier Analysis workspace	The workspace displays information about the health of a WebSphere application based on response time and completion rates for Web Tier requests. It also displays WebContainer thread pool information and PMI information related to HTTP sessions.

Workspace	Checkpoint	Comments
All Workspaces	The application server is running and the monitoring agent is connected to it	Check that the Status column in the Application Server Summary and Business Process Manager Summary workspaces shows Connected.
All Workspaces	There is user load applied on the application server	The Request data workspaces display data only when user load is applied. The Resource data workspaces still display data rows even if load is not applied, but the columns will either be empty or display zeros. The data rows in this case are created from the application server configuration information about the resource type.
Request Data Workspaces	Request Data collection is turned on	Verify by checking the Request Data Monitoring Level column in the Application Server Summary workspace is not Disabled. If it is Disabled, start the monitoring by using the Start_Request_Monitoring : Begin reporting request data Take Action command.
Request Data Workspaces	Sampling rate is high enough	The default sampling rate is 2%. If the load on the application server is low, the Agent might fail to track user transactions. Verify the sampling rate in the Request Data Sampling Rate(%) column in the Application Server Summary and Business Process Manager Summary workspaces. Set the rate higher by using the Set_Request_Sampling_Rate: Set the sampling rate for request data Take Action command.
Data sources workspace	Request Data Monitoring Level is set to Level 2	The Request Data Monitoring Level column in Application Server Summary and Business Process Manager Summary workspaces workspace displays the value. To change the monitoring level, use the Start_Request_Monitoring : Begin reporting request data Take Action command.
Data sources workspace	Data sources are configured in the application server; user requests are accessing these Data sources	To check the presence of Data sources, use the application server admin console. You need to know application logic to verify whether the user requests are accessing the Data sources. Check DB Connection Pools workspace for activity with the Data sources.
JMS Summary workspace	JMS resources (queues, topics) are configured and applications are accessing these resources	To check the existence of JMS resources, use the admin console. You need to know application logic to verify whether these resources are used.
Resource Data Workspaces	Feature is available	Verify the application server feature is being used. For example, Dynamic cache data will be available only when the cache feature has been set up. All "Platform Messaging" workspaces will be available only when the Service Integration Bus has been configured and used.
Resource Data Workspaces	PMI is enabled in the application server	Verify PMI is enabled through the administration console of WebSphere Application Server. Make sure PMI is enabled for the desired modules (for example, WebApplications, ServletSessions, EJBContainer, and so on). To do this, check the Runtime tab of the Performance Monitoring Infrastructure page in the application server admin console.
Resource Data Workspaces	Data not available in certain columns	Verify PMI level is high enough to capture data for these columns. Check the Instrumentation Level column in the workspace that you need to view. Change the PMI level through the application server admin console. The contextual help on the data columns in portal workspace specifies the PMI level at which data will be available.
Resource Data Workspaces	Resource Data Monitoring is turned on	The Resource Data Monitoring column in Application Server Summary and Business Process Manager Summary workspaces must say Enabled. If it is set to Disabled, turn it on using the Start_Resource_Monitoring: Begin reporting PMI data Take Action command.
Garbage Collection Analysis workspace	Verbose GC flag is turned on in WAS	Verify the Verbose GC box is checked in the Application Server->Process Definition->Java Virtual Machine page of the admin console.
Garbage Collection Analysis workspace	Garbage Collection Monitoring is enabled	The Garbage Collection Monitoring column in Application Server Summary and Business Process Manager Summary workspaces must be Enabled. If it set to Disabled, use the Start_GC_Monitoring: Begin reporting garbage-collection data Take Action command to start it. the Take Action command will not enable the verbose GC flag in the application server. You have to do it separately.