Вы находитесь на странице: 1из 42

CA Application Performance

Management Guide

CA Application Performance Management Integration 3.1.2


Document Revision 66
Thursday, April 11, 2013
Confidential and Proprietary
Information in this book is subject to change without notice. Names used in examples are fictitious
unless otherwise noted. No part of this document may be reproduced or transmitted in any form or
by any means, for any purpose, without the express written permission of Netuitive, Inc.

Copyright 2001-2013, Netuitive, Inc. All rights reserved.

Netuitive, Netuitive Analytics, Real-time Analysis Engine, Trusted Alarms, Trusted Alarm, Trusted
Incidents, and Trusted Incident are trademarks of Netuitive Incorporated. Netuitive products are
covered by patents and pending applications for one or more U.S. and international patents.

Netuitive contains software whose copyright is owned by MySQL AB. All other company and
product names may be trademarks of the respective companies with which they are associated.

Address correspondence to the following address:


Netuitive, Inc.
12700 Sunrise Valley Drive
Reston, Virginia 20191
USA
http://www.netuitive.com

This document and its content is the copyright of Netuitive, Inc. Netuitive, Inc. 2001-2013. All
rights reserved.

This document is subject to a license agreement and may not be used by any party not bound to the
terms of the license agreement. Any redistribution or reproduction of part or all of the contents in
any form, or any use other than as specifically permitted under the license agreement is strictly pro-
hibited.

Distribution or commercial exploitation of the content without the express written permission of
Netuitive, Inc. is strictly prohibited.

CA Application Performance ManagementiGuide


i
Confidential and Proprietary
Contents
About this document iv

Technical support iv

Chapter 1: Release notes 1

What's new 1

What's fixed 1

Known issues 1

Chapter 2: Overview 3

Chapter 3: Integration installation 5

System requirements 5

Installing the CA APM drop-in 5

Importing the CA APM Remote Collector plug-ins 6

Troubleshooting 7

Chapter 4: CA APM Environment Preparation 8

Filters 8

Communication port 8

Chapter 5: CA APM Configuration in Netuitive 9

Setting process mappings 9

Configuring CA APM Remote Collector plug-ins 11

Configuring connection attempts 14

Configuring domain groups 14

Configuring a CA APM data source in Netuitive 15

CA APM data collection 16

CA APM groups 16

CA APM Managed Elements 16

Chapter 6: Template Reference 18

CA Application Performance ManagementiGuide


ii
Confidential and Proprietary
Template references 18

Customer Experience Manager 18

JBoss 20

Tomcat 23

Web Application 26

WebLogic 27

WebSphere 31

Appendix A: Archived release notes 34

What's new 34

What's fixed 35

CA Application Performance ManagementiGuide


iii
Confidential and Proprietary
About this document
The CA Application Performance Management Guide discusses new features, fixes, known
issues, and changes in the current release of the CA Application Performance Management (CA
APM) integration. The document also provides information on how to install, configure, or upgrade
to the current release. Information in this document is frequently updated. Be sure to read this doc-
ument each time you install or upgrade your CA APM integration.

In this guide, you will find some documentation conventions designed to help you identify important
items, variables, and other information. This document contains bookmarks viewable as a table of
contents in your PDF viewer. Each chapter starts with a mini table of contents that link to the
chapter's content section by section.

Variables are offset by angle brackets or by italicized text. Angle brackets are most frequently used
around placeholders for values or directories. Italicized text is used to refer to the variable contained
within the angle brackets. Examples appear below:

l Open the <Netuitive installation directory>/scripts/linux/<distribution> directory where distribution is


either redhat or suse.
l After configuration, the JMX client can continue to connect via the JMX URL where hostname and
port1 are placeholders for the actual values:
service:jmx:rmi:///jndi/rmi://<hostname>:<port1>/nsiremote

For both of the above examples, replace the angle brackets and variables with the actual value.

Notes, tips, and important information are offset by colored text and start with the word Note,
Important, or Tip. Each table and figure is labeled with a number that corresponds to the chapter
where the table or figure is found and a description of the table or figure. These numbers serve as
bookmarks, allowing you to reference the table.

Technical support
We encourage you to visit the Netuitive support website at http://support.netuitive.com for any
product-related question or issue.

From the support site, you can:

l Download software versions and recent updates.


l Access up-to-date product manuals in PDF format.
l Open a Support Request if you experience problems installing or using the product.
l Send an email to product@netuitive.com to open an Enhancement Request if you have suggestions
on how to improve our product in a future version.
l Transfer your data via FTP for analysis by Netuitive.
l Contact sales for upgrades or information about upcoming versions.

CA Application Performance ManagementiGuide


iv
Confidential and Proprietary
About this document

l Access the Knowledge Base (KB), which includes FAQs, known issues, glossary terms, and other
support articles.

Access to our support website requires an individual account. If you do not have a support website
account or do not remember your login and password, please use the appropriate links on the main
support site page. If you wish to speak directly to one of our customer support representatives,
please contact us by one of the following means:
Netuitive, Inc.
Attn.: Technical Support
12700 Sunrise Valley Drive
Reston, VA 20191
E-mail: support@netuitive.com
Telephone: +1-703-464-1508

CA Application Performance ManagementiGuide


v
Confidential and Proprietary
Chapter 1: Release notes
What's new 1

What's fixed 1

Known issues 1

What's new
No new features were introduced in the CA APM 3.1.2 integration.

What's fixed
The following issues have been resolved in the CA APM 3.1.2 integration:

l The Aggregated Transaction Count (2521) metric is no longer correlated. This metric appears in the
Customer Experience Manager template in the APP resource type.
l The Memory Bytes In Use (2711) metric is no longer correlated. This metric appears in the JBoss,
Tomcat, WebLogic, and WebSphere templates in the MEM resource type.

Known issues
The following are known issues with the CA APM 3.1.2 integration:

l Because the CA APM 3.x integration creates new types of Managed Elements and uses new and
extensively revised templates, a direct upgrade from CA APM 2.x is not supported. This means that
the history of the CA APM 2.x Managed Elements cannot be moved to CA APM 3.1.2 Managed Ele-
ments because they are of different types.
l Clustering Application Server and Web Application Managed Elements is not supported in Netuitive
5.5. For the ability to cluster these types of Managed Elements, you must upgrade to Netuitive 6.0.
l The calculation of HTTP Session Utilization Percent (3997) may be off by a small percentage when
the Max Pool Size is set on some HTTP Session Pools but not on all HTTP Session Pools.
l When looking at the Workload Assistant for a Web Application, it is not possible to distinguish to
which group the metrics used to compute the values for the All URL Groups belong. Refer to Intro-
scope to determine which group is having problems.
l In order for relationships between servers (host machines being monitored) and application servers
to exist in Netuitive, the host name returned by CA APM must match the host name being provided
by other integrations. If server host names contain fully qualified domain names in Netuitive, then it
is recommended that host names be configured in CA APM with fully qualified domain names as
well.

CA Application Performance ManagementiGuide


1
Confidential and Proprietary
Chapter 1: Release notes

l If you are using Introscope Enterprise Manager 9.x, when running in historical mode, the command
fails with the error message that it is unable to parse the date. This error is the result of an issue with
CA APM, not Netuitive.
l The timestamp on historical data in instances of the CA Introscope CLW Historical Data plug-in in
Remote Collector may be off by one hour. This is the result of an issue with the handling of time
zones using EST, MST, and HST abbreviations in recent JDK releases. A workaround is available
on the Sun Web site at: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6530336. The JRE
for Remote Collector is located in the <Remote Collector install home>/jre directory.
l The CA APM data source creates a single Transaction Set Managed Element that is the parent of
several aggregated transactions used to monitor CEM metrics. The following metrics show up as
Not Found for that particular Transaction SetManaged Element:
l Aggregated Transaction Count
l Transactions Per Interval With Availability Defects
l Transactions Per Interval With Performance Defects

CA Application Performance ManagementiGuide


2
Confidential and Proprietary
Chapter 2: Overview
The CA APM integration is used to collect performance data at regular intervals from Introscope
Enterprise Manager for real-time analysis in Netuitive. It also supports collection of historical data
from Introscope Enterprise Manager. Figure 2-1 illustrates this integration.

This integration supports collection of performance measurements for Application Servers, Web
Applications, Customer Experience Manager (CEM), and custom applicationsif added. Data is col-
lected using the Remote Collector.

Netuitive collects and aggregates measurements from the Remote Collector database every 15
minutes by default. Templates in Netuitive specify the measurements that are retrieved and ana-
lyzed. Templates are provided for CEM, JBoss, Tomcat, Web Application, WebLogic, and
WebSphere. Custom templates can be created to support data from custom applications.

