APM - 9.5 - APM For Oracle WebLogic Server Guide

for Oracle WebLogic Server Guide
Release 9.5
CA Application Performance
Management

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, without
the 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 to
their respective companies.

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 ([assign the value for wed
in your book])
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 Server
Agents (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 for
IBM 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)
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)

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. At http://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 to [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.

Contents 7

Contents

Chapter 1: Introduction 9
Introduction ................................................................................................................................................................. 9
Using This Guide ........................................................................................................................................................... 9
Chapter 2: Installing and Configuring the Extension 11
Before You Begin ........................................................................................................................................................ 11
How to Install CA APM for Oracle WebLogic Server .................................................................................................. 12
Run the Installer .................................................................................................................................................. 12
Run the Agent Installer ....................................................................................................................................... 13
Set Up the Management Module ....................................................................................................................... 14
Set Up the Workstation Extension ...................................................................................................................... 14
Enable JMX Metric Collection ............................................................................................................................. 14
Configure a Startup Class in WebLogic Server .................................................................................................... 15
Exclude Increment Counters From Metric Aging ................................................................................................ 15
Optional: Integrate CA APM ChangeDetector ..................................................................................................... 17
Remove the Extension................................................................................................................................................ 19
Chapter 3: Using the Extension 21
View WebLogic Server Metrics in the Workstation ................................................................................................... 21
View Special Elements ................................................................................................................................................ 22
View WebLogic Server Dashboards ............................................................................................................................ 22
WebLogic Application Server - Overview ............................................................................................................ 23
WebLogic - JDBC Connection Pools ..................................................................................................................... 23
WebLogic - HTTP Sessions ................................................................................................................................... 24
WebLogic - EJB Subsystem .................................................................................................................................. 24
WebLogic - JMS Subsystem ................................................................................................................................. 24
WebLogic - JTA Subsystem .................................................................................................................................. 25
WebLogic - Security ............................................................................................................................................. 25
Appendix A: WebLogic Server Metrics 27
EJB Subsystem ............................................................................................................................................................ 27
Stateful Metrics ................................................................................................................................................... 28
NRU Cache Metrics ............................................................................................................................................. 28
LRU Cache Metrics .............................................................................................................................................. 28
Stateless Metrics ................................................................................................................................................. 29

8 for Oracle WebLogic Server Guide

Entity Cache Metrics ........................................................................................................................................... 29
Message-Driven Metrics ..................................................................................................................................... 30
Entity Metrics ...................................................................................................................................................... 30
Servlet Subsystem Metrics ......................................................................................................................................... 30
HTTP Sessions ............................................................................................................................................................. 30
JMS Subsystem ........................................................................................................................................................... 32
Distributed Destination Metrics ................................................................................................................................. 32
Security Subsystem .................................................................................................................................................... 33
Clustering ................................................................................................................................................................... 33
XML Subsystem .......................................................................................................................................................... 34
JMX Metrics ................................................................................................................................................................ 35
JMX Aggregate Metrics .............................................................................................................................................. 39

Chapter 1: Introduction 9

Chapter 1: Introduction

This section contains the following topics:
Introduction (see page 9)
Using This Guide (see page 9)
Introduction
CA APM for Oracle WebLogic Server is a CA APM extension, developed in cooperation
with Oracle Corporation. The extension provides advanced performance management
for production WebLogic Server environments.
Note: In this guide, CA APM for Oracle WebLogic Server is sometimes referred to as "the
extension." The product was formerly known as a "PowerPack."
CA APM for Oracle WebLogic Server monitors critical WebLogic resources and helps to
isolate application bottlenecks and improve the availability of WebLogic Server and
applications.
Using This Guide
This guide provides instructions for setting up and using CA APM for Oracle WebLogic
Server.
Note: For system requirements, see the Compatibility Guide.
At a high level, this guide provides the following information:
Installing and configuring CA APM for Oracle WebLogic Server (see page 11).
Using CA APM for Oracle WebLogic Server (see page 21).
WebLogic server metrics (see page 27).


Chapter 2: Installing and Configuring the
Extension

This chapter describes how to install and configure the CA APM for Oracle WebLogic
Server in a CA APM deployment.
Before You Begin (see page 11)
How to Install CA APM for Oracle WebLogic Server (see page 12)
Remove the Extension (see page 19)
Before You Begin
Before you install CA APM for Oracle WebLogic Server, you do preliminary steps.
Follow these steps:
1. Verify that you have a supported version of the WebLogic Server installed in your
environment.
Note: For a complete list of supported versions, see the CA APM Compatibility
Guide. The CA APM Compatibility Guide lists software and hardware compatibilities
for CA APM components. This guide is available from CA Support.
2. Identify the following directory locations in your CA Introscope environment:
The application server home directoryThe home directory of your
application server, from now on referred to as <AppServer_Home>.
The APM home directoryThe installation directory for APM on your
Enterprise Manager server, from now on referred to as <APM_Home>.
The APM agent directoryThe installation directory for the APM agent on
your application server, from now on referred to as <Agent_Home>.
3. Verify that you have a supported version of the Java Virtual Machine (JVM) installed
in your WebLogic Server environment.
Note: To reduce CPU use, set the cacheconnection property as follows:
introscope.agent.sqlagent.cacheConnectionsURLs=true
4. Shut down the application server instance where you are going to install CA APM
for Oracle WebLogic Server.
Important! The installation instructions assume that you are using JVM AutoProbe to
instrument your applications. For information about using JVM AutoProbe, see the CA
APM Java Agent Implementation Guide or CA APM .NET Agent Implementation Guide.
How to Install CA APM for Oracle WebLogic Server


