APM_9.5--APM for IBM WebSphere Application Server ZOS Guide

8/11/2019 APM_9.5--APM for IBM WebSphere Application Server ZOS Guide

1/30

for IBM WebSphere Application Server forz/OS Guide

Release 9.5

CA Application PerformanceManagement


2/30

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to

as the Documentation) is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, withoutthe prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed

by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing

your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and

CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may

print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your

employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced

copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable

license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to

certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY

KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE,

DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST

INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE

POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such

license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions

set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or

their successors.

Copyright 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong totheir respective companies.


3/30

CA Technologies Product References

This document references the following CA Technologies products and features:

CA Application Performance Management (CA APM)

CA Application Performance Management ChangeDetector (CA APM

ChangeDetector)

CA Application Performance Management ErrorDetector (CA APM ErrorDetector)

CA Application Performance Management for CA Database Performance (CA APM

for CA Database Performance)

CA Application Performance Management for CA SiteMinder (CA APM for CA

SiteMinder)

CA Application Performance Management for CA SiteMinder Application ServerAgents (CA APM for CA SiteMinder ASA)

CA Application Performance Management for IBM CICS Transaction Gateway (CA

APM for IBM CICS Transaction Gateway)

CA Application Performance Management for IBM WebSphere Application Server

(CA APM for IBM WebSphere Application Server)

CA Application Performance Management for IBM WebSphere Distributed

Environments (CA APM for IBM WebSphere Distributed Environments)

CA Application Performance Management for IBM WebSphere MQ (CA APM for

IBM WebSphere MQ)

CA Application Performance Management for IBM WebSphere Portal (CA APM forIBM WebSphere Portal)

CA Application Performance Management for IBM WebSphere Process Server (CA

APM for IBM WebSphere Process Server)

CA Application Performance Management for IBM z/OS (CA APM for IBM z/OS)

CA Application Performance Management for Microsoft SharePoint (CA APM for

Microsoft SharePoint)

CA Application Performance Management for Oracle Databases (CA APM for Oracle

Databases)

CA Application Performance Management for Oracle Service Bus (CA APM for

Oracle Service Bus) CA Application Performance Management for Oracle WebLogic Portal (CA APM for

Oracle WebLogic Portal)

CA Application Performance Management for Oracle WebLogic Server (CA APM for

Oracle WebLogic Server)

CA Application Performance Management for SOA (CA APM for SOA)


4/30

CA Application Performance Management for TIBCO BusinessWorks (CA APM for

TIBCO BusinessWorks)

CA Application Performance Management for TIBCO Enterprise Message Service

(CA APM for TIBCO Enterprise Message Service)

CA Application Performance Management for Web Servers (CA APM for Web

Servers)

CA Application Performance Management for webMethods Broker (CA APM for

webMethods Broker)

CA Application Performance Management for webMethods Integration Server (CA

APM for webMethods Integration Server)

CA Application Performance Management Integration for CA CMDB (CA APM

Integration for CA CMDB)

CA Application Performance Management Integration for CA NSM (CA APM

Integration for CA NSM)

CA Application Performance Management LeakHunter (CA APM LeakHunter)

CA Application Performance Management Transaction Generator (CA APM TG)

CA Cross-Enterprise Application Performance Management

CA Customer Experience Manager (CA CEM)

CA Embedded Entitlements Manager (CA EEM)

CA eHealth Performance Manager (CA eHealth)

CA Insight Database Performance Monitor for DB2 for z/OS

CA Introscope

CA SiteMinder

CA Spectrum Infrastructure Manager (CA Spectrum)

CA SYSVIEW Performance Management (CA SYSVIEW)


5/30

Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the

information that you need for your Home Office, Small Business, and Enterprise CA

Technologies products. Athttp://ca.com/support,you can access the following

resources:

Online and telephone contact information for technical assistance and customer

services

Information about user communities and forums

Product and documentation downloads