CA Application Performance ManagementiGuide


3
Confidential and Proprietary
Chapter 2: Overview

Figure 2-1: CA APM integration architecture

CA Application Performance ManagementiGuide


4
Confidential and Proprietary
Chapter 3: Integration installation
System requirements 5

Installing the CA APM drop-in 5

Importing the CA APM Remote Collector plug-ins 6

Troubleshooting 7

System requirements
Table 3-1 describes system requirements. The default Introscope Enterprise Manager com-
munication channel (default port =5001) must be enabled.

Product Version
Netuitive 6.0 or 5.5 SP8
Remote Collector 2.1.0
Introscope Enterprise Manager 9.1, 8.2.1, 8.0.2.3
Apache Tomcat 7.0.x, 6.0.x, and 5.5.x
JBoss 7.x, 6.x, 5.x, and 4.x
WebLogic 11gR1 (10.3.x), 10.3, 10.0, and 9.x
WebSphere 8.0, 7.0, and 6.1
Table 3-1: System requirements

In addition, you must use the correct CLWorkstation.jar file with all versions of Introscope Enter-
prise Manager.

Installing the CA APM drop-in


The CA APM drop-in is a package installed through the Netuitive Console.

Note If you were using the CA APM 2.x integration with Netuitive, you can install the CA APM
3.1.2 drop-in to run side by side with CA APM 2.x.

To install the CA APM drop-in for Netuitive 6.0

1. Stop the Netuitive Analytics Service and the Netuitive Proxy Collector service.
2. On the Administration menu, under Licenses / Installs, click Packages.
3. Click Install Package.

CA Application Performance ManagementiGuide


5
Confidential and Proprietary
Chapter 3: Integration installation

4. Specify the package to install (file with path name) or click Browse to locate the package in your file
system.
5. For Update Database, select Yes to run any database scripts associated with the drop-in.
6. Click Submit. All files in the package are automatically deployed.
7. Restart the Netuitive Analytics Service, the Netuitive Proxy Collector service, and the Tomcat ser-
vice.
8. Scan the CA APM data source.

To install the CA APM drop-in for Netuitive 5.5

1. Stop the Netuitive Analytics Service and the Netuitive Proxy Collector service.
2. On the Administration menu, under Licenses/Installs, click Install Package.
3. Specify the package to install (file with path name) or click Browse to locate the package in your file
system.
4. For Update Database, select Yes to run any database scripts associated with the drop-in.
5. Click Submit. All files in the package are automatically deployed.
6. Restart the Netuitive Analytics Service, the Netuitive Proxy Collector service, and the Tomcat ser-
vice.
7. Scan the CA APM data source.

See the Netuitive Operations Guide for more information about scanning data sources and starting,
stopping, or restarting services.

Importing the CA APM Remote Collector plug-ins


The CA APM integration uses Remote Collector to store data. The CA APM integration requires at
least one plug-in to be imported and configured in the Remote Collector. For more information on
the Remote Collector, see the Netuitive Remote Collector Users Guide.

To import the CA APM Remote Collector plug-in

1. Open the Remote Collector Console.

2. Click the Manage Plugin button .

3. In the Manage Plugins window, click the Import Plugin button .


4. Locate and open the CA APM plug-in. This plug-in is found within the CA APM package in the fol-
lowing location: \scripts\wily\rc-wily-plugin.zip. Once selected, click OK.
5. Close the Manage Plugins window.
6. Copy the CLWorkstation.jar located in the <Introscope Enterprise Manager install-
ation directory>/lib directory to the <Remote Collector installation dir-
ectory>/plugins/wily/scripts directory.

CA Application Performance ManagementiGuide


6
Confidential and Proprietary
Chapter 3: Integration installation

Note CLWorkstation.jar is a CA product that can only be found in existing installations of


Introscope Enterprise Manager. If CLWorkstation.jar is not located on the same machine as
the Remote Collector then it must be copied to the Remote Collector machine.

7. Restart the Netuitive Remote Collector service.

Troubleshooting
The following are tips to help troubleshoot issues with the CA APM integration:

l No data in Remote Collector: Ensure that you have configured process mapping settings in con-
fig.xml for each application type monitored (CEM, JBoss, Tomcat, Web Application, WebLogic, and
WebSphere).In addition, the agentfilter and metricfilter fields cannot be left blank when configuring
the plug-ins in Remote Collector. See"Setting process mappings" on page 9 and "Configuring CA
APM Remote Collector plug-ins" on page 11 for more information.
l Data not collecting and timeout messages appearing or integration not behaving as expec-
ted: Be sure that your CA APM Remote Collector plug-in is using the correct version of CLWork-
station.jar.

CA Application Performance ManagementiGuide


7
Confidential and Proprietary
Chapter 4: CA APM Environment
Preparation
The following topics are discussed in this chapter:

Filters 8

Communication port 8

Filters
To prepare the CA APM environment, you must set up filters to collect the necessary metrics from
Introscope Enterprise Manager for use by templates in Netuitive for data analysis.

It is important to understand what data from Introscope Enterprise Manager are analyzed by Netu-
itive. Use the regular expression (regex) filtering capability for CA APM agents and metrics to pre-
vent Remote Collector from collecting unnecessary data. The regex filter reduces the overhead for
the data collection; see "Configuring CA APM Remote Collector plug-ins" on page 11.

Communication port
You must enable the default Introscope Enterprise Manager communication channel. The default
port is 5001. The port must match the port entered for the Remote Collector plug-in. For more inform-
ation, see "Configuring CA APM Remote Collector plug-ins" on page 11.

CA Application Performance ManagementiGuide


8
Confidential and Proprietary
Chapter 5: CA APM Configuration in
Netuitive
The following topics are discussed in this chapter:

Setting process mappings 9

Configuring CA APM Remote Collector plug-ins 11

Configuring connection attempts 14

Configuring domain groups 14

Configuring a CA APM data source in Netuitive 15

CA APM data collection 16

CA APM groups 16

CA APM Managed Elements 16

Setting process mappings


Process mappings control what data is available for the CA APM plug-in to collect. Process map-
pings must defined for each application from which CA APM is collecting data. Process mappings
are defined in a subsection of the plug-in's local configuration file, config.xml, located in the
<Remote Collector Install Folder>/plugins/wily/conf directory.

Each entry in the process mappings subsection is defined with the following settings:

l name: The name of the process (or application) being monitored by CA APM.
l enabled: Use this flag to enable or disable processing metrics.
l columns: A list of fields (columns) that the process mapping pattern should be applied to when
attempting to map data to processes. The default value for this field is Process and the supported val-
ues for this setting are the header column names for the delimited data that is provided by the
CLWorkstation command line. This field should be a comma separated list and will be applied in the
order specified.
l pattern: A regular expression to match on the process name CA APM is using.
l qualify-agent-enabled: Use this flag to fully qualify agent names (enabled for CEM only). When
enabled, Application Server Managed Element names in Netuitive will appear as <host name> :
<application server name> : <agent name> and Web Application Managed Element names in Netu-
itive will appears as <host name> : <application server name> : <agent name> : <web application
name>.

CA Application Performance ManagementiGuide


9
Confidential and Proprietary
Chapter 5: CA APM Configuration in Netuitive

Take caution when updating the process mapping files. Keep the following items in mind:

l When customizing the regular expression for a particular process mapping, ensure that the regular
expression will not match against any of the other process mappings. A particular input should match
one and only one pattern from any process mapping. Allowing the regular expression to be matched
against any of the other process mappings will lead to unpredictable behavior.
l If you define two process mappings with the same <name>, then the last specified process wins.
Defining the same process mapping twice is not recommended.

Important If you customize the config.xml file remember that the Remote Collector will not col-
lect data until the process mapping files are configured correctly. The integration contains default
mappings that the Remote Collector will use to collect data.

The process mapping subsection is defined with factory defaults as follows:


<!-- Process Mappings -->
<!-- jboss process mapping -->
<process-mapping>
<name>JBoss</name>
<enabled>true</enabled>
<columns>Process</columns>
<pattern>.*([Jj][Bb]oss).*</pattern>
</process-mapping>
<!-- tomcat process mapping -->
<process-mapping>
<name>Tomcat</name>
<enabled>true</enabled>
<columns>Process</columns>
<pattern>.*([Tt]om[Cc]at).*</pattern>
</process-mapping>
<!-- weblogic process mapping -->
<process-mapping>
<name>WebLogic</name>
<enabled>true</enabled>
<columns>Process</columns>
<pattern>.*([Ww]eb[Ll]ogic).*</pattern>
</process-mapping>
<!-- websphere process mapping -->
<process-mapping>
<name>WebSphere</name>
<enabled>true</enabled>
<columns>Process</columns>