Installing and configuring CA APM for Oracle WebLogic Server involves the following
steps:
1. Run the installer (see page 12).
2. Run the agent installer (see page 13).
3. Set up the Management Module (see page 14).
4. Set up the Workstation Extension (see page 14).
5. Enable JMX Metric collection (see page 14).
6. Configure a startup class in WebLogic Server (see page 15).
7. Exclude incremental counters from metric aging (see page 15).
8. (Optional) Integrate ChangeDetector (see page 17).
Run the Installer
Run the CA APM installer.
The CA APM installer places the files into the
<APM_Home>\examples\<Extension_Home> directory. You copy the files to the correct
location, based on how they are organized in the \examples directory.
For details about running the CA APM installer, see the CA APM Installation and
Upgrade Guide.
Note: The following list uses the Microsoft Windows directory syntax. For other
installation platforms, such as UNIX, replace "\" with "/".
The installer places the following files in the
<APM_Home>\examples\<Extension_Home>\ directory:
.\config\modules\PPWebLogicManagementModule.jar
Management Module with preconfigured dashboards and alerts for viewing
WebLogic-specific metrics.
.\ext\PPWebLogicExtensionPlugins.jar
Enterprise Manager Extension to enable the JMX Aggregate metrics.
.\ext\ddtv\PPWebLogicTypeview.xml
Workstation extension to enable the AppServer View in the Investigator.


Run the Agent Installer
To install and initially configure agent information for the extension, run the agent
installer.
For details, see the CA APM Java Agent Implementation Guide or CA APM .NET Agent
Implementation Guide.
Note: The following list uses the Microsoft Windows directory syntax. For other
installation platforms, such as UNIX, replace "\" with "/".
The agent installer places the following files onto the application server computer in the
<Agent_Home>\wily directory:
ppweblogic.pbd
ProbeBuilder Directives file that contains the tracers that are required to
instrument your application for WebLogic Server. This file is located in the
<Agent_Home>/wily/core/config directory.
PPWebLogicJMXFilterString.txt
Text file with the JMX filter string. This file is located in the
<Agent_Home>/common directory.
ChangeDetector-config-WebLogic.xml
ChangeDetector configuration file. This file is located in the
<Agent_Home>/common directory.
The installer configures the agent and extension agent files with the Enterprise Manager
host and port information.
If you enable the extension during agent installation:
The installer installs the ppweblogic.pbd file in the <Agent_Home>/wily/core/config
or
JVM/wily directory, depending on whether the Java application is instrumented
using the AutoProbe-enabled Web Application Server or JVM.
The installer modifies the introscope.autoprobe.directivesFile property in the
IntroscopeAgent.profile file (located in the <Agent_Home>/wily/core/config
directory on your WebLogic Server host) to add the new directives file
ppweblogic.pbd to the list. For example:
introscope.autoprobe.directivesFile=weblogic-full.pbl,ppweblogic.pbd


Set Up the Management Module
You set up the management module to display the CA APM for Oracle WebLogic Server
dashboard.
Follow these steps:
1. Copy the management module file PPWebLogicManagementModule.jar to the
<APM_Home>/config/modules directory.
2. Restart the Enterprise Manager.
CA APM can display the CA APM for Oracle WebLogic Server dashboard.
Set Up the Workstation Extension
Set up the Workstation extension to view CA APM for Oracle WebLogic Server data in
the Workstation.
Follow these steps:
1. Copy PPWebLogicTypeview.xml to the <APM_Home>/ext/ddtv directory.
2. Copy PPWebLogicExtensionPlugins.jar to the <APM_Home>/ext directory.
3. Restart the Enterprise Manager.
Enable JMX Metric Collection
You can configure the extension to enable JMX metric collection.
Follow these steps:
1. Open the IntroscopeAgent.profile file and look under the JMX Configuration
heading for these properties:
a. introscope.agent.jmx.enable -- Uncomment this property and set its value to
true.
b. introscope.agent.jmx.name.primarykeys -- Comment out this property.
c. introscope.agent.jmx.name.filter -- Uncomment this property.
2. To collect more metrics than specified in the default value, append the string
specified in the PPWebLogicJMXFilterString.txt file. This file is located in the
<Agent_Home>\wily\common to the introscope.agent.jmx.name.filter property.
Note: The recommended filter string values select key JMX metrics for WebLogic
Server. To collect other JMX metrics, append them to the recommended filter value
in comma-separated form.
Important! The string is case-sensitive.