CA Support policies and guidelines

Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you

can send a message [email protected].

To provide feedback about CA Technologies product documentation, complete our

short customer survey which is available on the CA Support website at

http://ca.com/docs.
http://www.ca.com/supporthttp://www.ca.com/supporthttp://www.ca.com/supportmailto:[email protected]:[email protected]:[email protected]://www.ca.com/docshttp://www.ca.com/docshttp://www.ca.com/docshttp://www.ca.com/docsmailto:[email protected]://www.ca.com/support


6/30


7/30

Contents 7

Contents

Chapter 1: Introduction 9

Introduction ................................................................................................................................................................. 9

System Requirements .................................................................................................................................................. 9

Chapter 2: Installing the Extension 11

How to Install the Extension ...................................................................................................................................... 11

Extract the Installation Files ................................................................................................................................ 11

Install the Management Module ........................................................................................................................ 12

Install the Tab Extensions.................................................................................................................................... 12

Configure the Agent Profile................................................................................................................................. 13

Chapter 3: Using the Extension 15

Start the Extension ..................................................................................................................................................... 15

Configuration Changes Reflected in Dashboards ................................................................................................ 15

Dashboards and the Investigator ............................................................................................................................... 16

Overview Dashboard ........................................................................................................................................... 17

HTTP Session Objects Dashboard ........................................................................................................................ 17

JDBC Connections and Web Container Dashboard ............................................................................................. 18

Thread Pools Dashboard ..................................................................................................................................... 19

View Summary Metrics .............................................................................................................................................. 20View the HTTP Session Objects ........................................................................................................................... 20

View the Web Container ..................................................................................................................................... 20

View Individual Requests .................................................................................................................................... 21

View Request Details .......................................................................................................................................... 21

Appendix A: Metrics 23

WebSphere for z/OS Metrics...................................................................................................................................... 23

WebSphere 7 Metrics ................................................................................................................................................. 26

Appendix B: Frequently Asked Questions 29

Why Do I Use the Extension to Monitor my WebSphere Application Server?........................................................... 29

Why Are There Empty Panels in the Dashboards? ..................................................................................................... 29

Why Are Not All the Metrics in the Documentation? ................................................................................................ 30


8/30


9/30

Chapter 1: Introduction 9

Chapter 1: Introduction

This section contains the following topics:

Introduction(see page 9)

System Requirements(see page 9)

Introduction

The extension lets CA Introscope administrators monitor the health and performance

of IBM WebSphere Application Server on z/OS.

The extension uses a .PBD file to add custom tracers to your WebSphere .JAR files.

Preconfigured dashboards and alerts let you monitor the following performance metricsin a WebSphere environment:

System health

HTTP session objects (WebSphere Application Server-specific)

JDBC connection pools (WebSphere Application Server-specific)

Web containers (WebSphere Application Server-specific)

System Requirements

For supported versions of the extension, see the APM Extensions section of the

Compatibility Guide.

Note: Valid for CA Introscope 9.0.5 --The Japanese version of the extension only

works with CA Introscope 9.0.5.


10/30


11/30


Chapter 2: Installing the Extension


How to Install the Extension(see page 11)

How to Install the Extension

Installing the extension involves the following steps:

1. Extract the installation files.(see page 11)

2. Install the Management Module(see page 12).

3. Install the tab extensions(see page 12).

4.

Configure the agent profile(see page 13).

Extract the Installation Files

The extension for IBM WebSphere for z/OS includes the following installation package

archives:

OS Filename

Windows ExtensionforWebsphere6.1and7zOSvwindows.zip

z/OS ExtensionforWebsphere6.1and7zOSvebcdic.tar

UNIX ExtensionforWebsphere6.1and7zOSvunix.tar

The in the filename is the version of the IBM WebSphere for z/OS extension.

Extract the extension for IBM WebSphere for z/OS archive appropriate to your system.