CA Application Performance ManagementiGuide


10
Confidential and Proprietary
Chapter 5: CA APM Configuration in Netuitive

<pattern>.*([Ww]eb[Ss]phere).*</pattern>
</process-mapping>
<!-- cem process mapping -->
<process-mapping>
<name>CEM</name>
<enabled>true</enabled>
<columns>Process</columns>
<pattern>
.*[Cc]ustom\s[Mm]etric\s[Pp]rocess\s\([Vv]irtual\)|
[Cc][Ee][Mm].*
</pattern>
<qualify-agent-enabled>false</qualify-agent-enabled>
</process-mapping>

Configuring CA APM Remote Collector plug-ins


There are two types of CA APM plug-ins:

l CA Introscope CLW CLW plug-in for real-time data collection


l CA Introscope CLW Historical Data for historical data collection

You must create at least one instance of the CA Introscope CLW plug-in in Remote Collector to
configure and set the parameters for data collection from the Introscope Enterprise Manager envir-
onment.

When the Remote Collector collects historical data, it is stored only in memory. If you want to store
the data for later offline analysis, you must configure an external NDB database for Remote Col-
lector to store historical data. The default installation of Remote Collector will store the data only in
memory.

In the Remote Collector console, you can only view historical data up to 30 minutes before now.

Note When configuring the plug-ins, the agentfilter and metricfilter fields cannot be left blank.

To configure the CA Introscope CLW plug-in in Remote Collector

1. Open the Remote Collector Console.

2. Click the Manage Plugin button .


3. In the Manage Plugin window, select CA Introscope CLW Plugin, and then click the New Plugin

button .
4. Set the parameters.
5. Click OK, then Yes, and then OK to confirm.

The parameters for the CA Introscope CLW plug-in are:

CA Application Performance ManagementiGuide


11
Confidential and Proprietary
Chapter 5: CA APM Configuration in Netuitive

l Name: This name will be used to create the data source in Netuitive.
l hostname: Introscope Enterprise Manager host name.
l port: Introscope Enterprise Manager port number (default 5001).
l user: Introscope Enterprise Manager user name.
l password: Password for the user.
l cycleTime: How often (in seconds) to poll the Introscope Enterprise Manager. Acts as the default
timeout value.
l agentfilter: Use a regular expression filter on Introscope Enterprise Manager agents matching
(Host|Process|Agent). This field accepts special characters (for example, .*\|WebLogic.*?\|.* ). See
"Filter settings " on page 12 for suggested regular expressions that apply to each agent.
l metricfilter: Use a regular expression filter on Introscope Enterprise Manager metrics matching
(Resource|MetricName). This field accepts special characters (for example, .Fron-
tends\|Apps\|EJB3.* ). See "Filter settings " on page 12 for suggested regular expressions that apply
to each agent.

l offset: Offset in seconds to poll the Introscope Enterprise Manager. The default is 0, meaning no off-
set. If you set an offset value, when the CA Introscope CLWplug-in starts data collection, it will
query the Introscope Enterprise Manager server using the time range query with starttime = cur-
renttime - datainterval - offset, and endtime = currenttime - offset. For example, say the current time
of the Remote Collector is 17:50:25 UTC. The current time is converted to Remote Collector host
server local time using the time zone specified (for example, America/New_York), so the current
local time is 2009-09-23 13:50:25. If the offset is 30 seconds, the query time range will be between
"2009-09-23 13:44:55" and "2009-09-23 13:49:55" if the data interval is set to 300 seconds (the
default in the config file). By default, when the data arrives at the Remote Collector, the data
timestamp will be stamped as the system time when the data gets processed. If you want to use the
timestamp for that data point marked by Introscope Enterprise Manager server, set the <offset-
timestamp-current> element in config.xml to false. The config.xml file is located in the
<Remote Collector install home>/plugins/wily/conf directory.
l timeZone: Time zone of the CA APM host server. Valid IDs can be found in the TimeZoneIDs.txt
file located in the <Remote Collector install home>/plugins/wily/conf directory.
The default value is America/New_York.

If you set the agent filter or metric filter, in the Remote Collector Console you will only see the met-
ric data that match the filter specified.

Filter settings
Use the following regular expressions for the agentfilter and metricfilter fields when configuring
the Remote Collector CA Introscope CLW plug-in.
Tomcat agentfilter
.*\|Tomcat\|.*
Tomcat metricfilter
(CPU:.*|GC Heap:.*|GC Monitor:.*|Frontends\|Apps\|[^|]+:.*|
Frontends\|Apps\|[^|]+\|URLs\|.*|JMX\|Catalina\|

CA Application Performance ManagementiGuide


12
Confidential and Proprietary
Chapter 5: CA APM Configuration in Netuitive

.*:(currentThreadsBusy|currentThreadCount|maxThreads|numActive|
maxActive|numIdle|activeSessions|maxActiveSessions)|Threads:.*|
Tomcat.*)
JBoss agentfilter
.*\|JBoss\|.*
JBoss metricfilter
(CPU:.*|GC Heap:.*|GC Monitor:.*|Frontends\|Apps\|
[^|]+:.*|Frontends\|Apps\|[^|]+\|URLs\|.*|JMX\|jboss.*\|
.*:(currentThreadsBusy|[Cc]urrentThreadCount|[Mm]axThreads|
InUseConnectionCount|ConnectionCount|MaxSize|
AvailableConnectionCount|activeSessions|maxActiveSessions)|
Threads:.*)
WebLogic agentfilter
.*\|WebLogic\|.*
WebLogic metricfilter
(CPU:.*|GC Heap:.*|GC Monitor:.*|Frontends\|Apps\|
[^|]+:.*|Frontends\|Apps\|[^|]+\|URLs\|.*|JMX\|com\.bea\|
.*:(ExecuteThreadTotalCount|ExecuteThreadIdleCount|Throughput|
ExecuteThreadCurrentIdleCount|PendingRequestCurrentCount|
PendingRequests|StuckThreadCount|OpenSocketsCurrentCount|
ActiveConnectionsCurrentCount|CurrCapacity|MaxCapacity|
WaitingForConnectionCurrentCount|LeakedConnectionCount|
OpenSessionsCurrentCount)|Threads:.*)
WebSphere agentfilter
.*\|WebSphere\|.*
WebSphere metricfilter
(CPU:.*|GC Heap:.*|GC Monitor:.*|Frontends\|Apps\|
[^|]+:.*|Frontends\|Apps\|[^|]+\|URLs\|.*|WebSpherePMI\|
(threadPoolModule|connectionPoolModule|servletSessionsModule):
(ActiveCount|PoolSize|PercentMaxed|PercentUsed|
FreePoolSize|WaitTime|LiveCount)|Threads:.*)
CEM agentfilter
(Custom Metric Host \(Virtual\)\|
Custom Metric Process \(Virtual\)\|CEM Agent|.*\|CEM\|TESS Agent)
CEM metricfilter
(Business Service\|[^|]+\|Business Transactions\|
[^|]+.*|Business Segment\|[^|]+\|[^|]+\|[^|]+:.*)
To enable additional metrics, use the following optional regular expressions for metricfilter:
|Backends\|[^|]+:.*

CA Application Performance ManagementiGuide


13
Confidential and Proprietary
Chapter 5: CA APM Configuration in Netuitive

|EJB\|[^|]+\|[^|]+:.*
|JSP:.*
|Servlets:.*
The parameters for the CA Introscope CLW Historical Data are the same as for the CA Introscope
CLW plug-in with the following additional required fields:

l startDate: YYYY-MM-DD hh:mm:ss in Remote Collector host server time zone; starts the interval
for collection.
l endDate: YYYY-MM-DD hh:mm:ss in Remote Collector host server time zone; ends the interval for
collection.
l aggregateFrequency: Data aggregate interval (in seconds); by default it is 300 seconds, meaning
that the historical data is aggregated at 5 minute intervals.
l dataPointsPerCycle: Number of aggregate data points per polling cycle; default value is 1, meaning
each polling cycle only collects 1 data point. If set to 5, each polling cycle will retrieve 5 data points.
l simulate: By default this is false, which means the timestamp of the actual data is being used and
stored. If set to true, it makes historical data current for real-time analysis by Netuitive by setting the
time the data arrives to Remote Collector as the real time. If using simulate, the default values
should be used for cycleTime (300), aggregateFrequency (300), and dataPointsPerCycle (1). It is
a waste of resources to poll more often or collect more data points per cycle.