3. Save the IntroscopeAgent.profile file and restart your application.
Note: The JMX metrics match the metrics in the WLDF Console Extension of the
WebLogic Server Administration Console.
Configure a Startup Class in WebLogic Server
To obtain JMX data, you must have a startup class for CA Introscope configured in
WebLogic Server. If you have previously configured an APM startup class in WebLogic
Server, you can skip this step.
Follow these steps:
1. Click the Lock & Edit button on the WebLogic Administration Console.
2. Expand the Environment node under the server you are configuring and click the
Startup & Shutdown link.
A table with the existing Startup and Shutdown Classes is displayed.
3. Click the New button in the table.
The Configure a New Startup or Shutdown Class dialog appears.
4. Click the Startup Class option under Class Type and click Next.
5. In the Name field, type:
Introscope Startup Class
6. In the ClassName field, type:
com.wily.introscope.api.weblogic.IntroscopeStartupClass
7. Click Next.
8. Under Select Targets:
Select the boxes for the servers that you want to use the startup class for.
Select the boxes for any clusters, if your application server instances are
clustered.
9. Click Finish.
10. Click Activate Changes and restart the application server.
The startup class is configured and implemented in WebAppSupport.jar.
Important! Ensure that you add the location of the WebAppSupport.jar to the
application startup classpath.
Exclude Increment Counters From Metric Aging
Metrics occasionally appear gray or dimmed when the agent disconnects. Metrics for
increment and decrement counters should not be considered for metric aging.


Example: Metric Aging
Suppose the initial Session Count is 5. If this metric does not receive data for a specified
time period and is included for metric aging, it is disabled. The counter is reinitialized to
0. After some time, if this metric receives data, the counter starts from 0; this results in
the metric displaying incorrect data.
Therefore, metrics involving increment and decrement counters can give incorrect
information and should not be included for metric aging.
Follow these steps:
1. Navigate to <AgentHome>\wily\core\config and open the IntroscopeAgent.profile
file.
2. Uncomment the introscope.agent.metricAging.metricExclude.ignore property to
exclude metrics that involve increment and decrement counters from metric aging:
introscope.agent.metricAging.metricExclude.ignore.<X+1>=WebLogic|Servlet
Subsystem:Error Response Count
introscope.agent.metricAging.metricExclude.ignore.<X+2>=WebLogic|HTTP
Sessions Subsystem|All Sessions:Session Count
Sessions Subsystem|Cookie Sessions:Session Count
Sessions Subsystem|File Sessions:Session Count
Sessions Subsystem|JDBC Sessions:Session Count
Sessions Subsystem|Memory Sessions:Session Count
Sessions Subsystem|Replicated Sessions:Session Count
introscope.agent.metricAging.metricExclude.ignore.<X+8>=WebLogic|Clustering|C
hange Event:Count
introscope.agent.metricAging.metricExclude.ignore.<X+9>=WebLogic|Clustering|F
ull State Dump:Count
introscope.agent.metricAging.metricExclude.ignore.<X+10>=WebLogic|Clustering|
Announce:Count
Peer Gone Listeners:Count
RJVM Remote Call:Error Count
introscope.agent.metricAging.metricExclude.ignore.<X13>=WebLogic|XML
Subsystem|SAX Parsers:Creation Count
introscope.agent.metricAging.metricExclude.ignore.<X+14>=WebLogic|XML
Subsystem|Document Builder:Creation Count
introscope.agent.metricAging.metricExclude.ignore.<X+15>=WebLogic|XML
Subsystem|SAX Transformer:Creation Count


Note: You can use this list to add metrics to the metric aging exclude list in the
IntroscopeAgent.profile file. When doing so, remove the line breaks. These line
breaks have been included only for legibility.
In this list, X is the existing sequence number for the
introscope.agent.metricAging.metricExclude.ignore property of the
IntroscopeAgent.profile file. For example, If the last sequence in the
IntroscopeAgent.profile file for introscope.agent.metricAging.metricExclude.ignore
property is introscope.agent.metricAging.metricExclude.ignore.15=Thread a, then
X=15.
Optional: Integrate CA APM ChangeDetector
To integrate CA APM ChangeDetector with CA APM for Oracle WebLogic Server,
perform the following steps.
After you install the ChangeDetector configuration file, use CA APM ChangeDetector to
monitor changes that occur in the configured folders for WebLogic Server.
Note: When you start WebLogic Server, all the files that ChangeDetector detects are
marked as the initial version. The initial changes that you see are not the actual changes
but addition of initial versions of all files under the monitored folders. This behavior is as
designed.
Follow these steps:
1. Navigate to the <Agent_Home>/wily/common directory.
2. Copy ChangeDetector-config-WebLogic.xml to <AppServer_Home>/wily or JVM/wily
directory, depending on whether you want metrics on a Java application or on a
JVM.
3. Open the IntroscopeAgent.profile file on the WebLogic Server computer and set the
following property value. Point to the location of the ChangeDetector configuration
file:
introscope.changeDetector.profile=<path to
AppServerHome/wily>\ChangeDetector-config-WebLogic.xml
Java environment example:
introscope.changeDetector.profile=C:\\bea\\wlserver_10.3\\wily\\ChangeDetecto
r-config-WebLogic.xml.
UNIX environment example:
introscope.changeDetector.profile=/usr/bin/bea/wlserver_10.3/wily/ChangeDetec
tor-config-WebLogic.xml