Important!If you use FTP ASCII mode to transfer the .TAR installer or its files to the z/OS

platform, the files are corrupted.


12/30


12 for IBM WebSphere Application Server for z/OS Guide

The following files are included in the archive:

File Description

APM_for IBM_Websphere_AppServer_zOS_EN.pdf This user guide

PPWebSphere6.1zOS.pbd

PPWebSphere7zOS.pbd

The ProbeBuilder Directive file defines

which metrics will be collected and CA

Introscope enables the application

PPWebSphere6.1and7zOS.typeviewers.xml The tab extensions installation archive file

PPWebSphere6.1zand7OS_ManagementModule.jar The Management Module files installation

archive file

Install the Management Module

To provide CA Introscope with the monitoring configuration information for the

extension, install the Management Module.

Follow these steps:

1.

Shut down the Enterprise Manager.

2. Copy the extracted installation archive file,

PPWebSphere6.1and7zOS_ManagementModule.jar, to the Enterprise Manager

Management Module directory as follows:

\config\modules

Install the Tab Extensions

To provide support for the various views, install the tab extensions.

Follow these steps:

1.

Verify that the xmltv directory exists. If the xmltv directory does not exist, create it.

2. Copy the extracted installation archive file,

PPWebSphere6.1and7zOS.typeviewers.xml, to the CA Introscope directory:

/ext/xmltv


13/30



Configure the Agent Profile

To collect data for the extension, configure the CA Introscope agent profile.

Follow these steps:

1. Stop the WebSphere server.

2.

Copy the .PBD file that corresponds to your version of WebSphere to the \wily

directory. For example, the PPWebSphere7zOS.pbd corresponds to WebSphere 7.0.

3. Add the respective .PBD file name to the Introscope.autoprobe.directives

parameter in the IntroscopeAgent.profile file.

Example:

Introscope.autoprobe.directives=websphere-typical.pbd, PPWebSphere7zOS.pbd

Important!If you are using WebSphere 6.1 or 7.0 with Introscope 8.0 through 9.5,

comment out the ws70x.pbd file entry in the websphere-full.pbl and

websphere-typical.pbl files. Otherwise, CA Introscope skips an important filenecessary for WebSphere and does not display the "WebSphere|Managed JDBC

Connections" metrics for WebSphere 6.1 or 7.0.

4. Restart the WebSphere server.


14/30


15/30


Chapter 3: Using the Extension

This chapter outlines how to use the extension for IBM WebSphere.


Start the Extension(see page 15)

Dashboards and the Investigator(see page 16)

View Summary Metrics(see page 20)

Start the Extension

You start the extension and use it to view metrics and dashboards.

Follow these steps:

1. Start WebSphere.

2.

Start the Enterprise Manager and Workstation.

3. Log in to the Workstation.

4. Navigate to the Investigator window.

WebSphere server-specific metrics appear under the WebSphere node. A number

of possible metrics that the extension collects appears. A subset of these metrics

appears in your own environment, depending on which WebSphere resources your

applications use.

5. Open the console.

The extension provides a number of preconfigured dashboards for displaying

WebSphere performance metrics. A subset of these metrics appears in your

environment, as the metrics you see depend on which WebSphere resources your

applications use.

Configuration Changes Reflected in Dashboards

The extension dashboards provide real-time feedback on the effects of configuration

changes. To map some of the metrics in the dashboards with the WebSphere

configuration parameters, use this section. WebSphere configuration parameters can bemodified using the WebSphere Admin Console.

Note: Use the information in this table as a general guideline for fine-tuning

WebSphere. Consult CA Technologies Professional Services on further fine-tuning your

WebSphere environment.


16/30

Dashboards and the Investigator


The following items are the dashboard graphs and the associated metrics.

JDBC Connection Pool Response Time

If this value increases significantly generating a warning or problem (red) zone,

consider changing the size of your HTTP server JDBC connection pool. To allow yourWebSphere Application Server to handle more simultaneous JDBC requests, use the