You can accelerate the speed of the historical data collection by using a smaller cycle time, for
example 60 seconds, or using a larger number for data points per cycle or a combination of both.

Configuring connection attempts


If the CA APM plug-in cannot connect to the Introscope Enterprise Manager after 3 attempts, the
plug-in fails. Once the plug-in fails, you must manually restart it from within the Remote Collector
console.

The number of attempts to connect before failing can be configured by changing the <number-of-
cycles-to-attempt-connection> element in the config.xml file located in <Remote Collector install
home>/plugins/wily/conf directory.

Configuring domain groups


To configure groups to set a domain/server relationship in Netuitive, you must customize the
domain-group.xml.example file in the <Remote Collector install home>/plu-
gins/wily/config directory.

When you configure the domain group file, it adds domain groups to Netuitive for all CA APM real-
time plug-in instances running on that Remote Collector.You don't have to configure a file for each
CA APM plug-in instance.

To configure the domain-group.xml.example file

1. Set the value of <process-domain-as-group> element to true.


2. Define the Netuitive servers that will receive the group information by entering the hostname, port,
user, and password.The password can be provided as plain text or encrypted by the using the

CA Application Performance ManagementiGuide


14
Confidential and Proprietary
Chapter 5: CA APM Configuration in Netuitive

encrypt utility. If the password is encrypted, the value of <encrypted> element needs to be set as
true.
3. If you have multiple Netuitive instances scanning the same Remote Collector and want all of them to
receive this group information, create multiple <netuitive_si> elements under <netuitive_sis>.
4. By default, the group root path is set as Enterprise which corresponds to the Enterprise group in Netu-
itive. Define a group root path under Enterprise if desired, for example, Enterprise/IntroscopeGroup.
The separator in the group definition is a forward slash (/), not a backslash (\).
5. Rename the domain-group.xml.example file to domain-group.xml.
6. Stop and start all CA APM plug-in instances to reload the configuration changes. After a cycle, you'll
see the CA APM Domain group.

The encrypt utility is an executable called encrypt.jar located in the <Remote Collector
install home>/plugins/wily/lib directory. To run it, type java -jar encrypt.jar <your
plain password>. The output is the encrypted password that you can copy and paste into the
domain-group.xml file.

Configuring a CA APM data source in Netuitive


You must configure a data source in Netuitive to collect data from each CA APM plug-in instance in
the Remote Collector.

Before starting this procedure, you need to first install the CA APM drop-in and configure a CA APM
Remote Collector plug-in. See "Chapter 3: Integration installation" on page 5 for instructions.

To configure a CA APM data source for Netuitive 6.0

1. On the Administration tab, under Integrations, click Data Sources.


2. Click New Data Source.
3. Click Remote Collector.
4. For Name, type the name of the CA APM plug-in that was created in the Remote Collector.
5. Optional: For Description, type a short description.
6. For Remote Collector, select the name of the Remote Collector instance that contains the CA APM
plug-in.
7. For Match Against, select caapm.
8. Click Submit.
9. Scan the data source.

To configure a CA APM data source for Netuitive 5.5

1. On the Administration tab, under Integrations, click New Data Source.


2. Click Remote Collector.
3. For Name, type the name of the CA APM plug-in that was created in the Remote Collector.
4. Optional: For Description, type a short description.

CA Application Performance ManagementiGuide


15
Confidential and Proprietary
Chapter 5: CA APM Configuration in Netuitive

5. For Remote Collector, select the name of the Remote Collector instance that contains the CA APM
plug-in.
6. For Match Against, select caapm.
7. Click Submit.
8. Scan the data source.

See the Netuitive Operations Guide for information on scanning data sources.

CA APM data collection


The CA APM integration monitors only application servers (CEM, WebSphere, WebLogic, and Tom-
cat). It does not monitor host servers. Other monitoring technology with integrations to Netuitive
must be deployed to the host server first to create a complete Server Managed Element in Netu-
itive.

CA APM groups
If the CA APM integration is configured to collect domain group information, domain names will be
added to Netuitive as groups.

Because each Introscope Enterprise Manager doesn't necessarily have the whole group rela-
tionship defined for all servers, and because data is processed per each CA APM plug-in instance,
this group support only adds groups to Netuitive.

If any domain changes in any CA APM, you must delete the deprecated group or all CA APMgroups
created in Netuitive.

If you specified a root path (for example, Enterprise/IntroscopeGroup) when configuring the domain
groups in Remote Collector, you can delete the root group (for example, IntroscopeGroup) in Netu-
itive.

CA APM Managed Elements


For the CA APM integration, Netuitive models the following Managed Element types:

l Application Server Managed Element: A type of Managed Element that represents JVMs and
may host one or more web applications. These Managed Elements names are displayed in the fol-
lowing manner: <host name> : <application server name> : <agent name>.
l Web Application Managed Element: A type of Managed Element that represents a web applic-
ation running on a typical application server. These Managed Element names are displayed in the fol-
lowing manner:<host name> : <application server name> : <agent name> : <web application name>
l Transaction Set Managed Element: A type of Managed Element that is defined as a group of
atomic transactions or aggregated transactions that measure different aspects of the same applic-
ation or service (CEMonly).
l Aggregated Transaction Managed Element: A type of Managed Element that represents actual
customer experience data (real data) as opposed to synthetic transaction data. It is an aggregate of
actual customer experience (CEMonly).

CA Application Performance ManagementiGuide


16
Confidential and Proprietary
Chapter 5: CA APM Configuration in Netuitive

Note Application Server and Web Application are new types of Managed Elements that require
license keys. If you plan on monitoring them, please contact your sales representative and request
license keys.

If the aggregated transaction count for Web Application and Aggregated Transaction Managed Ele-
ments is zero for a given cycle, then all metrics for these types of Managed Elements will show
missing data. This behavior is expected and will not cause alarms.

CA Application Performance ManagementiGuide


17
Confidential and Proprietary
Chapter 6: Template Reference
Template references 18

Customer Experience Manager 18

JBoss 20

Tomcat 23

Web Application 26

WebLogic 27

WebSphere 31

Template references
This chapter contains information about each template: name, version number, description, and a
list of metrics. Metrics are organized according to resource type (for example, CPU) and have the
following properties:

l The metric's name (for example, CPU user percent)


l The metric's ID number (for example, 101)
l The metric's description, if applicable
l The acceptable value range (high and low values), if applicable
l (KPI) if the metric is a Key Performance Indicator
l (AGI) if the metric is an Alarm Generation Indicator
l (Baselined) if the metric is analyzed as part of the normal behavior of the element
l (Correlated) if the metric is considered as part of the correlations between metrics
l (Computed) indicates that the metric's value may be calculated based on values of other metrics or
the value may be collected; metrics marked as computed may not be present if the required collected
metrics are not present
l (None) if the metric is not marked as (KPI), (AGI), (Baselined), (Correlated), or (Computed)
l (Manual) if the metric is disabled by default

Customer Experience Manager


This template contains Customer Experience Manager (CEM) metrics which CEM provides to Intro-
scope. CEM metrics give the end-to-end response times and related metrics for business trans-
actions. They are treated as Aggregated Transactions and Transaction Sets within Netuitive.

CA Application Performance ManagementiGuide


18
Confidential and Proprietary
Chapter 6: Template Reference

APP
Response Index (1919) Normalized view of how response time for this service compares to his-
torical values. (Range: 0.0..1) (KPI) (AGI) (Baselined) (Correlated) (Computed)

Set Response Index (1920) Characterization of response time across a transaction set. (Range:
0.0..1) (KPI) (AGI) (Baselined) (Correlated) (Computed)

Aggregated Transaction Count (2521) (Range: 0.0...) (KPI) (AGI) (Baselined) (Computed)

Web Response Index (2560) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Computed)

E2E Average Response Time (4045) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)

Transactions Per Interval With Availability Defects (4046) (Range: 0.0...) (KPI) (AGI)
(Baselined) (Correlated)

Transactions Per Interval (4047) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Computed)

Defects Per Interval (4048) (Range: 0.0...) (Baselined)

Defects With Missing Response Per Interval (4049) (Range: 0.0...) (Baselined)

Defects With Slow Time Per Interval (4050) (Range: 0.0...) (Baselined)

Transactions Per Interval With Performance Defects (4051) (Range: 0.0...) (KPI) (AGI)
(Baselined) (Correlated)

E2E Total Response Time (4052) (Range: 0.0...) (KPI) (AGI) (Baselined) (Computed)

Percentage Of Transactions With Availability Defects (4054) (Range: 0.0...) (KPI) (AGI)
(Baselined) (Computed)

Percentage Of Transactions With Performance Defects (4055) (Range: 0.0...) (KPI) (AGI)
(Baselined) (Computed)