Note: If you have more than one domain and you want to configure
ChangeDetector for both the domains, CA Technologies recommends that you
enable the following property in IntroscopeAgent.profile:
introscope.changeDetector.agentID=<SampleApplicationName>
Failure to enable this property causes a possible conflict with ChangeDetector
Agent ID in Investigator, resulting in errors in the agent log file.
4. Save the IntroscopeAgent.profile file.
5. Configure your environment for ChangeDetector by performing one of the following
steps:
Modify the startup script (see page 18) (recommended).
Modify the agent profile (see page 19).
You have now successfully integrated ChangeDetector.
Modify the Startup Script
Configure your environment for ChangeDetector by modifying the startup script.
Important! To use the same agent profile for more than one agent, modify the startup
scripts instead of the agent profile. Failure to do so causes a possible conflict between
the domains that use the same agent profile.
Follow these steps:
1. Add the following line to the .cmd or .bat file that starts the WebLogic application
that CA APM for Oracle WebLogic Server monitors.
-DDOMAIN_HOME=<filepath1> -DAPPLICATION_HOME=<filepath2>
<filepath1> and <filepath2> are the file paths to the domain or application home,
respectively.
2. Save the .cmd or .bat file.
3. Restart your application.

Note: The DOMAIN_HOME and APPLICATION_HOME properties are preset in the
ChangeDetector configuration file that comes with CA APM for Oracle WebLogic
Server. If you want to use properties other than these preset properties, modify the
ChangeDetector XML configuration file to use the properties that you require. For
more information about using ChangeDetector and the ChangeDetector XML
configuration files, see the CA APM ChangeDetector User Guide.
Remove the Extension


Modify the Agent Profile
Configure your environment for ChangeDetector by modifying the agent profile.
Important! To use the same agent profile for more than one agent, modify the startup
scripts instead of the agent profile. Failure to do so causes a possible conflict between
the domains that use the same agent profile.
Follow these steps:
1. Open the IntroscopeAgent.profile file on the WebLogic Server and append the
following properties at the end of the file:
DOMAIN_HOME=<filepath1>
APPLICATION_HOME=<filepath2>
<filepath1> and <filepath2> are the file paths to the domain or application home,
respectively.
Note: The DOMAIN_HOME and APPLICATION_HOME properties are preset in the
ChangeDetector configuration file that comes with CA APM for Oracle WebLogic
Server. If you want to use properties other than these preset properties, modify the
ChangeDetector XML configuration file to use the properties that you require. For
more information about using ChangeDetector and the ChangeDetector XML
configuration files, see the CA APM ChangeDetector User Guide.
2. Save the IntroscopeAgent.profile file.
3. Restart your application.
To remove the extension, you manually remove the PBD file and files from the
Enterprise Manager and agent.
Follow these steps:
1. Remove these files from <APM_Home>:
.\config\modules\PPWebLogicManagementModule.jar
.\ext\ddtv\PPWebLogicTypeview.xml
.\ext\PPWebLogicExtensionPlugins.jar


2. Remove these files from the application server computer in the wily directory:
PPWebLogicJMXFilterString.txt
ChangeDetector-config-WebLogic.xml
3. Remove ppweblogic.pbd from the introscope.autoprobe.directives files in
IntroscopeAgent.profile.
4. Restart the agent.


Chapter 3: Using the Extension

This chapter describes the dashboards and alerts that are included with the extension.
View WebLogic Server Metrics in the Workstation (see page 21)
View Special Elements (see page 22)
View WebLogic Server Dashboards (see page 22)
View WebLogic Server Metrics in the Workstation
You can view WebLogic Server metrics in the Workstation.
Follow these steps:
1. Start your application.
2. Launch the Enterprise Manager.
3. Launch and log in to the Workstation.
4. Open the Investigator tree to view metrics.
All WebLogic-specific metrics appear under a WebLogic node in the Investigator
tree. Workstation displays metrics according to the WebLogic resources that your
applications use.
5. Select a tab to change how you view the information presented in the Investigator.
The tab views that are available vary depending on the resource or metric currently
selected in the Investigator tree.
Note: For more information about standard tab views, see the CA APM Workstation
User Guide.
More information:
WebLogic Server Metrics (see page 27)

View Special Elements