WebSphere Admin console.

Live HTTP Sessions

Gives insight into the number of active user sessions your application server is

servicing. To improve throughput, consider increasing memory or available CPU.

Aggregate HTTP Sessions Invalidated

As user sessions are invalidated (logged out) by the application server, growth in

this graph occurs.

Aggregate HTTP Sessions Timed Out

As the application server times out user sessions, growth in this graph occurs.

The extension for IBM WebSphere for z/OS comes with default caution/danger alert

thresholds for many of the performance metrics displayed in the dashboards. Consult

the CA APM Workstation User Guidefor instructions about customizing these alerts and

thresholds for your environment.


All the extension dashboards begin with WebSphere. This naming

distinguishes them from other Management Module dashboards already installed in CAIntroscope.

The dashboards in the extension contain visual elements (alerts, graphs, and so forth)

that display specific monitored WebSphere performance metrics.

Alerts visually indicate metrics that have exceeded predefined thresholds. Graphs

display metric values over time. Alerts occur when warning and danger threshold levels

have been triggered.


17/30



Overview Dashboard

The WebSphereX - Overview dashboard is the top-level dashboard and it displays

high-level status for the WebSphere platform. This dashboard groups WebSphere

resources in three major categories:

HTTP Session Object Count


Web Container Service Response Time

An Overview dashboard alert that turns red indicates you can drill down to the specific

metrics that triggered the alert. The list following the screen shot includes the

dashboard graph labels and their corresponding WebSphere performance metrics.

The following times are the dashboard graphs and the associated metrics.

HTTP Session Object CountWebSphere|HTTP Session Objects:Live HTTP Sessions Count


WebSphere|Managed JDBC Connections|Connection Request: Average Response

Time (ms)

Web Container Service Response Time

WebSphere|Web Container: Average Service Request Time (ms)

The Web Container Service Response Time and the Average Service Request Time

represent the same metric.

HTTP Session Objects Dashboard

The HTTP Session Objects dashboard presents a graphical representation of aggregate

and average metric data relating to HTTP session traffic and persistent sessions.

The following items are the dashboard graphs and their associated WebSphere

performance metrics.

Active HTTP Sessions

WebSphere|HTTP Sessions Objects:Live HTTP Sessions Count

Aggregate HTTP SessionsWebSphere|HTTP Sessions Objects:Aggregate Active HTTP Session Count

Aggregate HTTP Sessions Invalidated

WebSphere|HTTP Sessions Objects:Aggregate Invalidated HTTP Session Count


18/30



Aggregate HTTP Sessions TimedOut

WebSphere|HTTP Sessions Objects:Aggregate Timed Out HTTP Session Count

Average Get JDBC Connection Time

WebSphere|HTTP Sessions Objects|Get JDBC Connection:Average Response Time

(ms)

Average Persist Session Time

WebSphere|HTTP Session Objects|Get JDBC Connection and Persist

Session|Average Response Time (ms)

Average Read Session Time

WebSphere|HTTP Session Objects|Get JDBC Connection and Read

Sessions|Average Response Time (ms)

Read Cache Hit

WebSphere|Persistent HTTP Session Objects|Persistent Session ReadCache:Aggregate Count

JDBC Connections and Web Container Dashboard

The JDBC Connections & Web Container dashboard presents a graphical representation

of aggregate and average metric data relating to Managed JDBC connection resources

and web containers.



JDBC Connection Attempts Per Interval

WebSphere|Managed JDBC Connections|Connection Request:Responses Per

Interval

Aggregate JDBC Connections Used Count

WebSphere|Managed JDBC Connections:Aggregate Connections Opened/Closed

Count

Average Get Connection Time

WebSphere|Managed JDBC Connections|Connection Request:Average Response

Time (ms)

Average Close Connection Time

WebSphere|Managed JDBC Connections|Connection Close:Average Response Time

(ms)


19/30