Application Server Average Response Time (4056) (Range: 0.0...) (KPI) (AGI) (Baselined) (Cor-
related)

Application Server Responses Per Interval (4057) (Range: 0.0...) (KPI) (AGI) (Baselined) (Cor-
related)

Application Server Errors Per Interval (4058) (Range: 0.0...) (AGI) (Baselined) (Correlated)

Application Server Stall Count (4059) (Range: 0.0...) (AGI) (Baselined)

Application Server Concurrent Invocations (4060) (Range: 0.0...) (AGI) (Baselined) (Cor-
related)

Application Server Total Response Time (4061) (Range: 0.0...) (KPI) (AGI) (Baselined) (Com-
puted)

CA Application Performance ManagementiGuide


19
Confidential and Proprietary
Chapter 6: Template Reference

Average Transactions Per Interval (4064) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)
(Computed)

All Transaction - Application Server Average Response Time (4113) (Range: 0.0...) (KPI)
(AGI) (Baselined) (Correlated) (Computed)

All Transaction - Application Server Responses Per Interval (4116) (Range: 0.0...) (KPI) (AGI)
(Baselined) (Correlated) (Computed)

All Transaction - Application Server Errors Per Interval (4117) (Range: 0.0...) (AGI)
(Baselined) (Correlated) (Computed)

All Transaction - Application Server Stall Count (4118) (Range: 0.0...) (AGI) (Baselined) (Com-
puted)

All Transaction - Application Server Concurrent Invocations (4119) (Range: 0.0...) (AGI)
(Baselined) (Correlated) (Computed)

All Transaction - Application Server Total Response Time (4120) (Range: 0.0...) (KPI) (AGI)
(Baselined) (Computed)

All Transaction - Percentage With Availability Defects (4121) (Range: 0.0...) (KPI) (AGI)
(Baselined) (Computed)

All Transaction - Percentage With Performance Defects (4122) (KPI) (AGI) (Baselined) (Com-
puted)

All Transaction - E2E Average Response Time (4123) (Range: 0.0...) (KPI) (AGI) (Baselined)
(Correlated) (Computed)

All Transaction - Transactions Per Interval (4124) (Range: 0.0...) (KPI) (AGI) (Baselined) (Cor-
related) (Computed)

All Transaction - Defects Per Interval (4125) (Range: 0.0...) (Baselined) (Computed)

All Transaction - Defects With Missing Response Per Interval (4126) (Range: 0.0...)
(Baselined) (Computed)

All Transaction - Defects With Slow Time Per Interval (4127) (Range: 0.0...) (Baselined) (Com-
puted)

JBoss
This template contains Introscope metrics from JBoss application servers.