View Special Elements
The AppServer tab view contains special elements for the extension.
To view these elements, select an agent or the WebLogic node in the Investigator tree.
The AppServer tab view presents the following metrics:
Live HTTP Session Count
Gives information about the performance of cookies, files, memory, and JDBC
sessions. For WebLogic Server, live HTTP session counts are determined from the
following metric:
WebLogic\|HTTP Sessions Subsystem\|All Sessions:Session Count
Thread Pool Waiting Request Count
Gives information about the availability of executable threads. For WebLogic
Server, thread availability is determined from the following metric:
JMX\\|(.*)\\|(Type=Ex|Ex)ecuteQueueRuntime(.*):PendingRequestCurrentCount
JDBC Connection Pool Waiting Thread Count
Gives information about the number of free connections in the pool. For WebLogic
Server, connection availability is determined from the following metric:
JMX\\|(.*)\\|((Type=JDBC|JDBC)DataSourceRuntime|(Type=JDBC|JDBC)ConnectionPoo
lRuntime)(.*):WaitingForConnectionCurrentCount
EJB Pool Waiting Thread Count
Gives information about the number of available EJB instances. For WebLogic
Server, EJB availability is determined from the following metric:
JMX\\|(.*)\\|(Type=EJB|EJB)PoolRuntime(.*):Waiter(Total|Current)Count
View WebLogic Server Dashboards
CA APM for Oracle WebLogic Server provides preconfigured dashboards displaying
WebLogic Server performance metrics. The dashboard names begin with WebLogic to
distinguish them from other installed or standard dashboards.
The alerts displayed in the Workstation dashboards depend on thresholds being defined
for many of the performance metrics. Consult the CA APM Workstation User Guide for
information about customizing these alerts and thresholds to your environment.
Note: Thresholds for alerts in the Investigator tab views cannot be customized.


Follow these steps:
1. Launch the Workstation.
2. Navigate to Workstation > New Console.
The new console window opens.
3. Use the drop-down list at the top of the new console window and navigate to the
desired WebLogic Server dashboard.
Note: For more information about the design, use, and navigation of dashboards,
see the CA APM Workstation User Guide.
WebLogic Application Server - Overview
The WebLogic Application Server - Overview dashboard is a high-level dashboard
showing the overall health of the WebLogic Application Server. The Overview
Dashboard monitors WebLogic resources in four categories: Server Execute Threads
Availability, JDBC Connection Request Wait Count, Live HTTP Session Count, and EJB
Pool Availability. Alert indicators show the status of each resource at a glance.
The Overview dashboard contains operational notes explaining the meaning of alert
indicators, with suggestions for corrective action.
You can use one of the secondary dashboards to drill into a particular subsystem you
want more information about. On the WebLogic Application Server - Overview
dashboard, click any of the alert indicators to view the related dashboard.
WebLogic - JDBC Connection Pools
The WebLogic - JDBC Connection Pools dashboard contains graphs that show the
performance of JDBC connections.
The WebLogic - JDBC Connection Pools dashboard provides the following information,
with operational notes explaining graph activity and suggestions for corrective action:
Connection Request Wait Count
Active Connection Count
Leaked Connection Count
Total Connection Count


WebLogic - HTTP Sessions
The WebLogic - HTTP Sessions dashboard contains graphs that show the HTTP Session
information about cookies, file, memory, and JDBC sessions. This dashboard gives
information about the number of open sessions and the average time to create a
session.
The WebLogic - HTTP Sessions dashboard provides the following information, with
operational notes explaining graph activity and suggestions for corrective action:
Live HTTP, Cookie, Memory Sessions
Live HTTP Session Count
Cookie Session Count
Memory Session Count
File, JDBC, Replicated Sessions:
File Session Count
JDBC Session Count
Replicated Session Count
WebLogic - EJB Subsystem
The WebLogic - EJB Subsystem dashboard contains graphs that show the performance
of the EJB Subsystem.
The WebLogic - EJB Subsystem dashboard provides the following information, with
operational notes explaining graph activity and suggestions for corrective action:
EJB Pools/Caches/Functionalities Average Response Time
Entity Bean Pool
Stateless Bean Pool
Message Driven Bean Pool
Stateful NRU Cache
Stateful LRU Cache
Stateful Bean Read/Save/Replicate Time
WebLogic - JMS Subsystem
The WebLogic - JMS Subsystem dashboard contains graphs that show the performance
of JMS Messaging System.


The WebLogic - JMS Subsystem dashboard provides the following information:
JMS Activities
JMS Send/Receive Message Time
JMS Send/Receive Message Rate/Sec
JMS Read/Write Current Bytes Count
JMS Read/Write Cumulative Bytes Count
JMS Queue, JMS Topic
JMS Queue/Topic Current Consumer Count
JMS Queue/Topic Current Message Count
JMS Queue/Topic Current Bytes Count
JMS Queue/Topic Cumulative Message Count
WebLogic - JTA Subsystem
The WebLogic - JTA Subsystem dashboard contains graphs that show the performance
of transactions in the JTA Java Transaction API (Transaction Manager).
The WebLogic - JTA Subsystem dashboard provides the following information:
Total Transaction Count
Committed Count
Abandoned Count
Transaction RolledBack and Heuristic
RolledBack Total Count
RolledBack Timeout Count
Heuristics Total Count
WebLogic - Security
The WebLogic - Security dashboard contains graphs that show information about
security functions for applications.