Average Service Response Time

WebSphere|Web Container:Average Service Request Time (ms)

Note: Average Service Response Time and Average Service Request Time represent

the same metric.

Service Requests per Interval

WebSphere|Web Container:Service Requests Per Interval

Servlet Exception Count

WebSphere|Web Container:Servlet Exception Count

Thread Pools Dashboard

The Thread Pools dashboard shows the activity of the two primary WebSphere internal

pools.

The Threads Created metric tracks the total number of threads (z/OS Task Control

Blocks) that WebSphere has dynamically created during its processing.

The Threads Destroyed metric tracks the total number of threads (z/OS Task Control

Blocks) that WebSphere has dynamically destroyed/freed during its processing.

The Managed JDBC Connections Pool shows the number of JDBC Connection Requests

Per Interval and the total aggregate requests that WebSphere made to the database.

WebSphere uses internally managed JDBC sessions for processing HTTP Session objects

that are using a database to save shopping cartdata, and so forth. Internally managed

JDBC sessions are also used when WebSphere is processing (EJB) container-managed

activities that use a database as a backing store.



WebSphere Created Threads

WebSphere|Threads|ThreadPool:Thread Create

WebSphere Destroyed Threads

WebSphere|Threads|ThreadPool:Thread Destroy

Aggregate JDBC Sessions

WebSphere|Managed JDBC Connections:Aggregate Connections Opened/ClosedCount


20/30

View Summary Metrics



To view summary metrics, select these WebSphere nodes in the Investigator tree.

The extension displays an aggregate tab of summary metrics:

HTTP Session Objects

Web Containers

Servlets

View the HTTP Session Objects

To view the WebSphere HTTP session objects information, select the WebSphere HTTP

Session Objects node in the Investigator tree.

The Investigator displays the HTTP Session Objects tab view.

The HTTP Session tab view includes the Aggregate Active HTTP Sessions Count tab,

which presents a graphical representation of:

Aggregate Active HTTP Sessions Count

New HTTP Sessions Count Per Interval

Aggregate Invalidated HTTP Sessions Count

Aggregate Timed Out HTTP Sessions Count

View the Web Container

To view the web container information, select the WebSphere Web Container node in

the Investigator tree.

The Investigator displays the Web Container tab view.

The Web Container tab view includes the Aggregate Requests Graphical Summary tab

which presents a graphical representation of:

Aggregate Requests

Service Requests Per Interval

Average Service Request Time (ms)


21/30



View Individual Requests

To view individual requests, select the WebSphere Individual Requests node in the

Investigator tree.

The Investigator displays the Individual Requests tab view.

The Individual Requests tab view includes the Aggregate Requests Tabular Summary

tab, which presents a summary table of Web Container Requests.

View Request Details

To view request details, select the WebSphere Request Details node in the Investigator

tree.

The Investigator displays the Request Details tab view.

The Request Details tab view includes:

The Web Container Request Details View for each servlet or EJB

A graphical representation of an aggregate of requests

Responses per interval

The overall average response time


22/30


23/30


Appendix A: Metrics


WebSphere for z/OS Metrics(see page 23)

WebSphere 7 Metrics(see page 26)

WebSphere for z/OS Metrics

The following metrics are available for use in WebSphere for z/OS:

WebSphere|HTTP Session Objects:Aggregate Active HTTP Sessions Count

Aggregate of all active HTTP session objects processed.

WebSphere|HTTP Session Objects:Aggregate Invalidated HTTP Sessions Count

Aggregate of all logouts and invalidated user HTTP session objects.

WebSphere|HTTP Session Objects:Aggregate Live HTTP Sessions Count

Aggregate of all HTTP session objects that the system queues and processes.

WebSphere|HTTP Session Objects:Aggregate Read External Session Data Count

Aggregate of all Reads to read back HTTP session objects.

WebSphere|HTTP Session Objects:Aggregate Timed Out HTTP Sessions Count