APP
Average Servlet Response Time (1517) Average time it takes for this servlet to respond. (Range:
0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

EJB Average Response Time (1521) Average response time across all methods for this EJB.
(Range: 0.0...) (Baselined) (Correlated) (Manual)

CA Application Performance ManagementiGuide


20
Confidential and Proprietary
Chapter 6: Template Reference

EJB Request Rate (1988) (Range: 0.0...) (Baselined) (Correlated) (Manual)

JSP Response Time (ms) (2713) Average response time in milliseconds for JSP to respond to a
web client request. (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

JSP Responses (2714) Average number of JSP responses per time interval. (Range: 0.0...) (KPI)
(AGI) (Baselined) (Correlated) (Manual)

Servlet Responses (2715) Average number of servlet responses per time interval. (Range: 0...)
(KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Response Time (ms) (2718) Average response time in milliseconds for a backend to
respond to a request. A backend is an external system that an application relies on for some portion
of its processing, normally a database. (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)
(Manual)

Backend Responses (2719) Average number of backend responses per time interval. A backend
is an external system that an application relies on for some portion of its processing, normally a
database. (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Stall Count (2728) Number of backend methods started but whose invocation times
have exceeded a threshold. (Range: 0...) (KPI) (AGI) (Baselined) (Manual)

EJB Stall Count (2732) Number of EJB methods started but whose invocation times have
exceeded a threshold. (Range: 0...) (Baselined) (Manual)

Backend Concurrent Invocations (4002) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)
(Manual)

Backend Errors Per Interval (4003) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

EJB Concurrent Invocations (4004) (Range: 0.0...) (Baselined) (Correlated) (Manual)

EJB Errors Per Interval (4005) (Baselined) (Correlated) (Manual)

EJB Responses Per Interval (4103) (Baselined) (Correlated) (Manual)

JSP Responses Per Interval (4104) (KPI) (AGI) (Baselined) (Correlated) (Manual)

JSP Average Response Time (4105) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Average Response Time (4106) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Responses Per Interval (4107) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Servlet Average Response Time (4108) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Servlet Responses Per Interval (4109) (KPI) (AGI) (Baselined) (Correlated) (Manual)

CPU
CPU Utilization Percent (100) Percentage of the CPU resource available that is consumed.
(Range: 0..100.0) (KPI) (AGI) (Baselined) (Correlated) (Computed)

CA Application Performance ManagementiGuide


21
Confidential and Proprietary
Chapter 6: Template Reference

CPU Index (1729) Index computation. (Range: 0.0..1.0) (Computed)

JVM
Threads Active (3979) 100 WebLogic (Range: 0.0...) (Computed)

Threads Maximum Pool Size (3981) (Range: 0.0...) (Computed)

Threads All Active (3984) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)

Threads Allocated (3987) (Range: 0.0...) (Computed)

Threads Utilization Percent (3988) (Range: 0.0..1.0) (KPI) (AGI) (Baselined) (Correlated) (Com-
puted)

JDBC Connections Allocated (3989) (Range: 0.0...) (Computed)

JDBC Connections Maximum Pool Size (3990) (Range: 0.0...) (Computed)

JDBC Connections Utilization Percent (3991) 100 JBoss/WebLogic 110 Tomcat 120 JBoss/We-
bLogic 130 WebSphere (Range: 0.0..1.0) (KPI) (AGI) (Baselined) (Correlated) (Computed)

JDBC Connections Idle (3992) 100 JBoss/WebLogic (Range: 0.0...) (Computed)

JDBC Connections Average Wait Time (3993) (Range: 0.0...) (None)

JDBC Connections Wait Count (3994) (Range: 0.0...) (Computed)

HTTP Sessions Active Count (3995) (Range: 0.0...) (Baselined) (Correlated) (Computed)

HTTP Sessions Maximum Allowed (3996) (Range: 0.0...) (Computed)

HTTP Sessions Utilization Percent (3997) 100 JBoss (Range: 0.0..1.0) (Computed)

Application Server Workload (3998) (Range: 0.0..1.0) (KPI) (AGI) (Baselined) (Correlated) (Com-
puted)

JDBC Connections Available (3999) (Range: 0.0...) (Computed)

Work Manager All Current Thread Count (4000) (Range: 0.0...) (None)

Work Manager All Maximum Pool Size (4001) (Range: 0.0...) (None)

JDBC Pool Connections Active (4088) (Range: 0...) (None)

JDBC Pool Connections Allocated (4089) (Range: 0...) (Computed)

JDBC Pool Connections Max Pool Size (4090) (Range: 0...) (None)

JDBC Pool Connections Wait Count (4091) (Range: 0...) (None)

HTTP Session Pool Active Count (4095) (None)

Thread Pool Active (4096) (None)

CA Application Performance ManagementiGuide


22
Confidential and Proprietary
Chapter 6: Template Reference

Thread Pool Allocated (4097) (None)

Thread Pool Maximum Pool Size (4098) (None)

HTTP Session Pool Maximum Allowed (4099) (None)

JDBC Pool Connections Available (4100) (None)

Threads Idle (4110) (Computed)

JDBC Connections Active (4111) Number of connections from this JDBC pool that are active.
(Range: 0.0...) (Computed)

MEM
Memory Index (1730) Index computation. (Range: 0.0..1) (Computed)

Memory Bytes In Use (2711) Allocated garbage collection heap memory bytes that are in use.
(Range: 0...) (KPI) (AGI) (Baselined)

Memory Bytes Total (2712) Allocated total garbage collection heap memory in bytes. (Range: 0...)
(None)

Memory GC Time Percent (3986) (Range: 0.0..1.0) (Computed)

Memory Utilization Percent (4016) Application server memory utilization percent. (Range:
0.0..1.0) (Computed)

Memory GC Utilization Percent (4019) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)

Memory GC Percentage Of Time Spent In GC (4102) (Range: 0.0...) (KPI) (AGI) (Baselined)
(Correlated)

Tomcat
This template contains metrics for monitoring a Tomcat application server.

APP
Average Servlet Response Time (1517) Average time it takes for this servlet to respond. (Range:
0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

EJB Average Response Time (1521) Average response time across all methods for this EJB.
(Range: 0.0...) (Baselined) (Correlated) (Manual)

EJB Request Rate (1988) (Range: 0.0...) (Baselined) (Correlated) (Manual)

JSP Response Time (ms) (2713) Average response time in milliseconds for JSP to respond to a
web client request. (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

JSP Responses (2714) Average number of JSP responses per time interval. (Range: 0.0...) (KPI)
(AGI) (Baselined) (Correlated) (Manual)

CA Application Performance ManagementiGuide


23
Confidential and Proprietary
Chapter 6: Template Reference

Servlet Responses (2715) Average number of servlet responses per time interval. (Range: 0...)
(KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Response Time (ms) (2718) Average response time in milliseconds for a backend to
respond to a request. A backend is an external system that an application relies on for some portion
of its processing, normally a database. (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)
(Manual)

Backend Responses (2719) Average number of backend responses per time interval. A backend
is an external system that an application relies on for some portion of its processing, normally a
database. (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Stall Count (2728) Number of backend methods started but whose invocation times
have exceeded a threshold. (Range: 0...) (KPI) (AGI) (Baselined) (Manual)

EJB Stall Count (2732) Number of EJB methods started but whose invocation times have
exceeded a threshold. (Range: 0...) (Baselined) (Manual)

Backend Concurrent Invocations (4002) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)
(Manual)

Backend Errors Per Interval (4003) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

EJB Concurrent Invocations (4004) (Range: 0.0...) (Baselined) (Correlated) (Manual)

EJB Errors Per Interval (4005) (Baselined) (Correlated) (Manual)

JDBC Pool Connections Idle (4101) (None)

EJB Responses Per Interval (4103) (Baselined) (Correlated) (Manual)

JSP Responses Per Interval (4104) (KPI) (AGI) (Baselined) (Correlated) (Manual)

JSP Average Response Time (4105) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Average Response Time (4106) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Responses Per Interval (4107) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Servlet Average Response Time (4108) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Servlet Responses Per Interval (4109) (KPI) (AGI) (Baselined) (Correlated) (Manual)

CPU
CPU Utilization Percent (100) Percentage of the CPU resource available that is consumed.
(Range: 0..100.0) (KPI) (AGI) (Baselined) (Correlated) (Computed)

CPU Index (1729) Index computation. (Range: 0.0..1.0) (Computed)

JVM
Threads Active (3979) 100 WebLogic (Range: 0.0...) (Computed)

CA Application Performance ManagementiGuide


24
Confidential and Proprietary
Chapter 6: Template Reference

Threads Maximum Pool Size (3981) (Range: 0.0...) (Computed)

Threads All Active (3984) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)

Threads Allocated (3987) (Range: 0.0...) (Computed)

Threads Utilization Percent (3988) (Range: 0.0..1.0) (KPI) (AGI) (Baselined) (Correlated) (Com-
puted)

JDBC Connections Allocated (3989) (Range: 0.0...) (Computed)

JDBC Connections Maximum Pool Size (3990) (Range: 0.0...) (Computed)

JDBC Connections Utilization Percent (3991) 100 JBoss/WebLogic 110 Tomcat 120 JBoss/We-
bLogic 130 WebSphere (Range: 0.0..1.0) (KPI) (AGI) (Baselined) (Correlated) (Computed)

JDBC Connections Idle (3992) 100 JBoss/WebLogic (Range: 0.0...) (Computed)

JDBC Connections Average Wait Time (3993) (Range: 0.0...) (None)

JDBC Connections Wait Count (3994) (Range: 0.0...) (Computed)

HTTP Sessions Active Count (3995) (Range: 0.0...) (Baselined) (Correlated) (Computed)

HTTP Sessions Maximum Allowed (3996) (Range: 0.0...) (Computed)

HTTP Sessions Utilization Percent (3997) 100 JBoss (Range: 0.0..1.0) (Computed)

Application Server Workload (3998) (Range: 0.0..1.0) (KPI) (AGI) (Baselined) (Correlated) (Com-
puted)

JDBC Connections Available (3999) (Range: 0.0...) (Computed)

JDBC Pool Connections Active (4088) (Range: 0...) (None)

JDBC Pool Connections Max Pool Size (4090) (Range: 0...) (None)

JDBC Pool Connections Wait Count (4091) (Range: 0...) (None)

HTTP Session Pool Active Count (4095) (None)

Thread Pool Active (4096) (None)

Thread Pool Allocated (4097) (None)

Thread Pool Maximum Pool Size (4098) (None)

HTTP Session Pool Maximum Allowed (4099) (None)

JDBC Pool Connections Available (4100) (None)

Threads Idle (4110) (Computed)

CA Application Performance ManagementiGuide


25
Confidential and Proprietary
Chapter 6: Template Reference

JDBC Connections Active (4111) Number of connections from this JDBC pool that are active.
(Range: 0.0...) (Computed)

MEM
Memory Index (1730) Index computation. (Range: 0.0..1) (Computed)

Memory Bytes In Use (2711) Allocated garbage collection heap memory bytes that are in use.
(Range: 0...) (KPI) (AGI) (Baselined)

Memory Bytes Total (2712) Allocated total garbage collection heap memory in bytes. (Range: 0...)
(None)

Memory GC Time Percent (3986) (Range: 0.0..1.0) (Computed)

Memory Utilization Percent (4016) Application server memory utilization percent. (Range:
0.0..1.0) (Computed)

Memory GC Utilization Percent (4019) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)

Memory GC Percentage Of Time Spent In GC (4102) (Range: 0.0...) (KPI) (AGI) (Baselined)
(Correlated)

Web Application
This template contains metrics for web applications that run on JBoss, Tomcat, WebLogic, and
WebSphere application servers. The metrics are obtained from the Frontends branches of the Intro-
scope agents which correspond to instances of these application servers.

APP
Average Response Time (1459) Average response time in seconds. (Range: 0.0...) (KPI) (AGI)
(Baselined) (Correlated)

Aggregated Transaction Count (2521) (Range: 0.0...) (Computed)

URL Group Web Service Average Response Time (ms) (3907) (Range: 0.0...) (KPI) (AGI)
(Baselined) (Correlated)

URL Group Web Service Errors Per Interval (3909) (Range: 0.0...) (Baselined)

URL Group Web Service Responses Per Interval (3910) (Range: 0.0...) (KPI) (AGI) (Baselined)
(Correlated)

URL Group Web Service Stall Count (3911) (Range: 0.0...) (Baselined)

Responses Per Interval (4024) (KPI) (AGI) (Baselined) (Correlated) (Computed)

Concurrent Invocations (4025) (AGI) (Baselined) (Correlated)

Errors Per Interval (4026) (AGI) (Baselined) (Correlated)

Total Response Time (4027) (Range: 0.0...) (KPI) (AGI) (Baselined) (Computed)

CA Application Performance ManagementiGuide


26
Confidential and Proprietary
Chapter 6: Template Reference

Web Application Workload (4028) (Range: 0.0..1.0) (KPI) (AGI) (Baselined) (Correlated) (Com-
puted)

URL Group Average Response Time (ms) (4063) Average Response Time in ms (Range: 0...)
(KPI) (AGI) (Baselined) (Correlated)

URL Group Responses Per Interval (4066) (KPI) (AGI) (Baselined) (Correlated)

URL Group Errors Per Interval (4067) (AGI) (Baselined) (Correlated)

URL Group Concurrent Invocations (4068) (AGI) (Baselined) (Correlated)

URL Group Stall Count (4069) (AGI) (Baselined)

URL Group Database Average Response Time (ms) (4070) (KPI) (AGI) (Baselined) (Cor-
related)

URL Group Database Responses Per Interval (4071) (KPI) (AGI) (Baselined) (Correlated)

URL Group Database Errors Per Interval (4072) (Baselined)

URL Group Database Stall Count (4073) (Baselined)

All URL Groups Web Service Responses Per Interval (4074) (KPI) (AGI) (Baselined) (Cor-
related) (Computed)

All URL Groups Web Service Errors Per Interval (4075) (AGI) (Baselined) (Correlated) (Com-
puted)

All URL Groups Web Service Average Response Time (ms) (4076) (KPI) (AGI) (Baselined)
(Correlated) (Computed)

All URL Groups Web Service Stall Count (4077) (AGI) (Baselined) (Computed)

All URL Groups Database Average Response Time (ms) (4078) (KPI) (AGI) (Baselined) (Cor-
related) (Computed)

All URL Groups Database Responses Per Interval (4079) (KPI) (AGI) (Baselined) (Correlated)
(Computed)

All URL Groups Database Errors Per Interval (4080) (AGI) (Baselined) (Correlated) (Computed)

All URL Groups Database Stall Count (4081) (AGI) (Baselined) (Computed)

Stall Count (4112) (Range: 0.0...) (AGI) (Baselined)

WebLogic
This template contains Introscope metrics from WebLogic application servers.

CA Application Performance ManagementiGuide


27
Confidential and Proprietary
Chapter 6: Template Reference

APP
Average Servlet Response Time (1517) Average time it takes for this servlet to respond. (Range:
0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

EJB Average Response Time (1521) Average response time across all methods for this EJB.
(Range: 0.0...) (Baselined) (Correlated) (Manual)

EJB Request Rate (1988) (Range: 0.0...) (Baselined) (Correlated) (Manual)

JSP Response Time (ms) (2713) Average response time in milliseconds for JSP to respond to a
web client request. (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

JSP Responses (2714) Average number of JSP responses per time interval. (Range: 0.0...) (KPI)
(AGI) (Baselined) (Correlated) (Manual)

Servlet Responses (2715) Average number of servlet responses per time interval. (Range: 0...)
(KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Response Time (ms) (2718) Average response time in milliseconds for a backend to
respond to a request. A backend is an external system that an application relies on for some portion
of its processing, normally a database. (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)
(Manual)

Backend Responses (2719) Average number of backend responses per time interval. A backend
is an external system that an application relies on for some portion of its processing, normally a
database. (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Stall Count (2728) Number of backend methods started but whose invocation times
have exceeded a threshold. (Range: 0...) (KPI) (AGI) (Baselined) (Manual)

EJB Stall Count (2732) Number of EJB methods started but whose invocation times have
exceeded a threshold. (Range: 0...) (Baselined) (Manual)

Backend Concurrent Invocations (4002) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)
(Manual)

Backend Errors Per Interval (4003) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

EJB Concurrent Invocations (4004) (Range: 0.0...) (Baselined) (Correlated) (Manual)

EJB Errors Per Interval (4005) (Baselined) (Correlated) (Manual)

Threads Throughput (4007) (None)

Execute Queue Idle Thread Count (4008) (KPI) (AGI) (Baselined) (Correlated)

Execute Queue Total Thread Count (4009) (None)

Execute Queue Pending Request Count (4010) (KPI) (AGI) (Baselined) (Correlated)

CA Application Performance ManagementiGuide


28
Confidential and Proprietary
Chapter 6: Template Reference

Work Manager All Pending Requests (4011) (Range: 0...) (KPI) (AGI) (Baselined) (Correlated)
(Computed)

Work Manager All Stuck Thread Count (4012) (Range: 0...) (KPI) (AGI) (Baselined) (Correlated)
(Computed)

Sockets Current Count (4013) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)

JDBC Connections Leaked Count (4014) (Computed)

JDBC Pool Connections Leaked Count (4092) (Range: 0...) (AGI) (Baselined)

Work Manager Pool Pending Requests (4093) (Range: 0...) (None)

Work Manager Pool Stuck Thread Count (4094) (Range: 0...) (None)

EJB Responses Per Interval (4103) (Baselined) (Correlated) (Manual)

JSP Responses Per Interval (4104) (KPI) (AGI) (Baselined) (Correlated) (Manual)

JSP Average Response Time (4105) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Average Response Time (4106) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Responses Per Interval (4107) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Servlet Average Response Time (4108) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Servlet Responses Per Interval (4109) (KPI) (AGI) (Baselined) (Correlated) (Manual)

CPU
CPU Utilization Percent (100) Percentage of the CPU resource available that is consumed.
(Range: 0..100.0) (KPI) (AGI) (Baselined) (Correlated) (Computed)

CPU Index (1729) Index computation. (Range: 0.0..1.0) (Computed)

JVM
Threads Active (3979) 100 WebLogic (Range: 0.0...) (Computed)

Threads Maximum Pool Size (3981) (Range: 0.0...) (Computed)

Threads All Active (3984) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)

Threads Allocated (3987) (Range: 0.0...) (Computed)

Threads Utilization Percent (3988) (Range: 0.0..1.0) (KPI) (AGI) (Baselined) (Correlated) (Com-
puted)

JDBC Connections Allocated (3989) (Range: 0.0...) (Computed)

JDBC Connections Maximum Pool Size (3990) (Range: 0.0...) (Computed)

CA Application Performance ManagementiGuide


29
Confidential and Proprietary
Chapter 6: Template Reference

JDBC Connections Utilization Percent (3991) 100 JBoss/WebLogic 110 Tomcat 120 JBoss/We-
bLogic 130 WebSphere (Range: 0.0..1.0) (KPI) (AGI) (Baselined) (Correlated) (Computed)

JDBC Connections Idle (3992) 100 JBoss/WebLogic (Range: 0.0...) (Computed)

JDBC Connections Average Wait Time (3993) (Range: 0.0...) (None)

JDBC Connections Wait Count (3994) (Range: 0.0...) (Computed)

HTTP Sessions Active Count (3995) (Range: 0.0...) (Baselined) (Correlated) (Computed)

HTTP Sessions Maximum Allowed (3996) (Range: 0.0...) (Computed)

Application Server Workload (3998) (Range: 0.0..1.0) (KPI) (AGI) (Baselined) (Correlated) (Com-
puted)

JDBC Connections Available (3999) (Range: 0.0...) (Computed)

JDBC Pool Connections Active (4088) (Range: 0...) (None)

JDBC Pool Connections Allocated (4089) (Range: 0...) (Computed)

JDBC Pool Connections Max Pool Size (4090) (Range: 0...) (None)

JDBC Pool Connections Wait Count (4091) (Range: 0...) (None)

HTTP Session Pool Active Count (4095) (None)

Thread Pool Active (4096) (None)

Thread Pool Allocated (4097) (None)

Thread Pool Maximum Pool Size (4098) (None)

HTTP Session Pool Maximum Allowed (4099) (None)

JDBC Pool Connections Available (4100) (None)

Threads Idle (4110) (Computed)

JDBC Connections Active (4111) Number of connections from this JDBC pool that are active.
(Range: 0.0...) (Computed)

MEM
Memory Index (1730) Index computation. (Range: 0.0..1) (Computed)

Memory Bytes In Use (2711) Allocated garbage collection heap memory bytes that are in use.
(Range: 0...) (KPI) (AGI) (Baselined)

Memory Bytes Total (2712) Allocated total garbage collection heap memory in bytes. (Range: 0...)
(None)

Memory GC Time Percent (3986) (Range: 0.0..1.0) (Computed)

CA Application Performance ManagementiGuide


30
Confidential and Proprietary
Chapter 6: Template Reference

Memory Utilization Percent (4016) Application server memory utilization percent. (Range:
0.0..1.0) (Computed)

Memory GC Utilization Percent (4019) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)

Memory GC Percentage Of Time Spent In GC (4102) (Range: 0.0...) (KPI) (AGI) (Baselined)
(Correlated)

WebSphere
This template contains Introscope metrics from WebSphere application servers.

APP
Average Servlet Response Time (1517) Average time it takes for this servlet to respond. (Range:
0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

EJB Average Response Time (1521) Average response time across all methods for this EJB.
(Range: 0.0...) (Baselined) (Correlated) (Manual)

EJB Request Rate (1988) (Range: 0.0...) (Baselined) (Correlated) (Manual)

JSP Response Time (ms) (2713) Average response time in milliseconds for JSP to respond to a
web client request. (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

JSP Responses (2714) Average number of JSP responses per time interval. (Range: 0.0...) (KPI)
(AGI) (Baselined) (Correlated) (Manual)

Servlet Responses (2715) Average number of servlet responses per time interval. (Range: 0...)
(KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Response Time (ms) (2718) Average response time in milliseconds for a backend to
respond to a request. A backend is an external system that an application relies on for some portion
of its processing, normally a database. (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)
(Manual)

Backend Responses (2719) Average number of backend responses per time interval. A backend
is an external system that an application relies on for some portion of its processing, normally a
database. (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Stall Count (2728) Number of backend methods started but whose invocation times
have exceeded a threshold. (Range: 0...) (KPI) (AGI) (Baselined) (Manual)

EJB Stall Count (2732) Number of EJB methods started but whose invocation times have
exceeded a threshold. (Range: 0...) (Baselined) (Manual)

Backend Concurrent Invocations (4002) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)
(Manual)

Backend Errors Per Interval (4003) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated) (Manual)

EJB Concurrent Invocations (4004) (Range: 0.0...) (Baselined) (Correlated) (Manual)

CA Application Performance ManagementiGuide


31
Confidential and Proprietary
Chapter 6: Template Reference

EJB Errors Per Interval (4005) (Baselined) (Correlated) (Manual)

Threads Maxed Percent (4017) (Range: 0.0...) (None)

EJB Responses Per Interval (4103) (Baselined) (Correlated) (Manual)

JSP Responses Per Interval (4104) (KPI) (AGI) (Baselined) (Correlated) (Manual)

JSP Average Response Time (4105) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Average Response Time (4106) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Backend Responses Per Interval (4107) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Servlet Average Response Time (4108) (KPI) (AGI) (Baselined) (Correlated) (Manual)

Servlet Responses Per Interval (4109) (KPI) (AGI) (Baselined) (Correlated) (Manual)

JDBC Connections Utilization (4114) (KPI) (AGI) (Baselined) (Correlated)

CPU
CPU Utilization Percent (100) Percentage of the CPU resource available that is consumed.
(Range: 0..100.0) (KPI) (AGI) (Baselined) (Correlated) (Computed)

CPU Index (1729) Index computation. (Range: 0.0..1.0) (Computed)

JVM
Threads Active (3979) 100 WebLogic (Range: 0.0...) (Computed)

Threads Maximum Pool Size (3981) (Range: 0.0...) (Computed)

Threads All Active (3984) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)

Threads Allocated (3987) (Range: 0.0...) (Computed)

Threads Utilization Percent (3988) (Range: 0.0..1.0) (KPI) (AGI) (Baselined) (Correlated) (Com-
puted)

JDBC Connections Allocated (3989) (Range: 0.0...) (Computed)

JDBC Connections Maximum Pool Size (3990) (Range: 0.0...) (Computed)

JDBC Connections Utilization Percent (3991) 100 JBoss/WebLogic 110 Tomcat 120 JBoss/We-
bLogic 130 WebSphere (Range: 0.0..1.0) (Computed)

JDBC Connections Idle (3992) 100 JBoss/WebLogic (Range: 0.0...) (Computed)

JDBC Connections Average Wait Time (3993) (Range: 0.0...) (None)

JDBC Connections Wait Count (3994) (Range: 0.0...) (Computed)

HTTP Sessions Active Count (3995) (Range: 0.0...) (Baselined) (Correlated) (Computed)

CA Application Performance ManagementiGuide


32
Confidential and Proprietary
Chapter 6: Template Reference

HTTP Sessions Maximum Allowed (3996) (Range: 0.0...) (Computed)

Application Server Workload (3998) (Range: 0.0..1.0) (KPI) (AGI) (Baselined) (Correlated) (Com-
puted)

JDBC Connections Available (3999) (Range: 0.0...) (Computed)

JDBC Pool Connections Max Pool Size (4090) (Range: 0...) (None)

JDBC Pool Connections Wait Count (4091) (Range: 0...) (None)

HTTP Session Pool Active Count (4095) (None)

Thread Pool Active (4096) (None)

Thread Pool Allocated (4097) (None)

Thread Pool Maximum Pool Size (4098) (None)

HTTP Session Pool Maximum Allowed (4099) (None)

JDBC Pool Connections Available (4100) (None)

Threads Idle (4110) (Computed)

JDBC Connections Active (4111) Number of connections from this JDBC pool that are active.
(Range: 0.0...) (Computed)

MEM
Memory Index (1730) Index computation. (Range: 0.0..1) (Computed)

Memory Bytes In Use (2711) Allocated garbage collection heap memory bytes that are in use.
(Range: 0...) (KPI) (AGI) (Baselined)

Memory Bytes Total (2712) Allocated total garbage collection heap memory in bytes. (Range: 0...)
(None)

Memory GC Time Percent (3986) (Range: 0.0..1.0) (Computed)

Memory Utilization Percent (4016) Application server memory utilization percent. (Range:
0.0..1.0) (Computed)

Memory GC Utilization Percent (4019) (Range: 0.0...) (KPI) (AGI) (Baselined) (Correlated)

Memory GC Percentage Of Time Spent In GC (4102) (Range: 0.0...) (KPI) (AGI) (Baselined)
(Correlated)

CA Application Performance ManagementiGuide


33
Confidential and Proprietary
Appendix A: Archived release notes

Appendix A: Archived release notes


This section includes information included in the "Release notes" section of past versions of the
CA Application Performance Management Guide.

What's new 34

What's fixed 35

What's new
The following is a list of new features from previous versions of this integration. The list is grouped
by version.

Version 3.1.0
The following is a list of new features introduced in the CA APM integration version 3.1.0.
Support for Netuitive 6.0
This version of the CA APM integration supports Netuitive 6.0. For a list of system requirements for
the CA APM integration, please see "System requirements" on page 5.
New Managed Elements
The following new Managed Elements have been added to the CA APM integration:

l Application Server Managed Element


l Web Application Managed Element
l Transaction Set Managed Element (CEM)
l Aggregated Transaction Managed Element(CEM)

In addition, a dependent URL Group Managed Element was added. Independent JVM and Depend-
ent JVM Managed Elements have been superseded by the Application Server Managed Element.
See "CA APM Managed Elements" on page 16 for additional information about the new Managed
Elements.
New templates
This version of the integration has two new templates: Customer Experience Manager (CEM) and
Web Application. In addition, the templates for the JBoss, Tomcat, and WebLogic Application Serv-
ers have been revised extensively. See "Chapter 6: Template Reference" on page 18 for more
information.
Now supports aggregated collection methods
Remote Collector now supports custom aggregated collection methods used to associate different
types of calculations for collected metric values. These aggregation methods are configurable for
this integration. There are five supported aggregated collection methods:

CA Application Performance ManagementiGuide


34
Confidential and Proprietary
Appendix A: Archived release notes

l Minimum: The minimum value of the collected metric values


l Maximum: The maximum value of the collected metric values
l Sum: The total value for the collected metric values
l Mean: The average value across the collected metric values
l Weighted mean: The weighted average across the collected metric values

Contact Netuitive Professional Services for assistance configuring aggregated collection methods.
Advanced Process Mappings
This version of the CA APM integration adds the ability to select the specific fields of the raw data
that should be used to enable or disable process mappings. The same filter will be applied to each
field configured in order. To enable this setting, modify the <columns> field in the config.xml file
in the <Remote Collector install home>/plugins/wily/conf directory.
Migration from CA APM 2.x to CA APM 3.1.0
There is no direct upgrade path from CA APM 2.x to CA APM 3.1.0; however, you can migrate
between versions by installing the new version alongside the existing CA APM 2.x integration. This
way, the existing CA APM 2.x Managed Elements and metrics are not lost when migrating to the
newer version. After confirming that CA APM 3.1.2 Managed Elements and metrics meet expect-
ations, you can remove the CA APM 2.x data source. For installation and configuration instruc-
tions, see "Chapter 3: Integration installation" on page 5 and "Chapter 5: CA APM Configuration in
Netuitive" on page 9.

Version 2.0
The following is a new feature introduced in the CA APM integration version 2.0.
Integration Name Changed to CA Application Performance Management
The integration formerly known as CA Wily Introscope is now known as CA Application Per-
formance Management (CA APM).

What's fixed
The following is a list of resolved issues from previous versions of this integration. The list is
grouped by version.

Version 3.1.1
The following fixes were made to improve the integration:

l Template changes have been applied to the JBoss, Tomcat, WebLogic, and WebSphere application
server templates in the following manner:
l The JVM resource type has been added and multiple metrics have been moved to this resource
type from other resource types. See "Chapter 6: Template Reference" on page 18 for a list of the
metrics appearing under the JVM resource type.
l Multiple metrics on each template have had adjustments made to KPI, AGI, Baselined, and Cor-
related properties.

CA Application Performance ManagementiGuide


35
Confidential and Proprietary
Appendix A: Archived release notes

l Memory GC Utilization Percent (4019) and Memory GC Percentage Of Time Spent In GC (4102)
have been moved from the APP resource to the MEM resource.
l The WebApplication template has had adjustments made to KPI, AGI, Baselined, and Correlated
properties for multiple metrics.

Version 3.1.0
The following fixes were made to improve the integration:

l Minor logging improvements.


l Fixed an error that prevented CA APM 3.x plug-ins to run in the same Remote Collector as CA APM
2.x plug-ins.
l Corrected an issue where Web Application workload could display invalid values.

Version 2.0
The following fix was made to improve the integration:

l Batch Processing of Metrics. Version 2.0 of this plug-in was not properly processing metrics in large
batches. This has now been resolved.

CA Application Performance ManagementiGuide


36
Confidential and Proprietary