The WebLogic - Security dashboard provides the following information:
Average Response Time of User Authentication Functions:
Basic User Form Authentication
Authenticate Users
Run As Users
Average Response Time of Other Security Functions:
Access Checks
Get Roles
Adjudicate Results
Validate Principals


Appendix A: WebLogic Server Metrics

This appendix describes CA APM for Oracle WebLogic Server metrics.
EJB Subsystem (see page 27)
Servlet Subsystem Metrics (see page 30)
HTTP Sessions (see page 30)
JMS Subsystem (see page 32)
Distributed Destination Metrics (see page 32)
Security Subsystem (see page 33)
Clustering (see page 33)
XML Subsystem (see page 34)
JMX Metrics (see page 35)
JMX Aggregate Metrics (see page 39)
EJB Subsystem
The Workstation displays metrics for the WebLogic EJB subsystem under the following
subnodes:
Stateful metrics
NRU Cache metrics
LRU Cache metrics
Stateless metrics
Entity Cache
Message-driven
Entity
EJB Subsystem


Stateful Metrics
The following metrics are available in the Investigator tree under the WebLogic > EJB
Subsystem > Stateful node.
File Serialization:Average Response Time (ms)
Average time to serialize a file.
File Deserialization: Average Response Time (ms)
Average time to deserialize a file.
Replicate Bean:Average Response Time (ms)
Average time to replicate a bean.
NRU Cache Metrics
The following metrics for the not recently used cache are available in the Investigator
tree under the WebLogic > EJB Subsystem > NRU Cache node.
Get Beans from Pool:Average Response Time (ms)
Average time to get a bean from the NRU cache pool.
Get Beans from Pool:Average Responses Per Second
Frequency of getting a bean from the NRU cache pool.
Return Beans to Pool:Average Response Time (ms)
Average time to return a bean from the NRU cache pool.
Return Beans to Pool: Average Responses Per Second
Frequency of returning a bean from the NRU cache pool.
LRU Cache Metrics
The following metrics are available for the least recently used cache in the Investigator
tree under the WebLogic > EJB Subsystem > LRU Cache node.
Get Beans from Pool:Average Response Time (ms)
Average time to get a bean from the LRU cache pool.
Get Beans from Pool:Average Responses Per Second
Frequency of getting a bean from the LRU cache pool.
EJB Subsystem


Return Beans to Pool:Average Response Time (ms)
Average time to return a bean from the LRU cache pool.
Return Beans to Pool:Average Responses Per Second
Frequency of returning a bean from the LRU cache pool.
Stateless Metrics
Subsystem > Stateless node.
Get Bean:Average Response Time (ms)
Average time to get a stateless bean.
Get Bean:Average Responses per Second
Frequency of getting a stateless bean.
Return Bean:Average Response Time (ms)
Average time to return a stateless bean.
Return Bean:Average Responses per Second
Frequency of returning a stateless bean.
Entity Cache Metrics
Subsystem > Entity Cache node.
Average time to get a bean from the entity LRU cache.
Frequency of getting a bean from the entity LRU cache.
Return Bean:Average Response Time (ms)
Average time to return a bean from the entity LRU cache.
Return Bean:Average Responses per Second
Frequency of returning a bean from the entity LRU cache.
Servlet Subsystem Metrics


Message-Driven Metrics
Subsystem > Message-driven node.
Average time to get a message-driven bean.
Frequency of getting a message-driven bean.
Entity Metrics
Subsystem > Entity node.
Average time to get an entity bean.
Frequency of getting an entity bean.
Servlet Subsystem Metrics
The following metrics are available in the Investigator tree under the WebLogic > Servlet
Subsystem node:
Error Response Count
Cumulative error count.
Proxy Services:Average Response Time (ms)
Average time to proxy services.
HTTP Sessions
The following metrics are available in the Investigator tree under the WebLogic > HTTP
Sessions Subsystem node. The metrics are organized under subnodes for Cookie
Sessions, File Sessions, JDBC Sessions, Memory Sessions, and Replicated Sessions:
All Sessions:Session Count
Total number of open HTTP sessions.
HTTP Sessions


The following sessions are cookie sessions:
Session Count
Number of open cookie sessions.
Create Session:Average Response Time (ms)
Average time to create a session.
The following sessions are files sessions:
Session Count
Number of the open file sessions.
The following sessions are JDBC sessions:
Session Count
Number of open JDBC sessions.
The following sessions are memory sessions:
Session Count
Number of open memory sessions.
The following sessions are replicated sessions:
Session Count
Number of open replicated sessions.
Average time that is taken to create a session.
JMS Subsystem