Aggregate of timed out user HTTP session objects.

WebSphere|HTTP Session Objects:Aggregate Write External Session Data Count

Aggregate of all Writes to write out an HTTP session object.

WebSphere|HTTP Session Objects:Average Response Time

Average response time for HTTP session objects.

WebSphere|HTTP Session Objects:Concurrent Invocations

Total number of concurrent invocations.

WebSphere|HTTPSession Objects:Live HTTP Sessions Count

Number of HTTP session data objects currently queued in the system.

WebSphere|HTTP Session Objects:New HTTP Sessions Count Per IntervalNumber of new HTTP session objects created in the last time (15 second) interval.


24/30



WebSphere|HTTP Session Objects:New Invalidated HTTP Sessions Count Per Interval

Number of HTTP session objects invalidated in the late time (15 second) interval.

WebSphere|HTTP Session Objects:New Timed Out HTTP Sessions Count Per Interval

Number of HTTP session objects that timed out in the last reported interval.

WebSphere|HTTP Session Objects|Get JDBC Connection:Aggregate Count

Aggregate number of JDBC Connections that HTTP session objects per interval

requested.

WebSphere|HTTP Session Objects|Get JDBC Connection:Average Response Time (ms)

Average response time of HTTP session objects that are attempting to get a JDBC

Connection.

WebSphere|HTTP Session Objects|Get JDBC Connection:Responses Per Interval

The number of JDBC Connection responses per interval.


Sessions:Aggregate Count

Aggregate count of persisted session requests by HTTP session objects.

WebSphere|HTTP Session Objects|Get JDBC Connection and Persist Sessions:Average

Response Time (ms)

Average response time of HTTP session objects attempting to get a JDBC

Connection to persist the associated session object.


Sessions:Responses Per Interval

Number of responses for persisted HTTP session objects per Interval.

WebSphere|HTTP Session Objects|Get JDBC Connection and Read Sessions:Aggregate

Count

Aggregate count of session objects read in from JDBC backed table because of

requests from HTTP session objects.

WebSphere|HTTP Session Objects|Get JDBC Connection and Read Sessions:Average

Response Time (ms)

Average length of time that is required to obtain a JDBC Connection and read in a

persisted HTTP session object.

WebSphere|HTTP Session Objects|Get JDBC Connection and Read Sessions:Responses

Per IntervalNumber of JDBC responses during the last time interval.

WebSphere|Managed JDBC Connections: Aggregate Connections Opened/Closed

Count

Aggregate number of Managed JDBC Connections that performed the sequence of:

Open, process data, and then close.


25/30



WebSphere|Managed JDBC Connections|Connection Close:Average Response Time

(ms)

Average response time for a connection close request.

WebSphere|Managed JDBC Connections|Connection Close:Responses Per Interval

Number of connection close responses per interval.

WebSphere|Managed JDBC Connections|Connection Request: Average Response

Time (ms)

Average JDBC get connection request response time.

WebSphere|Managed JDBC Connections|Connection Request:Responses Per Interval

Number of connection requests to a JDBC per interval.

WebSphere|Web Container:Aggregate Requests

Aggregate of all web container requests invoked.

WebSphere|Web Container:Average Service Request Time (ms)

Average responsiveness of all requests to the application server.

Note: Average Service Request Time and Average Service Response Time represent

the same metric.

WebSphere|Web Container:Service Requests Per Interval

Number of requests per Interval to the application server.

WebSphere|Web Container:Servlet Exception Count

Unhandled servlet exceptions that occurred while dispatching a servlet (or JSP)

request.

WebSphere|Web Container|Individual Requests|:Aggregate

Requests

Aggregate of requests that are made to appserver, for the specified servlet class

name.

WebSphere|Web Container|Individual Requests|: Average

Response Time (ms)

Average response time of requests to appserver by the servlet class name.

WebSphere|Web Container|Individual Requests|:Concurrent

Invocations