JMS Subsystem
The following metrics are available in the Investigator tree under the WebLogic > JMS
Subsystem node:
Send Message:Average Response Time (ms)
Average time to send a JMS message.
Send Message:Average Responses Per Second
Rate of sending JMS messages.
Receive Message:Average Response Time (ms)
Average time to receive a JMS message.
Receive Message:Average Responses Per Second
Rate of receiving JMS messages.
Producer Send Response:Average Response Time (ms)
Average time for the message producer to send a response.
Producer Send Response:Average Responses Per Second
Rate of the message producer sending responses.
Distributed Destination Metrics
The following metrics are available in the Investigator tree under the WebLogic > JMS
Subsystem > Distributed Destination subnode:
Add Rate response:Average Response Time (ms)
Average time for the distributed destinations to add a response.
Add Rate response:Average Responses Per Second
Rate of the distributed destinations adding rate responses.
Remove Rate Response:Average Response Time (ms)
Average time for the distributed destinations to remove a response.
Remove Rate Response:Average Responses Per Second
Rate of the distributed destinations removing rate responses.
Security Subsystem


Security Subsystem
The following metrics are available in the Investigator tree under the WebLogic >
Security Subsystem node:
Basic User Form Authentication: Average Response Time (ms)
Average time to check basic user form authentication.
Authenticate Users: Average Response Time (ms)
Average time to authenticate a user.
Access Checks: Average Response Time (ms)
Average time to check for the access.
Get Roles: Average Response Time (ms)
Average time to get the roles given a resource and subject.
Adjudicate Results: Average Response Time (ms)
Average time to adjudicate results.
Validate Principal: Average Response Time (ms)
Average time to validate principal.
Run as Users: Average Response Time (ms)
Average time for the request on running as a particular user.
Clustering
The following metrics are available in the Investigator tree under the WebLogic >
Clustering node:
Change Event:Count
Number of times a cluster change event is fired to all listeners.
Change Event:Average Responses Per Second
Rate of firing a cluster change event to all listeners.
Announce:Count
Number of announcements that have been received from remote clusters.
Announce:Average Response Time (ms)
Average time to process an announcement from remote clusters.
Announce:Average Responses Per Second
Rate of receiving announcements from remote clusters.
XML Subsystem


Full State Dump:Count
Number of full state dumps sent to all remote clusters.
Full State Dump:Average Responses Per Second
Rate of full state dumps sent to all remote clusters.
NAK Processing:Average Response Time (ms)
Average time to process an NAK from remote clusters.
NAK Processing:Average Responses Per Second
Rate of receiving NAKs from remote clusters.
Peer Gone Listeners:Count
Number of peer gone listeners to the RJVM.
Peer Gone Listeners|Add:Average Response Time (ms)
Average time to add a peer gone listener.
Peer Gone Listeners|Add:Average Responses Per Second
Rate of adding peer gone listeners.
RJVM Remote Call:Error Count
Number of Errors on RJVM Remote Calls.
XML Subsystem
The following metrics are available in the Investigator tree under the WebLogic > XML
Subsystem node:
SAX Parsers:Creation Count
Number of SAX parsers are created.
Document Builder:Creation Count
Number of document builders parsers are created.
SAX Transformer:Creation Count
Number of SAX Transformer are created.
JMX Metrics


JMX Metrics
The following metrics are available in the Investigator tree under the JMX node in the
format: JMX\|(.*)\|(Type=)?<MBean Name>:<Attribute Name>.
ServerRuntime: OpenSocketsCurrentCount
The current number of sockets open on the server.
ServerRuntime: SocketsOpenedTotalCount
The total number of sockets that have been opened on the server.
ExecuteQueueRuntime: ExecuteThreadCurrentIdleCount
The number of idle threads that are assigned to the queue.
ExecuteQueueRuntime: PendingRequestCurrentCount
The number of waiting requests in the queue.
ExecuteQueueRuntime: ServicedRequestTotalCount
The number of requests that this queue processes.
JDBCDataSourceRuntime: ActiveConnectionsCurrentCount
The number of JDBC connections currently in use in this datasource.
JDBCDataSourceRuntime: ConnectionsTotalCount
The total number of JDBC connections created in this datasource from the time it
was deployed.
JDBCDataSourceRuntime: LeakedConnectionCount
The number of JDBC connections that were leaked.
JDBCDataSourceRuntime: WaitingForConnectionCurrentCount
The number of connection requests waiting for a JDBC connection.
JDBCDataSourceRuntime: NumAvailable
The number of JDBC connections that are currently available in this datasource.
EJBCacheRuntime: ActivationCount
The total number of beans from this EJB Home that have been activated.
EJBCacheRuntime: CacheAccessCount
The total number of attempts to access a bean from this cache.
EJBCacheRuntime: CachedBeansCurrentCount
The current number of beans from this EJB Home that are in the EJB cache.
EJBCacheRuntime: CacheHitCount
The number of cache access attempts that have succeeded.
JMX Metrics


EJBLockingRuntime: TimeoutTotalCount
Total number of threads that have timed out waiting for a lock on a bean.
EJBPoolRuntime: BeansInUseCount
The number of bean instances from this pool that are currently being used.
EJBPoolRuntime: IdleBeansCount
The number of bean instances from this pool that are currently free.
EJBPoolRuntime: TimeoutTotalCount
Total number of threads that have timed out waiting for an available bean from this
pool.
EJBPoolRuntime: WaiterCurrentCount
Provides a count of the number of Threads currently waiting for an available bean
instance from the free pool.
EJBTransactionRuntime: TransactionCommittedTotalCount
The total number of transactions that have been committed for this EJB.
JMSRuntime: ConnectionsTotalCount
The total number of JMS connections made to this WebLogic Server after the last
reset.
JMSRuntime: JMSServersCurrentCount
The total number of JMS servers that are deployed on this WebLogic Server
instance.
JMSPooledConnectionRuntime: NumAvailable
The number of available JMS sessions in the pool that are not currently being used.
JMSDestinationRuntime: BytesReceivedCount
The number of bytes received in this destination after the last rest.
JMSDestinationRuntime: ConsumersTotalCount
The total number of consumers that have accessed this destination after the last
reset.
JMSDestinationRuntime: MessagesReceivedCount
The number of messages received in this destination after the last reset.
JMSDestinationRuntime: BytesCurrentCount
The current number of bytes stored in the destination.
JMSDestinationRuntime: ConsumersCurrentCount
The current number of consumers accessing this destination.
JMX Metrics


JMSDestinationRuntime: MessagesCurrentCount
The current number of messages in the destination.
JMSDurableSubscriberRuntime: MessagesReceivedCount
The number of messages that this durable subscriber receives after the last reset.
JMSDurableSubscriberRuntime: BytesCurrentCount
The number of bytes that this durable subscriber receives.
JMSDurableSubscriberRuntime: MessagesCurrentCount
The number of messages still available by this durable subscriber.
JMSServerRuntime: BytesReceivedCount
The total number of bytes that this JMS server receives after the last reset.
JMSServerRuntime: BytesCurrentCount
The current number of bytes stored on this JMS server.
JMSConnectionRuntime: SessionsCurrentCount
The current number of sessions for this connection.
TransactionNameRuntime: TransactionAbandonedTotalCount
The total number of transactions that were abandoned after the last reset.
TransactionNameRuntime: TransactionCommittedTotalCount
The total number of transactions that were committed after the last reset.
TransactionNameRuntime: TransactionHeuristicsTotalCount
The total number of transactions that completed with a heuristic status after the
last reset.
TransactionNameRuntime: TransactionRolledBackTotalCount
The total number of transactions that were rolled back after the last reset.
TransactionNameRuntime: TransactionRolledBackTimeoutTotalCount
The total number of transactions that were rolled back due to a timeout experience
after the last reset.
TransactionNameRuntime: TransactionTotalCount
The total number of transactions processed (committed/rolled back/heuristic) since
the last reset.
JMX Metrics


TransactionResourceRuntime: TransactionCommittedTotalCount
The total number of transactions that were committed since the last reset.
TransactionResourceRuntime: TransactionHeuristicsTotalCount
The total number of transactions that completed with a heuristic status since the
last reset.
TransactionResourceRuntime: TransactionRolledBackTotalCount
The total number of transactions that were rolled back since the last reset.
TransactionResourceRuntime: TransactionRolledBackTimeoutTotalCount
since the last reset.
TransactionResourceRuntime: TransactionTotalCount
the last reset.
JTARuntime: TransactionAbandonedTotalCount
The total number of transactions that were abandoned since the last reset.
JTARuntime: TransactionCommittedTotalCount
The total number of transactions that were committed since the last reset.
JTARuntime: TransactionHeuristicsTotalCount
The total number of transactions that completed with a heuristic status since the
last reset.
JTARuntime: TransactionRolledBackTotalCount
The total number of transactions that were rolled back since the last reset.
JTARuntime: TransactionRolledBackTimeoutTotalCount
since the last reset.
JTARuntime: TransactionTotalCount
the last reset.
Server: IdleConnectionTimeout
The current value of the HTTP Session timeout.
JMX Aggregate Metrics


JMX Aggregate Metrics
The following metrics are available in the Investigator tree under the WebLogic > JMX
Aggregate node:
Thread Pool: Waiting Request Count
Provides a count of the total number of Threads currently requesting for an
available instance from the free pool.
JDBC Connection Pool: Waiting Thread Count
Provides a count of the total number of Threads currently waiting for an available a
connection instance from the free pool.
EJB Pool: Waiting Thread Count
Provides a count of the total number of Threads currently waiting for an available
bean instance from the free pool.

APM - 9.5 - APM For Oracle WebLogic Server Guide

Uploaded by

Copyright:

Available Formats

APM - 9.5 - APM For Oracle WebLogic Server Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

APM - 9.5 - APM For Oracle WebLogic Server Guide

Uploaded by

Copyright:

Available Formats

for Oracle WebLogic Server Guide

You might also like