Number of concurrent invocations.WebSphere|Web Container|Individual Requests|:Errors Per

Interval

Number of errors per interval by servlet.


26/30

WebSphere 7 Metrics


WebSphere|Web Container|Individual Requests|:Responses Per

Interval

Number of responses per interval that are made per servlet class name.

WebSphere|Web Container|Individual Requests|:Stall Count

Number of stalls per servlet class name.

WebSphere 7 Metrics

The following metrics apply to WebSphere 7 only.

WebSphere|Managed DBMS Connections:Aggregate Connections Opened/Closed

Count

Aggregate number of database (DBMS) related connections that the WebSphere

"Managed RDB" support used. This support is primarily invoked as part of Container

Managed persistence, and related activities.

WebSphere|Managed DBMS Connections:Currently Active Connections Count

Number of JDBC connections currently in use by WebSphere. These connections

can be in use for such things as:

HTTP Session objects

Container Managed persistence

Other activities using WebSphere Managed JDBC sessions

WebSphere|Managed DBMS Connections|Connection Request:Average Response

Time (ms)

Average response time for requests that are sent to a back-end database (DBMS),

as part of the WebSphere "Managed RDB" support.

WebSphere|Managed DBMS Connections|Connection Request:Responses Per Interval

Number of requests that are sent to a back-end database, over a 15-second

interval, as part of the WebSphere "Managed RDB" support.

WebSphere|Managed DBMS Connections|Connection Close:Average Response Time

(ms)

Average response time for closing a connection to a back-end database, as part of

the WebSphere "Managed RDB" support. Gives an approximation of the amount of

overhead that occurred during termination of a database request.

WebSphere|Managed DBMS Connections|Connection Close:Responses Per Interval

Total count of connection closes issued to a back-end database as part of the

WebSphere "Managed RDB" support.


27/30

WebSphere 7 Metrics


WebSphere|Managed DBMS Connections:Aggregate Connection Errors Count

Total count of connection errors that were encountered while trying to connect to a

back-end database as part of the WebSphere "Managed RDB" support.

WebSphere|Managed DBMS Connections:Connection Errors Per Interval

Number of errors occurring over a 15-second interval, when trying to connect to a

database, as part of the WebSphere "Managed RDB" support. A spike in these

numbers usually indicates that either the database crashed or the physical

connection (network, channel, and so forth) to the database failed.


28/30


29/30


Appendix B: Frequently Asked Questions


Why Do I Use the Extension to Monitor my WebSphere Application Server?(see page

29)

Why Are There Empty Panels in the Dashboards?(see page 29)

Why Are Not All the Metrics in the Documentation?(see page 30)

Why Do I Use the Extension to Monitor my WebSphereApplication Server?

Symptom:

Why do I use the extension to monitor my WebSphere Application Server?

Solution:

The extension monitors a number of WebSphere operations that the IBM WebSphere

Development team provided details. The extension monitors operations, which are

deemed performance-critical by IBM. The extension also comes with preconfigured

dashboards for monitoring performance metrics on other attributes, such as:

GC Heap

Sockets Bandwidth

File input/output Rate

JSP / Servlet / JDBC performance

Why Are There Empty Panels in the Dashboards?

Symptom:

Why am I seeing empty panels in the dashboards?

Solution:

The dashboards are created to showcase a general set of performance metrics out of

the extension. You are seeing empty panels because your applications do no use those

metrics. To customize the dashboard and the extension for your application

environment, consult CA Technologies Professional Services.


30/30

Why Are Not All the Metrics in the Documentation?

Why Are Not All the Metrics in the Documentation?

Symptom:

Why am I not seeing all the metrics listed in the documentation?

Solution:

You only see performance data for those WebSphere resources/components that your

application uses.

APM_9.5--APM for IBM WebSphere Application Server ZOS Guide

Documents

Transcript of APM_9.5--APM for IBM WebSphere Application Server ZOS Guide