CA Application Performance Management
Overview Guide Release 9.6
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 is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. 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 © 2014 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 (CA APM ErrorDetector)
■
CA Application Performance Management for CA Database Performance (CA APM for CA Database Performance)
■
CA Application Performance Management for CA SiteMinder® (CA APM for CA SiteMinder®)
■
CA Application Performance Management for CA SiteMinder® Application 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 for z/OS (CA APM for IBM WebSphere Application Server for z/OS)
■
CA Application Performance Management for IBM WebSphere for Distributed Environments (CA APM for IBM WebSphere for 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®
■
CA NetQoS® Performance Center
■
CA Performance Center
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 Chapter 1: Introducing CA Application Performance Management
11
Welcome to CA Technologies Application Performance Management ..................................................................... 11 CA Introscope® and CA CEM ...................................................................................................................................... 13
Chapter 2: Understanding the CA APM Environment
15
About CA APM ............................................................................................................................................................ 15 What is CA Introscope®? ............................................................................................................................................ 16 What Does CA Introscope® Do? ................................................................................................................................. 16 CA Introscope® Components...................................................................................................................................... 18 Enterprise Manager ............................................................................................................................................ 18 Agents ................................................................................................................................................................. 19 Workstation ........................................................................................................................................................ 19 WebView ............................................................................................................................................................. 21 SmartStor ............................................................................................................................................................ 21 APM Database ..................................................................................................................................................... 21 Baselines Database ............................................................................................................................................. 21 Transaction Events Database .............................................................................................................................. 22 CA Introscope® Alerts and Reports Output ................................................................................................................ 22 How CA Introscope® Monitors Java and .NET Applications ....................................................................................... 22 What is CA CEM? ........................................................................................................................................................ 24 What Does CA CEM Do? ............................................................................................................................................. 24 CA CEM Components ................................................................................................................................................. 25 Enterprise Manager ............................................................................................................................................ 25 CEM Console ....................................................................................................................................................... 26 TIM ...................................................................................................................................................................... 26 APM Database ..................................................................................................................................................... 26 CA CEM and Web Transactions .................................................................................................................................. 27 CA APM Environment Options ................................................................................................................................... 27 Standalone Environment..................................................................................................................................... 28 Clustered Environment ....................................................................................................................................... 29 Multiple-Cluster Environment............................................................................................................................. 30 Infrastructure Aware Application Triage Environment ....................................................................................... 31 Unified End-User Experience Monitoring Environment ...................................................................................... 33 CA Introscope®-Only Environment ..................................................................................................................... 34 Additional Extensions Provided With Your License .................................................................................................... 35 CA APM Product Architecture .................................................................................................................................... 39
Contents 7
CA Application Performance Management for SOA .................................................................................................. 39
Chapter 3: Integrating With Other CA Technologies Products
41
CA Introscope® Integration With Other CA Technologies Products ........................................................................... 41 CA Introscope® Integration With CA SOI ............................................................................................................. 41 CA Introscope® Integration With CA CMDB ........................................................................................................ 42 CA Introscope® Integration With CA Spectrum Infrastructure Manager ............................................................ 43 CA Introscope® Integration With CA eHealth ..................................................................................................... 45 CA Introscope® Integration With CA NSM .......................................................................................................... 46 CA Introscope® Integration With CA Insight Database Performance Monitor (DPM) ........................................ 47 CA Introscope® Integration With CA Cloud Monitor ........................................................................................... 48 CA Introscope® Integration With CA Performance Center ................................................................................. 48 CA CEM Integration With Other CA Technologies Products ...................................................................................... 49 CA CEM Integration With CA CMDB .................................................................................................................... 49 CA CEM Integration With CA SiteMinder ............................................................................................................ 50 CA CEM Integration With CA NSM ...................................................................................................................... 50 CA CEM Integration With CA Service Desk .......................................................................................................... 51
Chapter 4: CA APM Product Scenarios
53
CA APM Scenario ........................................................................................................................................................ 53 Introscope Scenarios .................................................................................................................................................. 53 Recording an Agent-Only Banking Business Transaction to Monitor Customer Transaction Times ................... 54 Using the Application Triage Map to See What is Up and Running .................................................................... 55 Dynamic Instrumentation: Adding, Removing, and Exporting Instrumentation Using the Transaction Tracer .................................................................................................................................................................. 57 CA CEM Scenarios....................................................................................................................................................... 59 CA EEM and Business Service-Based Security Provide Flexible Permissions ...................................................... 59 CA CEM Automatic Transaction Discovery Speeds Monitoring from Test to Production Environments............ 61 Monitoring Defects in Multibyte Applications .................................................................................................... 62 CA Application Performance Management for SOA Scenario .................................................................................... 63
Appendix A: CA APM Guides and Help System
67
The CA Support Online Knowledge Base .................................................................................................................... 67 Accessing the Knowledge Base ........................................................................................................................... 67 Searching and Browsing Knowledge Base Articles .............................................................................................. 67 Most Popular Knowledge Base Articles .............................................................................................................. 68 Additional CA APM Product and Information Resources ........................................................................................... 69 CA APM Community Site ..................................................................................................................................... 69 CA Education Services ......................................................................................................................................... 69 CA Professional Services ..................................................................................................................................... 70
8 Overview Guide
CA Support .......................................................................................................................................................... 70
Index
71
Contents 9
Chapter 1: Introducing CA Application Performance Management This section contains the following topics: Welcome to CA Technologies Application Performance Management (see page 11) CA Introscope® and CA CEM (see page 13)
Welcome to CA Technologies Application Performance Management CA Introscope® and CA Customer Experience Manager (CA CEM) come together as the core products in the CA Technologies Application Performance Management (CA APM) solution. CA APM provides an effective and comprehensive application performance management strategy that enables you to understand the end-user experience and measure Service Level Agreements (SLAs). You can map all transactions to the end-to-end infrastructure, and conduct incident triage and root-cause diagnoses in a complete and integrated solution. This ability provides you with bookend coverage—from end-user website monitoring using CA CEM to deep internal application monitoring using CA Introscope®. CA APM helps you do the following: ■
Understand the real user experience.
■
Set and manage SLAs on business services to answer "Are our service levels acceptable?"
■
Gain near 100 percent transaction visibility.
■
Determine the source of problems quickly.
■
Conduct triage, identify stakeholders, and perform root cause analyses.
■
Prioritize incidents that are based on a true business impact.
■
Provide proactive and predictive application monitoring.
■
Increase reporting and enable continuous improvement.
CA APM manages the performance and availability of your mission-critical and revenue-generating business applications and transactional environments. ■
Monitors your real website and web application users. CA APM is not a robot monitoring synthetic transactions. CA APM provides real-time and historical data about the experience of your end users.
Chapter 1: Introducing CA Application Performance Management 11
Welcome to CA Technologies Application Performance Management
■
Measures the business value of the experience of each user, allowing you to establish SLAs. As shown in the following graphic, in a complex application infrastructure environment, little issues add up. Even short periods of down time in disparate applications across your environment can add up to unacceptable experience for your website or web application users.
■
12 Overview Guide
Connects the dots across your environment. –
Monitors transactions map to business services, which map to your SLAs.
–
Provides Transaction Tracing across complex application environments and associated infrastructure including Java, MQ, SOA, and .NET.
■
Proactively detects and prioritizes problems that are based on a business impact.
■
Conducts incident triage and root cause analysis across complex application environments and associated infrastructure.
■
CA APM shows the source of an issue. IT triagers can quickly alert the expert who owns the problem and determine whether the issue is a network, application, or database problem, for example.
■
Provides predictive baselining to establish trends.
■
Supplies reporting that is based on a large number of metrics.
CA Introscope® and CA CEM
CA Introscope® and CA CEM CA APM integrates CA Introscope® and CA CEM. ■
This integration provides a common transaction model for CA Introscope® and CA CEM. –
CA APM components use same language when monitoring and displaying data about your business applications. CA APM provides information about business services and business components. CA Introscope® is no longer looking only at, for example, only Agent A and its metric. Now CA Introscope® provides data about the most mission-critical application at your organization and uses the data as visual output to provide the application triage map.
–
You can measure response times and SLAs.
–
This model provides cross-functional CA Introscope® and CA CEM capabilities such as agent-only business transaction recording. CA Introscope® now allows you to record information from agents using the CEM console. CA Introscope® agents can now record and monitor transactions, allowing you to track information about how your application is doing from a business perspective.
■
This integration monitors and allows reporting on all transactions through your IT infrastructure. –
CA APM dashboards show the business health of your mission-critical applications.
–
CA APM provides business and technical information.
–
Based on the common transaction model, CA APM monitoring supports multiple types of users.
– ■
■
CEOs and CFOs use high-level easy to digest CA Introscope® dashboards. These users track how much business activity is happening per time period and the amount of income coming in to an organization.
■
Technical users use detailed Introscope Workstation trees, the application triage map, and CA CEM to see technical information to monitor and triage.
Information about your business services is based on shared CA CEM and CA Introscope® data.
This integration lets you triage problems quickly and easily. –
You can understand your environment from end-user experience down to deep application health.
Chapter 1: Introducing CA Application Performance Management 13
CA Introscope® and CA CEM
–
You can detect issues proactively, conduct problem triage, and diagnose the root cause of the problem.
–
You can use the application triage map to see real-time metrics about your mission-critical business applications.
Note: To learn more about how CA Technologies and CA APM products work together, see www.ca.com/apm.
14 Overview Guide
Chapter 2: Understanding the CA APM Environment This section contains the following topics: About CA APM (see page 15) What is CA Introscope®? (see page 16) What Does CA Introscope® Do? (see page 16) CA Introscope® Components (see page 18) CA Introscope® Alerts and Reports Output (see page 22) How CA Introscope® Monitors Java and .NET Applications (see page 22) What is CA CEM? (see page 24) What Does CA CEM Do? (see page 24) CA CEM Components (see page 25) CA CEM and Web Transactions (see page 27) CA APM Environment Options (see page 27) Additional Extensions Provided With Your License (see page 35) CA APM Product Architecture (see page 39) CA Application Performance Management for SOA (see page 39)
About CA APM Together CA CEM and CA Introscope® create the CA APM solution, which allows you to address both your business and IT concerns. ■
CA APM addresses business concerns With customer experience metrics, you can answer questions that are important to the business: –
Are my customers getting the level of service that they need?
–
Are we getting the Return on Investment that we expect from our web applications and services?
–
Are web customers experiencing a problem that is affecting the bottom line?
Using customer experience metrics, you can receive regular updates for the volume, errors, and average response time of business transactions critical to your business. You can create custom business dashboards so your business users can see how the web-based business transactions are performing in real time.
Chapter 2: Understanding the CA APM Environment 15
What is CA Introscope®?
■
CA APM addresses IT concerns: With incident and defect troubleshooting, you can answer questions that are important to IT: –
Are the web applications and services available and performing as expected?
–
Are we effective at resolving customer issues quickly, before there is a widespread impact?
–
Are we meeting the SLA levels that we promised to the business users?
You can use CA CEM to analyze the root cause of problems by using correlated transaction information from CA Introscope®. You can triage support cases quickly, directing issues to the appropriate teams. This process enables faster problem resolution, higher transaction success rates, and more consistent revenue streams. When slow time transaction defects begin to increase, your incident generation settings take effect. These settings cause CA CEM to initiate CA Introscope® transaction trace sessions.
What is CA Introscope®? CA Introscope® is an enterprise application performance management solution. This solution lets you monitor complex web applications in production environments 24x7, detect problems before they affect your customers, and resolve these issues quickly and collaboratively. CA Introscope® gives you the ability to manage transaction integrity and user satisfaction—key requirements for ensuring successful customer interactions with your mission-critical web applications. Using patented, low-overhead technology, CA Introscope® provides comprehensive end-to-end transaction visibility and diagnostic capabilities across your entire infrastructure without degrading performance. The infrastructure can include the web application itself, application servers, web servers, messaging middleware, databases, and transaction servers.
What Does CA Introscope® Do? CA Introscope® performs end-to-end Java and .NET application transaction management and analysis. A transaction is a request that starts with a user and is sent to or uses back-end systems such as databases, a mail server, or messaging system. CA Introscope® also monitors web services and application use of messaging-oriented middleware, such as WebSphere MQ, extending application performance management to Service Oriented Architecture (SOA) applications.
16 Overview Guide
What Does CA Introscope® Do?
CA Introscope® prevents and solves enterprise application problems as it performs these functions: ■
Monitors applications so you know what is going on from the inside out across your broad enterprise network and systems.
■
By monitoring load, requests, and sessions, CA Introscope® lets you know how your application system resources are getting consumed.
■
Uses alerts to notify the right person—application support or the Service Level Manager—to diagnose and solve production problems.
■
Provides system triage by identifying offending subsystems: –
Is our problem in the code, the database, or the backend?
–
Are our service levels acceptable?
CA Introscope® sees through the tangle of front-end, connectivity, and back-end applications, and answers the question: What is the impact and priority of the problem? ■
Enables problem root cause diagnosis CA Introscope® isolates a problem and pinpoints it to the component or method level. These capabilities allow you to determine, for example: –
Is there a specific SQL call that is badly constructed?
–
Is there a bottleneck through an overused component?
–
Does the application inefficiently use its backends?
–
Are there enough resources to power the application?
With CA Introscope®, you can quickly and reliably answer these questions and determine where to assign the fix.
Chapter 2: Understanding the CA APM Environment 17
CA Introscope® Components
CA Introscope® Components The major components of CA Introscope® are the Enterprise Manager, CA Introscope® agents, Workstation, WebView, SmartStor, and APM database as shown in the following graphic. Many smaller components are explained in the CA Introscope® product documentation.
Enterprise Manager The Enterprise Manager acts as the repository of CA Introscope® performance metrics. The Enterprise Manager receives performance metrics from one or more CA Introscope® agents, allowing users to collect metrics centrally from many applications, application servers, and supporting systems. You can deploy the Enterprise Managers in different ways depending on the size and complexity of the enterprise system. The role of a specific Enterprise Manager depends on how it is deployed in a standalone or in a clustered CA APM environment. More information: Standalone Environment (see page 28) Clustered Environment (see page 29) Multiple-Cluster Environment (see page 30)
18 Overview Guide
CA Introscope® Components
Agents CA Introscope® agents collect and report several types of application and environmental performance metrics. One agent is deployed per process (Java Virtual Machine [JVM] or .NET CLR instance). The total number of agents depends on the size of the CA Introscope® deployment, for example: ■
A small pilot network uses as few as half a dozen agents to monitor a few test applications.
■
A large extended enterprise production environment uses hundreds or thousands of agents to monitor applications across the enterprise.
CA Introscope® agents collect performance metrics from several sources: ■
The various components inside the running application
■
The application server
■
Performance and availability data from the surrounding computing environment.
The agents then report these metrics to the Enterprise Manager. You can import real-time generic and non-Java data into CA Introscope® through modified version of the agent named the Environment Performance Agent (EPA or EPAgent). EPA uses simple scripts that allow CA Introscope® to monitor virtually any type of application subsystem impacting performance. For example, using EPA CA Introscope® can monitor directory servers, operating systems, messaging middleware, and transaction servers.
Workstation The Workstation provides the Investigator, console, and APM Status Console for viewing application health and data. The Workstation also allows CA Introscope® administrators to do the following actions: ■
Set alerts for individual metrics or logical metric groups.
■
Customize views to represent their unique environment.
■
Set up reports for application health, SLAs, and capacity planning.
Console The Workstation console provides CA Introscope® dashboards, which are high-level screens showing status using color-coded alerts.
Chapter 2: Understanding the CA APM Environment 19
CA Introscope® Components
Investigator The Workstation Investigator contains two primary tabs: the Metric Browser and Triage Map tabs. Metric Browser tab Displays metric data in both tree and tab formats. These formats allow CA Introscope® users to view different types of information about the component or resource selected in the Investigator tree. You can use the metric browser tree Location Map tab to view alert data that infrastructure domain managers monitoring physical and virtual machines report. Using the Location map, you can triage problems down to the physical and virtual system infrastructure. Triage Map tab Displays the application triage map, which is an application-centric view of your monitored applications. The application triage map presents a graphical visualization of the components that make up your application, showing application health and errors. This map is automatically generated from CA Introscope® and customer experience metrics, component discoveries, and events, which are displayed in the By Frontends node. In the By Business Service node, the application triage map presents applications and business transactions in the business-centric terms that you have defined. The application triage map enables you to grasp instantly in a visual manner the structure of applications and the relationship between applications in your environment. This information helps you identify and triage current and emerging problems. The application triage map also displays information about your system resources such as percent CPU usage. The TradeService frontend application displays the calling of number of its dependencies. The yellow indicator on the top left corner of the AuthenticationEngine icon shows that the application is in an unhealthy state, which is based on the IT application owner definition of unhealthy. By hovering on the application triage map icons, you can see transaction metrics for each call.
APM Status Console The APM Status console is an Introscope Workstation user interface for monitoring and addressing Enterprise Manager runtime health issues. CA APM administrators can view important status and events for a stand-alone or clustered Enterprise Manager. This functionality provides out-of-the-box monitoring capabilities that would otherwise require the administrator to configure alerts on Enterprise Manager supportability metrics.
20 Overview Guide
CA Introscope® Components
The APM Status Console consists of four panes: 1.
Enterprise Manager Map
2.
Important Events
3.
Information
4.
Denied Agents
WebView WebView presents the CA Introscope® customizable dashboards and the Workstation tree views to authorized users in a browser interface. These capabilities allow CA Introscope® users to view critical information anytime and anywhere.
SmartStor SmartStor is the largest of the four CA Introscope® data stores for storing metric and transaction data. The CA Introscope® SmartStor database records all application performance data (CA Introscope® metrics) at all times. This database information lets users analyze historical data, identify root causes of application downtime, or perform capacity analysis without the need for an external database. SmartStor is enabled by default during CA Introscope® installation. SmartStor data is set to age out over time, so the data store will not get excessively large. Multiple data files can grow in number as more data is generated.
APM Database The APM database includes business service and business transaction data, which is used in the CA Introscope® Investigator application triage map and for CA CEM incidents and defects. The database also stores all CA CEM-related configuration data. Note: Both CA Introscope® and CA CEM use the APM database.
Baselines Database The CA Introscope® baselines database stores the most common, normal range of values for each metric in your system. The CA Introscope® heuristic logic uses the values to determine whether there is an abnormal condition that requires administrator attention, or special event process such as Transaction Tracer.
Chapter 2: Understanding the CA APM Environment 21
CA Introscope® Alerts and Reports Output
Transaction Events Database The CA Introscope® Transaction Events database contains detailed transaction data. This data includes Transaction Traces, stalls, and data that is collected from triggered events, such as error snapshots.
CA Introscope® Alerts and Reports Output In addition to sending performance data to the Workstation and WebView for viewing, you can configure an Enterprise Manager or MOM to send output to other systems. CA Introscope® can send the following output: ■
Alerts, event notifications, performance data CA Introscope® can send this output to Tivoli and other integrated CA Technologies applications.
■
Specialized application health, SLA, and capacity planning reports. CA Introscope® can send this output to your business managers, SLA managers, and capacity planners, for example.
How CA Introscope® Monitors Java and .NET Applications CA Introscope® captures transaction data about run-time activity in your Java and .NET web applications as follows: 1.
CA Introscope® inserts probes into Java Virtual Machines (JVMs) and .NET Common Language Runtime components (CLRs). These probes monitor application-component bytecode such as called classes, methods, and parameters. CA Introscope® does not touch your source code.
2.
The probes report data to agents.
3.
The agents report data to the Enterprise Manager. Other subsystems, like Java Management Extensions (JMX) and Performance Monitoring Infrastructure (PMI), report data that the agents collect. The agent also records and sends captured structural data about applications to the Enterprise Manager. This data displays in a graphical format as the application triage map. The application triage map also shows how the business transaction flows into the frontends that service the applications.
4.
The Enterprise Manager compiles this data into metrics and uses the metrics data in the following components: ■
22 Overview Guide
The APM database includes business service and business transaction data, which is used in the CA Introscope® Investigator application triage map and for CA CEM incidents and defects. This database also stores all CA CEM-related configuration data.
How CA Introscope® Monitors Java and .NET Applications
■
The CA Introscope® Workstation allows you to control CA Introscope® and access performance metrics. You can set alerts for individual metrics or logical metric groups, view performance metrics, and you can customize views for your own unique environment.
■
The CA Introscope® WebView presents the CA Introscope® customizable dashboards and Investigator tree views in a browser interface. WebView allows critical information to be viewed without the aid of the CA Introscope® Workstation.
■
The CA Introscope® SmartStor database records all application performance data (CA Introscope® metrics) at all times. This database enables users to analyze historical data, to identify the root causes of application downtime, or perform capacity analysis without the need for an external database.
The following graphic shows a high-level view of how CA Introscope® monitors applications to measure application health.
Chapter 2: Understanding the CA APM Environment 23
What is CA CEM?
What is CA CEM? CA CEM is a performance monitoring product that measures web application performance for each individual customer. This capability enables both your business managers and IT staff to understand and resolve performance problems before end users call for support. CA CEM focuses on the monitoring and management of the customer experience, and the quality of service levels that are provided to customers. CA CEM enables you to monitor real user activities—including login, account update, or purchase transactions—at the business service level. This level of performance monitoring provides you with immediate insight into the experience of your customers.
What Does CA CEM Do? CA CEM measures the performance and quality of customer transactions, identifies defects and variance, and quantifies the impact on customers and the business. By proactively detecting trends in degraded customer transaction response times and providing various actionable reports, CA CEM enables you to act before problems occur or SLAs are out of compliance. These capabilities allow you to answer the following questions, for example:
24 Overview Guide
■
How many requests to a specific service failed during the last hour?
■
Which customers and users were affected when specific transactions failed?
■
What is the status of my application network?
■
How long did a specific request take?
CA CEM Components
CA CEM Components The CA CEM components are the Enterprise Manager, CEM console, Transaction Impact Monitor (TIM), and the APM database as shown in the following graphic.
Enterprise Manager The Enterprise Manager runs the following Enterprise Manager services that CA CEM primarily uses: ■
TIM Collection
■
Stats Aggregation
■
Database Cleanup.
You must distribute the services across different Collectors. CA CEM users access the CEM console from the Manager of Managers (MOM) Enterprise Manager. You can deploy Enterprise Managers in different ways depending on the size and complexity of the enterprise system. The role of a specific Enterprise Manager depends on how it is deployed in a standalone or in a clustered CA CEM environment. More information: Standalone Environment (see page 28) Clustered Environment (see page 29) Multiple-Cluster Environment (see page 30)
Chapter 2: Understanding the CA APM Environment 25
CA CEM Components
CEM Console The CEM console is a user interface that lets you do the following functions: ■
Set up and configure CA CEM, including transaction recording and creating transaction definitions.
■
Produce and view CA CEM-specific reports.
■
View defect data and transaction definitions, group transactions into services, and manage CA CEM user access to CA CEM data.
TIM The TIM is responsible for the following functions: ■
Recording and observing HTTP packets.
■
Identifying user logins and the related transactions.
■
Monitoring and reporting defects and other statistics to the Enterprise Manager. Defects are generated per defective transaction; a single transaction can create multiple defects.
■
Uploading the defects and interval statistics to the Enterprise Manager. –
For enterprise applications, interval statistics are generated per hour, per transaction definition, and per user.
–
For e-commerce applications, interval statistics are generated per hour and per transaction definition.
One or more TIMs can exist in a CA APM environment.
APM Database The APM database stores defect and incident data, and user-based statistics for both enterprise and e-commerce users. The database also stores all CA CEM-related configuration data. Note: Both CA CEM and CA Introscope® use the APM database.
26 Overview Guide
CA CEM and Web Transactions
CA CEM and Web Transactions CA CEM monitors the customer experience (HTTP traffic) at a point between the client and the web server. For example, CA CEM can see if a transaction is running slowly while verifying if a book is in stock. In addition, CA CEM can see if there are overall defects to the transaction, for example, if any components or responses are missing. CA CEM TIM monitoring also pinpoints which customers were experiencing the issue, which customers were not, and why. For added capability, you can use CA Application Performance Management Transaction Generator (CA APM TG). CA APM TG provides synthetic transactions to test and monitor your web services with CA CEM. CA APM TG generates simulated transactions that CA CEM then monitors to find and fix problems. This process can identify problems that arise outside business hours—before real users and real customers are affected.
CA APM Environment Options You can set up any of the following environments: If you are monitoring
You can deploy to For more information, see this environment
Small lab, Proof of Concept, or low Standalone CA metric volume environments APM
Standalone environment (see page 28)
Many web applications and web transactions
Clustered environment (see page 29)
Clustered CA APM
Large numbers of web applications Multiple-cluster and web transactions that can be CA APM in different areas of the enterprise
Multiple-cluster environment (see page 30)
Many web applications and web transactions and exchange data with other CA Technologies Infrastructure Management products
Infrastructure Infrastructure Aware Aware Application Application Triage Triage environment (see page 31)
Many web applications and web transactions and exchange data with CA Application Delivery Analysis network monitoring components
Unified End User Experience Monitoring
Unified End User Experience Monitoring environment (see page 33)
Java or .NET applications with no HTTP component
CA Introscope® only
Introscope only environment (see page 34)
Chapter 2: Understanding the CA APM Environment 27
CA APM Environment Options
The CA APM environment that you deploy depends on many factors including the size and complexity of your network. Other factors include the number of web applications you want to monitor using CA Introscope® and the number of web applications and web transactions you want to monitor using CA CEM.
Standalone Environment When you deploy CA APM using a single Enterprise Manager to collect all agent metrics (see the following graphic), this setup is named a standalone environment.
Note: Performance metric data from outside sources (non-Java systems and .NET) can also be sent to the Enterprise Manager. For example, the CA Technologies Environment Performance Agent is a product that integrates metric data from non-Java sources into CA Introscope® to monitor system information. A standalone environment is valuable for testing your prerelease applications. For example, use a standalone environment for the following capabilities:
28 Overview Guide
■
Get insight into the performance of your prerelease application and detecting load issues on test platforms.
■
Provide visibility into failing application components and performance of back-end systems.
■
Integrate and compare data from load testing tools to application performance.
■
Focus testing with the business impact of potential performance issues in mind.
■
Create and refine transaction definitions that you later roll out to production.
CA APM Environment Options
Clustered Environment You can cluster the Enterprise Managers to scale your CA APM environment when you have a large system that generates large numbers of metrics. In a CA Introscope® cluster, multiple Enterprise Managers (named Collectors when clustered) collect all the agent metrics. Metrics from all the Collectors subscribe to the Manager of Managers (MOM) Enterprise Manager. The MOM compiles the metrics. In addition, the MOM manages cluster functions. For example, the MOM handles all Workstation requests for data and gathers those requests from the Collectors.
Both MOM and Collectors are Enterprise Managers. What differentiates them is the job that they perform in a cluster. The physical differentiation is done by configuring specific properties in CA Introscope® files. Because they store large amounts of data, each Collector and MOM requires a dedicated disk for its SmartStor database.
Chapter 2: Understanding the CA APM Environment 29
CA APM Environment Options
Multiple-Cluster Environment Your organization can deploy multiple clusters, as shown in the following graphic.
The Cross-cluster Data Viewer (CDV) is a specialized Enterprise Manager that gathers agent and customer experience metrics data from multiple Collectors across multiple clusters. Using the CDV Workstation, CA Introscope® administrators and triagers can create and view dashboards showing a consolidated view of agent and customer experience metrics that the Collectors provide. Each Collector can connect to multiple CDVs, giving your organization flexibility in monitoring and viewing applications that are reporting to different CA APM clusters. Note: The following features cannot be viewed in the CDV Workstation:
30 Overview Guide
■
Application Triage Map
■
Customer Experience Manager
CA APM Environment Options
Infrastructure Aware Application Triage Environment Infrastructure aware application triage provides data and alerts to flow between CA APM and other CA Technologies infrastructure monitoring products, as shown in the graphic. In an Infrastructure aware application triage environment, CA APM sends its transaction model and alert information to CA Catalyst and receives infrastructure data from CA Catalyst. CA Catalyst is a platform for federating, correlating, reconciling, and storing high-level, business-relevant data from a wide variety of management products. Each product has a connector to send data to CA Catalyst and receive data from CA Catalyst. These CA Technologies products exchange data with CA APM using CA Catalyst: ■
CA Service Operations Insight (CA SOI) (see page 41)
■
CA Spectrum Infrastructure Manager (see page 43)
■
CA eHealth (see page 45)
Chapter 2: Understanding the CA APM Environment 31
CA APM Environment Options
■
CA Insight Database Performance Monitor (see page 47)
■
CA Virtual Assurance for Infrastructure Managers (when integrated with CA Spectrum Infrastructure Manager)
Infrastructure aware application triage enables you to do the following tasks:
32 Overview Guide
■
Visualize infrastructure dependencies in the application triage map and the Location map, including servers, virtualization layer, and databases.
■
Use the Investigator Location map that provides a view of the physical and virtual servers supporting the applications.
■
View alerts specific to databases and servers (both physical and virtual).
■
Send CA APM metric-based and entity level alerts to CA Service Operations Insight.
CA APM Environment Options
Infrastructure aware application triage allows you to isolate problems to a specific layer: physical, virtual, database, or application by providing visibility into the underlying infrastructure that has a significant impact on application performance. Using infrastructure aware application triage, component relationships are updated dynamically as transaction paths change.
Unified End-User Experience Monitoring Environment The Unified End-User Experience Monitoring solution is an integration between CA APM and CA Infrastructure Management. This integration provides visibility into both application and performance data that is related to application usage by an end user. This integration uses the Multi-Port Monitor appliance, with CA APM Transaction Impact Manager (TIM) installed, to monitor passively your application and network infrastructure. When a TIM is installed on a Multi-Port Monitor, the appliance is often referred to as a converged appliance. This integration allows you to analyze data and triage using a number of varied CA APM components and methods. The Unified End-User Experience Monitoring solution provides many deployment options, depending on the size and complexity of your network.
Chapter 2: Understanding the CA APM Environment 33
CA APM Environment Options
The following graphic shows a CA APM cluster that is integrated with the CA Performance Center and Multi-Port Monitor components.
CA Introscope®-Only Environment You deploy CA Introscope® only if your organization has purchased: ■
CA APM and you want to deploy only CA Introscope® at this time.
■
Only CA Introscope®.
When you deploy CA Introscope®, you install and configure these components:
34 Overview Guide
■
Enterprise Manager
■
SmartStor database
■
CA Introscope® Workstation
Additional Extensions Provided With Your License
■
CEM console (enabled only for agent recording)
■
APM database
■
(Optional) CA EEM for security
The following graphic shows a typical CA Introscope® only deployment in a standalone environment.
Additional Extensions Provided With Your License CA Introscope® monitors Java and .NET applications. Your CA Introscope® or CA APM license also allows you to install additional extensions that broaden functionality. Note: You must have a CA APM license to install the TIM software appliance, which CA CEM uses. The CA Introscope® extension for CA SYSVIEW is sold separately and cannot be downloaded using the base CA Introscope® or CA APM license. The following table lists CA APM extensions that are available for you to install. You do a separate install for each extension. You decide how many extensions to install and when to install them.
Product
Description
CA APM ChangeDetector
Detects changes to code, configurations, tables, and files.
Chapter 2: Understanding the CA APM Environment 35
Additional Extensions Provided With Your License
Product
Description
Environment Performance Agent
Integrates metric data from non-Java sources into CA Introscope® to monitor system information, including Note: Also named EPAgent or process availability, disk statistics, web application server and web server logs, Solaris KStat and HTTP EPA service availability.
36 Overview Guide
CA APM ErrorDetector
Isolates errors that the application or backend systems generate.
CA APM for Oracle WebLogic Server
Provides additional performance management capability for any production WebLogic Server environment.
CA APM for CA SiteMinder Web Access Manager
Monitors the performance impact of CA SiteMinder and CA SOA Security Manager on distributed web applications and distributed web services, respectively.
CA APM for IBM CICS Transaction Gateway
Monitors the performance of CICS transactions and connections between any production Java application and the CICS Transaction Server.
CA APM for IBM WebSphere Distributed Environments
Provides advanced performance management for WebSphere running in production environments.
CA APM for IBM WebSphere MQ
Monitors WebSphere MQ Java connectors and critical activity inside the WebSphere MQ messaging system (MQ) and WebSphere Message Broker (WMB).
CA APM for Oracle Databases
Provides visibility into the performance and availability of Oracle databases.
CA APM for Web Servers
Provides visibility into the availability, performance, and load of web servers such as Apache, Microsoft IIS, IBM HTTP Server (IHS), and iPlanet.
CA APM for Microsoft SharePoint
Monitors SharePoint Portal components and extends visibility beyond SharePoint Portal to identify performance problems both within SharePoint Portal and in connection to critical back-end systems.
CA APM for Oracle WebLogic Server
Provides visibility into individual portlets, the entire portal workflow, and connections to critical back-end systems beyond the portal framework such as transaction servers, databases and other back-end systems.
Additional Extensions Provided With Your License
Product
Description
CA APM for IBM WebSphere Portal
Provides visibility into individual portlets, the entire portal workflow, and connections to critical back-end systems beyond the portal framework such as transaction servers, databases and other back-end systems.
CA APM TG
The CA APM TG is an intelligent, programmable agent that creates metrics. These metrics help you to monitor the availability, health, and performance of web sites and services from the perspective of a user attempting to access web sites. The CA APM TG Agent uses synthetic transactions containing a combination of FTP, HTTP, and script objects. These transactions determine the availability, round-trip response time, and content availability for specified web sites and services. CA APM TG generates transactions and sends them to CA Introscope® and CA CEM, where you can use the functionality of both products to more fully monitor your web sites and services.
Chapter 2: Understanding the CA APM Environment 37
Additional Extensions Provided With Your License
Product
Description
CA APM for SOA
Monitors critical services around the clock, detects problems proactively, and performs root cause analysis when issues arise. Provides comprehensive, live views into web services, web applications, SOA infrastructure, and the back-end systems to which they connect. CA APM for SOA includes the following functionality:
38 Overview Guide
■
Ability to monitor your TIBCO BusinessWorks (TBW) components and environment including TIBCO Enterprise Message Service (EMS) by viewing TBW-specific dashboards and metrics. Includes TBW-specific cross-process Transaction Tracing capability. You can monitor TIBCO EMS both when run in a TBW environment or as a messaging bus.
■
Ability to monitor your webMethods (WM) components and environment including webMethods Integration Server and webMethods Broker by viewing WM-specific dashboards and metrics. Includes WM-specific cross-process Transaction Tracing capability.
■
Ability to monitor your Oracle Service Bus (OSB) components and environment by viewing OSB-specific dashboards and metrics. Includes OSB-specific cross-process Transaction Tracing capability.
■
Ability to monitor your WebSphere Process Server (WPS) components and environment by viewing WPS-specific dashboards and metrics. Includes WPS-specific cross-process Transaction Tracing capability. You can monitor WESB both when run in a WPS environment or as a standalone application.
■
The SOA Dependency Map displays the relationship of the interdependent web services within your SOA environment. This capability allows you to understand quickly both the physical and logical layout of your SOA environment, and view key metrics that are related to each instrumented web service.
■
Real-time SOA dashboards and metrics that present a quantitative summary of the health of your SOA environment. Provides an up-to-date status display to help your Application Support team identify trends and changes in your SOA environment.
CA APM Product Architecture
CA APM Product Architecture CA APM provides a number of products to help you monitor your entire system. In addition to CA Introscope® and CA CEM, you can use CA APM extensions to monitor your environment. The following graphic shows the highest-level product architecture between CA Introscope®, CA APM extensions, and CA CEM.
CA Application Performance Management for SOA Service-Oriented Architecture (SOA) introduces a layer of coordination across the enterprise. For example, introducing a new business rule no longer requires that you rebuild the environment and all the dependent applications—it simply requires configuring one or two components. Decoupling business logic from deployed applications and making logic rules writable at runtime enables architects to provide a dynamic environment. CA Application Performance Management for SOA (CA APM for SOA) enables consumers and producers of web services to monitor critical services around the clock, detect problems proactively, and perform root cause analysis when issues arise. This solution provides comprehensive live views into web services, web applications, and the back-end systems to which they connect. CA APM for SOA delivers the detailed information that architects and developers use to isolate and resolve problems quickly. This information includes views of individual transactions in which web services are involved, the number and nature of web service faults, and component interactions.
Chapter 2: Understanding the CA APM Environment 39
CA Application Performance Management for SOA
The following graphic shows the highest-level CA APM for SOA product monitoring capabilities. As with CA Introscope®, CA APM for SOA provides a single solution across J2EE and .NET.
40 Overview Guide
Chapter 3: Integrating With Other CA Technologies Products This section contains the following topics: CA Introscope® Integration With Other CA Technologies Products (see page 41) CA CEM Integration With Other CA Technologies Products (see page 49)
CA Introscope® Integration With Other CA Technologies Products You can use CA Introscope® to monitor critical web applications from within these CA Technologies products: ■
Introscope integration with CA Service Operations Insight (CA SOI) (see page 41)
■
Introscope integration with CA Configuration Management Database (CMDB) (see page 42)
■
Introscope integration with CA Spectrum Infrastructure Manager (see page 43)
■
CA Virtual Assurance for Infrastructure Managers (when integrated with CA Spectrum Infrastructure Manager)
■
Introscope integration with CA eHealth (see page 45)
■
Introscope integration with CA NSM (see page 46)
■
Introscope integration with CA Insight Database Performance Monitor (DPM) (see page 47)
■
Introscope integration with Application Delivery Analysis (see page 48)
CA Introscope® Integration With CA SOI CA Service Operations Insight (CA SOI) is an advanced IT management tool that integrates with application and infrastructure domain management and other tools. This integration builds real-time views of service status to analyze and pinpoint service problems to help speed remediation and mitigate business risks. Using CA SOI, you visualize and analyze your infrastructure domains, applications and transactions together, according to the services they support. This capability lets you pinpoint, prioritize and resolve service problems across your IT supply chain to help you accomplish these business goals: ■
Minimize risks to your business
Chapter 3: Integrating With Other CA Technologies Products 41
CA Introscope® Integration With Other CA Technologies Products
■
Improve service quality and predictability
■
Optimize operational efficiency
CA APM integration with CA SOI includes these capabilities: ■
Provide the CA APM transaction model to aid in a dynamically discovered service model.
■
Provide CA APM metrics-based and entity level alerts, giving operations staff visibility into application health.
CA SOI Integration Features CA APM integrates with CA SOI as follows: ■
CA APM provides its transaction model to CA SOI. This transaction model is correlated with the infrastructure models that the infrastructure management domain managers publish. This correlation creates a dynamically discovered service model that helps operations staff more easily build and maintain these models.
■
CA APM sends metrics-based alerts and application level alerts to CA SOI, which gives operations staff visibility into application performance. This visibility helps operations staff to quickly triage and delegate tasks to the appropriate domain.
Business Value Integration with CA Service Operations Insight (CA SOI) helps improve service quality and predictability while optimizing your operations. ■
Improve service quality by quickly pinpointing sources of service-impacting issues across all technology domains—so you can quickly fix them and restore quality.
■
Identify sources of risk to services across all technology domains and improve service predictability. You can address issues before they impact quality.
■
Optimize operations by reducing the manual labor for alert and service management, reducing triage and mean-time-to-repair of service issues, and improving cross-discipline communication and collaboration.
CA Introscope® Integration With CA CMDB CA CMDB is an enterprise IT database that provides full visibility into the relationships between different components and processes in an IT infrastructure. CA CMDB makes it possible to provide and store reliable, up-to-date details on assets and their relationships with each other. These relationships form the basis for impact analysis, an important tool for managing change within an organization.
42 Overview Guide
CA Introscope® Integration With Other CA Technologies Products
The CA Technologies Unified Service Model (USM) helps organizations overcome the complexity of IT management so that organizations can take a service-focused approach. The CA Introscope®-CMDB Integration Pack allows you to integrate application objects that CA Introscope® monitors into USM. This integration gives your staff visibility into relationships and dependencies across your enterprise process infrastructure.
Integration Features CA APM integrates with CA CMDB as follows: ■
Allows CA Introscope® application objects to be displayed as Configuration Items within CMDB.
■
Provides visual representation of CA Introscope® application configuration items (and their relationships and dependencies) to streamline incident resolution and change impact analysis processes.
Business Value Integration with CA CMDB has the following business value: ■
Improves your ability to analyze service disruptions by directly linking CA Introscope® objects and IT infrastructure performance information within the CA Technologies Unified Service Model.
CA Introscope® Integration With CA Spectrum Infrastructure Manager CA Spectrum Infrastructure Manager is a network fault management system that provides proactive management of the network infrastructure through patented root-cause analysis, impact analysis, event correlation, and service level management. CA Spectrum Infrastructure Manager integrates with CA Virtual Assurance for Infrastructure Managers. CA Virtual Assurance for Infrastructure Managers supports large production virtualization environments, enhancing operational visibility and control, and driving agility. CA Virtual Assurance for Infrastructure Managers delivers a greater ROI by providing centralized, heterogeneous virtualized systems management. You can extend CA Virtual Assurance for Infrastructure Managers to support networks, databases, and applications. When the CA Virtual Assurance for Infrastructure Managers integration with CA Spectrum Infrastructure Manager is coupled with the CA APM integration with CA Spectrum Infrastructure Manager, CA APM users can get information about the virtual layer.
Chapter 3: Integrating With Other CA Technologies Products 43
CA Introscope® Integration With Other CA Technologies Products
Integration Features CA Spectrum Infrastructure Manager automatically handles these CA Introscope®-related tasks: ■
Discovers CA Introscope® agents and the applications the agents are monitoring, and then populates CA Spectrum Infrastructure Manager models.
■
Synchronizes the CA Introscope® agent status with the CA Spectrum Infrastructure Manager CA Introscope® agent model.
■
Forwards CA Introscope® alerts to the associated CA Introscope® agent model within the CA Spectrum Infrastructure Manager OneClick web server/IU network topology.
■
Server-related information and events are sent to CA APM using CA Catalyst. The Location Map displays this information. The information and events provide application support triagers with useful information about health of the physical or virtual server infrastructure.
■
The integration of CA Virtual Assurance for Infrastructure Managers and CA APM with CA Spectrum Infrastructure Manager provides application triagers with visibility into the virtual layer. The triagers use that visibility to expedite problem identification and resolution. Using this integration, triagers can answer questions such as these: –
Where is the monitored application running? Is it on a virtual server or a physical server?
–
If the monitored application is running on a virtual server, what physical host is the virtual server running on?
–
How are the virtual server and its physical host performing? Are there associated alarms that have been detected? If so, the alarms are visible on the Investigator location map.
Business Value The integration has the following business value: ■
44 Overview Guide
Monitors mission-critical web applications within CA Spectrum Infrastructure Manager OneClick for more effective monitoring and triage across your entire infrastructure.
CA Introscope® Integration With Other CA Technologies Products
■
Provides application performance alerts directly to CA Spectrum Infrastructure Manager OneClick to correlate with related network infrastructure and reduce time to resolution.
■
Provides a way for application triagers to see and understand quickly infrastructure-related information using the CA APM user interface that is optimized for the triager tasks. For example, the triager can get infrastructure data using the CA APM Location map. Access to this information allows the triager to understand how the infrastructure is affecting application performance. This understanding speeds problem resolution and avoids back and forth communication with system administrators who are each using their own user interface tools to pinpoint the problem location.
CA Introscope® Integration With CA eHealth CA eHealth continuously collects performance and usage data from voice and data network devices, physical and virtual systems, multi-vendor databases, and client/server applications. The data is then evaluated for threshold violations. CA eHealth issues early warnings in real time to help you identify threat of performance degradation, which could disrupt the business service. These warnings allow you to act before internal and external customers are impacted. CA eHealth identifies and alerts you of developing bottlenecks, degradations, and impending failures and then documents the need for repair, reconfiguration, or capacity upgrades. Role-based reports help you to meet the needs of IT and business management, operations staff, administrators, engineers, and capacity planners.
eHealth Integration Features CA eHealth monitors infrastructure-related components such as servers. CA APM gets server infrastructure information and alerts from CA eHealth, which provides application triagers with an ongoing indicator of system health.
Business Value Integration with CA eHealth helps assure the health and availability of business services by providing visibility into the health of the dependent IT infrastructure. ■
You can transform IT operations from reactive to proactive with CA eHealth patented technology to detect performance anomalies.
Chapter 3: Integrating With Other CA Technologies Products 45
CA Introscope® Integration With Other CA Technologies Products
CA Introscope® Integration With CA NSM CA NSM is a robust service and system management product that simplifies system management and provides centralized management for heterogeneous IT infrastructures. CA NSM self-manages systems and continuously assesses infrastructure components, reducing the cost and complexity that are associated with managing business-driven IT environments. Deep integration between CA Introscope® and CA NSM enables you to proactively and effectively manage the performance of your mission-critical web applications with no disruption to your existing systems management processes. CA Introscope® includes special features that allow CA NSM customers to take advantage of the CA APM industry-leading web application performance management solution.
Integration Features Integration with CA NSM has the following features: ■
Creates managed objects for CA Introscope® agents in the CA NSM Management Database. –
Includes CA Introscope® agent icons with status propagation.
–
Allows inclusion in CA NSM Business Process Views (BPVs).
■
CA Introscope® agent dashboards are available within CA NSM Explorer, 2D Map, Management Command Center, and CA NSM Portal.
■
CA Introscope® alerts appear in the CA NSM Event Console. –
Links to CA Introscope® agent dashboards are included in the alerts.
Business Value The integration has the following business value:
46 Overview Guide
■
Monitors mission-critical web applications within CA NSM consoles for more effective monitoring and triage across your entire infrastructure.
■
Allows IT organizations to collaborate more effectively by viewing CA Introscope®-collected application performance alerts in their own consoles, and communicate about issues using a common IT language.
■
Allows application performance alerts from CA Introscope® to be used in centralized correlation, notification, and resolution processes.
CA Introscope® Integration With Other CA Technologies Products
CA Introscope® Integration With CA Insight Database Performance Monitor (DPM) CA Insight Database Performance Monitor (DPM) is a product that enables you to centrally monitor and manage performance on a distributed relational database management system (RDBMS), simplifying management across databases, vendors, and operating system environments. With CA Insight DPM, you can easily view the overall health of your database infrastructure across the entire enterprise. This information lets you quickly identify, diagnose, and solve the root cause of your database performance issues before they impact business critical processes.
Integration Features Integration has the following features: ■
CA Insight DPM delivers key performance and database health information directly into CA Introscope®.
■
Provides you with CA Insight DPM metrics and out-of-the-box dashboards in CA Introscope®.
■
Includes metrics and dashboards for DB2 Linux, UNIX and Windows, SQL Server, Sybase, and DB2 for z/OS (when CA Insight for DB2 for z/OS is installed).
■
The integration component, named the Insight Bridge for CA Introscope®, provides additional database vendor support, database metrics, and additional dashboards in CA Introscope®.
Business Value The integration has the following business value: ■
Helps your application administrators and operations personnel to triage and identify database performance problems.
■
Allows you to understand CA Insight DPM key performance and database health information easily using the CA Introscope® user interface.
■
Allows you to monitor how databases are transacting application requests. You can diagnose how and what database internal workings are impacting and affecting the application workload being processed within the database.
■
Provides real-time in-depth visibility of database resources and workload for application work. This visibility eliminates guessing and resolution delay.
Chapter 3: Integrating With Other CA Technologies Products 47
CA Introscope® Integration With Other CA Technologies Products
CA Introscope® Integration With CA Cloud Monitor CA APM Cloud Monitor enables you to perform the following tasks: ■
Understand complete user experience from 60+ monitoring stations in 40+ countries.
■
Monitor real browsers to accurately measure user experience.
■
Monitor applications delivered by SaaS vendors and MSPs to keep them accountable to SLAs.
■
Test application response time from outside the firewall (using synthetic transactions) to understand global end-user experience and monitor performance even at times when there is no real user traffic.
■
Replicate real-user transactions to monitor performance throughout the application infrastructure to identify, diagnose, and resolve problems quickly.
Instructions on integrating CA APM with CA APM Cloud Monitor are in the CA APM Configuration and Administration Guide. Instructions on using CA APM to monitor CA APM Cloud Monitor are in the CA APM Workstation Guide.
CA Introscope® Integration With CA Performance Center CA APM is integrated with the following CA Infrastructure Management component: CA Performance Center. Managing network performance and providing optimal application delivery requires an understanding of the relationship among device infrastructure, network traffic, and application performance. The CA Performance Center links end-to-end service and transaction visibility with top-to-bottom understanding of the underlying IT infrastructure across networks, systems and databases. This comprehensive linkage delivers a comprehensive, unified understanding of how applications and infrastructure deliver business services. CA Performance Center includes a web-based reporting dashboard. The dashboard is designed to help network managers, engineers, and operations personnel access the right information at the right time. To transform data into actionable information, it analyzes every data packet with intelligent baselines, thresholds, trending, and anomaly detection algorithms. The integration of CA APM with CA Performance Center provides visibility into both application and performance data. This data provides information that is related to application usage by an end user. This integration utilizes the Multi-Port Monitor, with CA APM Transaction Impact Manager (TIM) installed. Note: For more information, see the CA APM Integration for CA Infrastructure Management Guide (2.0.00).
48 Overview Guide
CA CEM Integration With Other CA Technologies Products
CA CEM Integration With Other CA Technologies Products You can use CA CEM to monitor critical web applications from within these CA Technologies products: ■
CA CEM integration with CA CMDB (see page 49)
■
CA CEM integration with CA SiteMinder (see page 50)
■
CA CEM integration with CA NSM (see page 50)
■
CA CEM integration with CA Service Desk (see page 51)
CA CEM Integration With CA CMDB CA CMDB is an enterprise IT database that provides full visibility into the relationships between different components and processes in an IT infrastructure. CA CMDB makes it possible to provide and store reliable, up-to-date details on assets and their relationships with each other. These relationships form the basis for impact analysis, an important tool for managing change within an organization. The CA Technologies Unified Service Model (USM)—available and maintained within the CA CMDB—helps organizations overcome the complexity of IT management so that organizations can take a service-focused approach. The CA CEM-CMDB Integration Pack allows you to integrate application objects that CA CEM monitors into USM, giving your staff visibility into relationships and dependencies across your enterprise process infrastructure.
Integration Features The integration has the following features: ■
Incorporates CA CEM business services, business transactions, and their relationships as Configuration Items within the CMDB to facilitate reconciliation with related services.
■
Allows CA CEM application objects to be displayed as Configuration Items within CMDB. Provides visual representation of CA CEM application configuration items (and their relationships and dependencies) to streamline incident resolution and change impact analysis processes.
Business Value The integration has the following business value: ■
Improves your ability to analyze service disruptions by directly linking CA CEM objects and IT infrastructure performance information within the CA Technologies Unified Service Model.
Chapter 3: Integrating With Other CA Technologies Products 49
CA CEM Integration With Other CA Technologies Products
CA CEM Integration With CA SiteMinder CA CEM works with CA SiteMinder security software, which provides security features such as single sign-on (SSO) and centralized control of user access to web applications. You can use the CA SiteMinder plug-in when the CA CEM monitored applications are integrated with SiteMinder for single sign-on. In this case, the TIM communicates with the CA SiteMinder server to determine the user and session information. (Without CA SiteMinder, the user name and session ID can be observed in the header and the session ID does not change or expire.)
CA CEM Integration With CA NSM CA NSM is a robust service and system management product that simplifies system management and provides centralized management for heterogeneous IT infrastructures. CA NSM self-manages systems and continuously assesses infrastructure components, reducing the cost and complexity that are associated with managing business-driven IT environments. CA CEM collects important performance information about business services and transactions. This information can be shared with CA NSM, a comprehensive management solution that helps improve infrastructure performance by monitoring network and systems elements. Deep integration between CA CEM and CA NSM enables you to view and investigate CA CEM incidents almost immediately, which gives you added insight into the health of your network.
Integration Features The integration has the following features:
50 Overview Guide
■
The CA CEM-NSM bridge dynamically creates NSM WorldView objects for each CA CEM business service, business transaction, and monitored customer user group, and keeps them up to date in the NSM repository.
■
The CA CEM-NSM bridge receives notifications for any changes in CA CEM data, including incidents and severity changes, and updates the NSM repository with these changes.
■
CA CEM incidents are reported in the NSM Event Console.
CA CEM Integration With Other CA Technologies Products
Business Value The integration has the following business value: ■
You can monitor customer transactions in addition to overall network health.
■
You can see when slow response times or poor application performance affects users. This visibility helps you identify the root cause of problems so you can correct them.
CA CEM Integration With CA Service Desk CA Service Desk supports help desk analysts perform their incident management responsibilities including detecting and recording, classifying and supporting, tracking and resolving incidents. CA Service Desk employs the Information Technology Infrastructure Library (ITIL) best-practice processes by automating service support incident management. Deep integration between CA CEM and CA Service Desk enables you to send CA CEM incident and defect information to CA Service Desk, so tickets can be generated and tracked as appropriate.
Integration Features The integration has the following feature: ■
You can configure CA CEM and CA Service Desk to create service requests (or incidents) in CA Service Desk. These requests are based on incidents that CA CEM detects.
Business Value Integration with CA Service Desk provides incident management support by automatically generating service requests from CA CEM incidents.
Chapter 3: Integrating With Other CA Technologies Products 51
Chapter 4: CA APM Product Scenarios This section contains the following topics: CA APM Scenario (see page 53) Introscope Scenarios (see page 53) CA CEM Scenarios (see page 59) CA Application Performance Management for SOA Scenario (see page 63)
CA APM Scenario Introscope and CA CEM work together as CA APM to help you monitor, detect, and triage enterprise web application management problems. To help you understand CA APM and see a scenario about cross-enterprise application performance management using CA APM and CA Technologies Application Performance Management for CA SYSVIEW®, see this demonstration: http://www.ca.com/media/apm/wily/ca-wily-shell.html
Introscope Scenarios In these scenarios, the Introscope functionality allows IT personnel to quickly and easily monitor, diagnose, and triage various web application issues. ■
Recording an agent-only banking business transaction to monitor customer transaction times (see page 54)
■
Using the application triage map to see what is up and running (see page 55)
■
Dynamic instrumentation: adding, removing, and exporting instrumentation via the Transaction Tracer (see page 57)
Chapter 4: CA APM Product Scenarios 53
Introscope Scenarios
Recording an Agent-Only Banking Business Transaction to Monitor Customer Transaction Times Chris is an IT application support triager for Great Bank Inc. Part of the job that Chris does is to monitor, detect, and triage the Great Bank web site. Chris monitors the web site business transactions in which a customer logs in, does a search or account check, perhaps performs an additional banking transaction, and then logs out. Chris is often asked for business transaction information, for example, how many times a specific banking transaction such as Transfer Funds got hit in the last hour and how many seconds on average it took to complete that transaction. Chris decides to use the Introscope agent-only business transaction recording capability to answer these questions. Chris is familiar with using the CEM console to record business transactions, and has already enabled his target agent for recording operations. Chris will use the CEM console to perform the business transaction recording, and then will view the business transactions in the Investigator metric browser tree. Chris decides to record a business transaction that runs on the Great Bank banking application, which IT calls GreatBank. To start recording Chris logs in to CEM console, which Chris knows is running on the MOM. Chris goes to the Administration link, and then clicks the Business Service tab because business transactions are children belonging to business services. In the CEM console Chris clicks Business Service then New to create a new business service named GreatBankAccountCheckService. Now Chris has a business service to hold the business transaction about to be recorded. Chris next clicks the Recording Sessions tab, then New to set the recording parameters. On the Record page for Recording Type, Chris selects the Agents radio button because the Introscope agents, not the CA CEM TIMs will be recording this business transaction. Chris would rather have the TIM record this business transaction because the monitoring would extend to the end users of the application, but in the Great Bank IT area that Chris monitors, the TIM does not have visibility to the GreatBank http traffic. But Chris is happy to have the option of using the agent-only recording feature, even if the Introscope metrics collected will only extend to the edge of the Java or .NET instance serving the GreatBank application. Chris toggles to a new browser session, opens the GreatBank application and logs in to the Great Bank web site, with the goal of finding out how long the transaction takes to check account details. Chris toggles back to CA CEM, then clicks Record to bring up the Recording Session page, then clicks Record Next Transaction, which changes the Recording Status to "In progress". Chris toggles back to the Great Bank web site and on the Bank Accounts page clicks the Check Checking Account link. Chris toggles back to CA CEM and on the Recording Session page sees that the JSP definition of new transaction, which is GreatBankOnline/acc_details.jsp, is now listed at the bottom of the page. Chris has the information needed, so clicks Stop to end the recording session.
54 Overview Guide
Introscope Scenarios
Chris promotes or adds the Check Account details business transaction to the GreatBankAccountCheckService. Chris then renames the business transaction as "Check Account" for easy visibility and then enables it. Now that the Check Account business transaction is enabled and properly defined, Chris synchronizes the monitors to send this business transaction to all the agents for monitoring. Now whenever a Great Bank online bank customer performs a Great Bank web site transaction that hits the Check Account business transaction, the hit will be monitored and reported on separately. To test this out, Chris toggles back the Great Bank web site, then performs some web transactions that hit the Checking Account business transaction a couple of times. Chris then looks at the Workstation Investigator and scans the metric browser tab tree looking for the Business Segments node, which displays the newly-monitored higher level business information about business services. Chris finds the GreatBank node, under which sits the Check Account node. Here Chris finds the GreatBankOnline/acc_details.jsp transaction with its associated metrics. Chris notes that each web site hit had an Average Response Time of eight milliseconds, which will make Toni, the GreatBank application owner, happy. Chris gives this business transaction time information to Toni, who passes it along to Jason, the Great Bank web site application sponsor. Jason is glad to hear that the business transaction time is fast, but wants to know how long it takes to get the Check Account information to the web page end user. Chris knows that it will be easy to get this additional information using CA CEM once management approves the Great Bank application triage group to use TIMs to monitor the GreatBank web traffic.
Using the Application Triage Map to See What is Up and Running In CA APM out of the box, the Introscope Workstation has a Triage Map tab that displays the application triage map. Here Chris, the IT application support triager for Great Bank, sees how the Great Bank instrumented frontends and backends, such as databases, are related to each other, how they are communicating, and if there are any current problems. This allows Chris to easily know what is coming and going from all instrumented applications and answer "Is any specific application up and running and how is it performing?" The Great Bank CA APM Application Group deployed the Introscope agents that monitor the Great Bank web site application, which IT calls GreatBank. Chris knows that on the Triage Map tab the nodes under the By Frontend tree are automatically populated based on what the agents have found. Based on reading the documentation, Chris knows that Introscope has used cross-process Transaction Tracing to discover that the GreatBank application makes a SOA call to the GreatBank service.
Chapter 4: CA APM Product Scenarios 55
Introscope Scenarios
Chris confirms this on the triage map tree by clicking the GreatBank node under the By Frontend node, and then looks at the associated application triage map. As expected, Chris sees that Introscope is automatically displaying icons for the GreatBank application that calls the GreatBank service, as well as an arrow pointing from the application to the service. When Chris hovers the cursor over the intersection of the arrow and the GreatBank service, Introscope displays metrics showing how many times the GreatBank service was hit and how long the average business transaction took. This allows Chris to see the Introscope current 15-second time slice information about what is happening in the GreatBank application at that time. In the application triage map, what Chris sees is the aggregation of the JVMs that are processing the GreatBank application. Since Chris is looking at a map of the Great Bank production environment, there are over 100 clustered JVMs running the GreatBank application and running the GreatBank service. So it is the aggregation of the JVMs that makes up the Average Response Time showing Chris the health of the Great Bank application. Similarly, since 100 JVMs are running the GreatBank service, then Chris knows that the Responses per Interval metric is a value aggregated across the 100 clustered JVMs. Chris likes the ease of getting the aggregated information, because Chris is often asked to report IT application information such as this to both the GreatBank application owner and the Great Bank business owner. But Chris especially likes the application triage map for the primary job duty of a triager: first level triage. With the map, Chris can see if a mission-critical service is communicating with another service, and tell if the communication is struggling. Since Chris works with such important Great Bank monitoring, and can alert on items in the application triage map, Chris decides to set an alert on the GreatBank application Stall Count metric. Chris chooses a value of 7, because if the application stalls more often than that in a 15-second time slice, Chris knows the application is in trouble. Chris right clicks on the Stall Count node, creates the alert, adds it to a Management Module and makes the alert active. Now any time the GreatBank application stalls more than 7 times in a 15-second time slice, in the application triage map a new alert on the GreatBank application icon displays as red. Chris also puts a Stall Count alert on the GreatBank service. If this value goes above 5, the alert on the application triage map icon for GreatBank service turns red. Now in the triage map tree Chris sees the new alerts on both the map icons and the tree nodes for the GreatBank application and service. Chris knows that when red alerts show on both the GreatBank application and GreatBank service, it is time to do some root cause diagnostics to get more information.
56 Overview Guide
Introscope Scenarios
Earlier when testing the Introscope agent-only business transaction recording, Chris recorded the Check Account business transaction and added it to a new GreatBankAccountCheckService business service. In looking at the application triage map Business Service node, Chris sees at a glance how the GreatBankAccountCheckService business service and the Check Account business transaction actually flow within the Great Bank logical IT infrastructure. This includes information about their status and the status of the other frontends and backends they are communicating with right now. Chris knows that being able to visually assess the Great Bank Introscope Collector cluster using the application triage map is going to make life as a first level triager faster and little less stressful.
Dynamic Instrumentation: Adding, Removing, and Exporting Instrumentation Using the Transaction Tracer Tandav is an Application Support Specialist for Mastery Medical Corp. Tandav needs to triage the Master Physician application, which runs on WebLogic, and which keeps Mastery Medical the market leader. This means he needs to be able to view deep into workings of the Master Physician application and be able to view methods associated with the Master Physician application transactions. Using Introscope and CA Application Performance Management for SOA (CA APM for SOA), Tandav monitors the production Master Physician application and does emergency production investigation. In addition, Tandav is asked to rapidly test upcoming configuration changes in the pre-production Master Physician test application. While monitoring the Master Physician application, Tandav navigates to the Master Physician application icon on the Investigator application triage map. He can clearly see arrows showing that the Master Physician application talks to the WebLogic Medical Records application which in turns talks to the Physician Web Services application as well as a database. Tandav also notices that there is a Master Physician business service. Since the Medical Records application is slow, Tandav right clicks on its icon to see its health metrics. He reviews the Average Response Time aggregated across all the agents in the list of Application Locations. Tandav believes there might be a problem in one of the agents in the list, so double clicks on that agent name in the list. Introscope automatically jumps to the WebLogic agent in the Metric Browser tree and displays data about Medical Record application node. In the viewer pane, Tandav clicks the Traces tab and notes that there are not any Transaction Traces for this agent. He goes to the Workstation menu, chooses New Transaction Trace Session, selects parameters to trace any transaction that lasts longer than one second to catch everything across all agents, and then clicks OK. Tandav is now tracing the transactions that go through the Medical Records application.
Chapter 4: CA APM Product Scenarios 57
Introscope Scenarios
Watching the first Transaction Trace session, Tandav notices that a Physician business transaction is a cross-process call hitting a number of methods and classes, then going out to a SOA call. Tandav finds this interesting, and wants to get more information about an Invoke method, so clicks on the Transaction Trace band showing that call. When the View all Called Methods menu displays, Tandav sees the specific classes that call specific methods. He scrolls down the list of methods, chooses the Invoke method, and then clicks Add Instrumentation. He uses the same steps to instrument the Web Service Summary class within the JVM. When a new business transaction goes through the JVM, Tandav opens up the Transaction Trace, and now sees calls for the two new dynamically-instrumented classes and methods. He notes these are quite easy to see because the Invoke method and Web Summary class bands in the Transaction Trace are green. In addition, on the left side of the band there is a new icon that denotes temporary instrumentation status. This means that the instrumentation is temporarily loaded into the memory of the Java agent. Tandav knows that when he closes the Transaction Trace window, this temporary dynamic instrumentation goes away. Intrigued, Tandav further explores the new dynamic instrumentation functionality. He clicks on the Transaction Trace band for the temporary Invoke method and selects Add Temporary Instrumentation to All (instrumentable) Called Methods. As another business transaction goes through, Tandav sees one more new method, the Invoke from a Web Server stub object method. Introscope also allows Tandav to easily save newly-instrumented classes and methods as permanent instrumentation. Tandav clicks on the Transaction Trace band for the Invoke for a Web Server stub object method, and chooses "Make instrumentation permanent". Now when a Physician business transaction goes through, on the Transaction Trace Tandav sees the classes and methods that are still being found using temporary dynamic instrumentation as well as the permanently instrumented object. Tandav notes that the Invoke for a Web Server stub object method band in the Transaction Trace no longer displays the temporary instrumentation status icon. Tandav navigates to the metric browser tree, right clicks on the WebLogic Agent node, and then chooses "Change dynamic instrumentation level". Using this functionality, Tandav can turn on or off dynamic instrumentation for whole groups of methods and classes that he has created. From reading the CA Application Performance Management Java Agent Implementation Guide, Tandav knows that it is especially useful to enable and disable pre-defined groups in order to perform rapid diagnostics. Later, Tandav, who has been working in the pre-production environment, is ready to export the recent instrumentation changes by copying them to other agents in the Mastery Medical production environment. Tandav goes to metric browser tree and clicks the WebLogic Agent node. Tandav then right clicks and chooses Export All Instrumentation, knowing that he can also choose to export individual methods and classes. After Tandav clicks OK, Introscope creates a new ProbeBuilder Directive (PBD) file that tells the agents exactly what to monitor in specific JVMs.
58 Overview Guide
CA CEM Scenarios
Tandav saves to his desktop the new PBD, and then opens the file to review the changes before putting the PBD into production. Tandav remarks to his colleague, Jane, that using the Introscope dynamic instrumentation, he has not needed to restart a monitored application once. Now he will be even faster at triaging the Master Physician application.
CA CEM Scenarios Kim is the CA APM administrator for Great Bank Inc. and is reviewing the CA CEM capabilities. First Kim notes that only one login is needed for both CA CEM and Introscope because of the single sign-on functionality. Kim recalls that other CA APM security-related changes that have also made a real difference: Great Bank has just deployed CA Embedded Entitlements Manager (CA EEM). Through CA EEM, Great Bank can take advantage of CA CEM business service based security. After reviewing the security changes, Kim wants to test out the automatic transaction discovery capability, which will record the Great Bank actual web site user experience for specific mission-critical transactions that Kim chooses. After that, Kim needs to set up a CA CEM transaction query in Japanese on the term "bad transaction" using the CA CEM capability for monitoring web applications in multibyte languages. ■
CA EEM and business service based security provide flexible permissions across the organization (see page 59)
■
CA CEM automatic transaction discovery speeds monitoring from test to production environments (see page 61)
■
Monitoring defects in multibyte applications (see page 62)
CA EEM and Business Service-Based Security Provide Flexible Permissions Kim appreciates the CA CEM business service based security, which permits specific CA APM users to view data about specific bank business areas. CA CEM monitors the Great Bank web site, which is international in scope. Another CA APM capability is the ability to secure permissions (access policies) based on its integration with CA EEM. Great Bank has deployed CA EEM for CA APM authentication and authorization, and Kim is also the CA EEM Administrator. Within CA EEM Kim can set up and look at the bank personnel who use CA APM—both individual users as well as the security groups that contain the individuals—and is able to control permissions to pages, tabs, and data for everyone.
Chapter 4: CA APM Product Scenarios 59
CA CEM Scenarios
CA CEM does not need to know what generates the Great Bank web site activity or where the activity comes from. For example, the web user activity could be coming from single or multiple business units such as consumer banking, commercial banking, private banking, and investment banking. Each of these business units has its own activity that comes across as internet web services from the Great Bank web site. The business unit IT owners care that their businesses are running well and that any IT problems are quickly repaired. However, the business unit IT owners want to share information about how their business unit IT services are doing with only the people in their business unit. With CA CEM business service based security and CA EEM, Kim can partition CA APM data according to business area. Great Bank has configured CA EEM so that each standard CA CEM user belongs to a defined security group. Great Bank has a large and high-revenue Great Bank Japan business unit. Kim has set up a GB_JPN security group and the associated access policies in CA EEM. Kim then configured the business services so that only CA CEMs users who are members of the GB_JPN group can see business services related to the related to Great Bank Japan business unit. Since Kim often uses CA CEM, Kim likes the fact that it is easy to view the access policies for business service in CA CEM as well. Kim clicks the Access Policies tab to view the access policies, which puts access control on all the business services that have been created, including the GreatBankAccountCheckService that Chris, the IT application support triager for Great Bank, recently created. Kim can also see all the security groups that have been created that could be associated with an access policy for any given business service. Kim confirms that the GB_JPN group security group can access data about GreatBankAccountCheckService. Kim has been asked to confirm that a new employee, Carla Meredith, has access to the Great Bank Japan CA CEM data. Kim logs into CA EEM, where Kim periodically updates CA CEM user permissions. Kim looks at all the users who have been defined in CA EEM and finds Carla Meredith. Kim confirms Carla is part of the GB_JPN security group, as well as a security group named "Guest". Kim can change permissions, which are additive, so that any group that Carla is added to increases the CA CEM information Carla sees about Great Bank business units and applications. For example, if Carla is added to the Administrator group, she can see what Kim and the other CA APM Administrators see in CA CEM. But because Carla works within the Great Bank Japan business unit and has been granted the GB_JPN and Guest security group permissions, she only sees the CA CEM Great Bank Japan information well as specific higher level data that the Guest security group uses for reporting purposes. Kim knows that based on the CA EEM permissions for Carla and CA CEM business service based security, when Carla logs into CA CEM, she can only see a limited number of links, tabs, and data in the CEM console. For example, Carla can only see the incidents related to the Great Bank Japan business service and the business transactions related to that service.
60 Overview Guide
CA CEM Scenarios
As the CA APM security owner, Kim reflects about the flexibility and control that CA EEM and business service based security provide. Then Kim remembers wanting to test the new CA CEM automatic discovery capability.
CA CEM Automatic Transaction Discovery Speeds Monitoring from Test to Production Environments Kim is looking forward to using the CA CEM automatic discovery capability to record business transactions, and then monitor them in production. This is important to Kim who uses CA CEM in two ways: for ongoing proactive monitoring and for making rapid updates when changes take place to the Great Bank applications being monitored by CA CEM. At Great Bank, Kim is a member of the application monitoring group, which is also part of the application deployment team. Part of the Great Bank application deployment process is making sure that the application monitoring is updated whenever any of the Great Bank applications are changed. So when the application deployment team pushes out changes to production, they also push out their monitoring tools including CA CEM. At the last firm Kim worked, which also used CA CEM, this process was not as easy. Kim remembers being a member of the monitoring team there as well. However, at the former firm the monitoring group was independent from the application deployment team. In this case, Kim as the CA CEM configuration administrator had to scramble when there were changes to an application being monitored. A member of the application deployment team would race over to Kim and say, "We have just deployed an app; can you get the monitoring up and running as soon as possible?" This added stress and frustration to Kim, who already had a difficult job. Back to thinking about application monitoring at Great Bank, Kim is looking forward to the speed of automatic transaction discovery because the Great Bank applications do change regularly. Making the associated CA CEM monitoring changes and recording those changes manually can become a time consuming for Kim. Kim has colleague named Rene who has already tried out automatic transaction discovery for another Great Bank application and given it a positive report. Kim reviews what Rene has done. Kim notes that Rene has already distributed the Enterprise Manager services and selected appropriate TIMs in their test environment. Kim creates a new template and adds some parameters, making sure that the business application is set to the one of interest and that the URL path filter uniquely identifies the web site and application that Kim is interested in today. Kim synchronizes all the TIM monitors. Now ready to try out this new CA CEM feature, Kim starts automatic transaction discovery.
Chapter 4: CA APM Product Scenarios 61
CA CEM Scenarios
Kim toggles to a new browser window and starts a new session on the Great Bank web site. Kim in this automatic transaction discovery process is only looking for new activity, that is, new transactions that CA CEM has not seen before. Kim wants to perform some web banking activities that would typically be performed by specific bank web users over time. Kim logs in, and continues to click around to mimic customers who need to transfer funds periodically. After checking some account details, Kim logs out of the Great Bank web site and toggles back to CA CEM. In the Automatic Transaction Discovery page, Kim clicks the Stop button to end this automatic transaction discovery session. Kim clicks through the Business Services: Discovered Transactions page and sees that there are seven newly discovered transactions captured around the time that Kim was clicking around the Great Bank web site. Kim views the details of a few of the new transactions, and then decides that it would be good to create a new business service as a container in which to monitor these transactions as a set. Kim creates a new business service called BankAutoDisc, and then moves a few of the newly discovered transactions into the business service. Then Kim navigates to the BankAutoDisc service, enables, reviews, and then syncs it. Now CA CEM is monitoring the newly discovered transactions Kim included in the BankAutodDisc business service.
Monitoring Defects in Multibyte Applications Because Great Bank has worldwide operations, Kim appreciates that now CA CEM can do transaction discovery, monitoring, and looking for defects in multibyte language applications like Chinese, Japanese, and Korean. CA CEM does these actions using multibyte characters that can monitor bank applications, such as the Great Bank web site, in operation. Kim looks at transaction data in CA CEM, when Great Bank transactions actually run, to see the details of the defects that come off the transactions. Kim can see content defects that are based on characters in the response body, including content in Japanese as well as content errors in Japanese. This allows Kim to look for response errors as well as transaction errors across multibyte applications. Today to support the Great Bank Japan business unit, Kim has been asked to set up CA CEM monitoring on "bad transaction" in Japanese transactions and transaction response headers. Kim has already set up the Internet Explorer browser on the PC to properly display Japanese font. Kim logs in to the CEM console and navigates to the Business Applications tab and opens the GreatBank2 application. There Kim selects Japanese character encoding for Microsoft Windows (Shift-JIS) for the GreatBank2 application, then clicks Save.
62 Overview Guide
CA Application Performance Management for SOA Scenario
Kim needs to record a new transaction using multibyte characters, and can do so because TIMs read the Content-Type header and tags during the recording process. After making sure the TIM is enabled on the Setup link Monitors page, Kim clicks the Administration link, Recording Sessions tab, to set up a new recording session. Kim sets the Monitor Type to TIMs and names the recording using the Japanese characters for "bad transaction". Kim sets the recording conditions including the same character encoding used for the GreatBank2 application—Shift-JIS. Kim starts the recording, and then toggles to a preset web page. There Kim performs some activities, including one that always results in the response of "bad transaction" in Japanese. Kim toggles back to CA CEM and stops the recording. Kim deletes all the recorded transactions except the transaction resulting in the "bad transaction" response, which is now a "bad transaction" transaction definition. Kim adds a new parameter of HTTP header to transaction definition, and then sets the transaction component so that a defect is created every time "bad response" appears in a transaction response header. Kim creates a new business service called BadTransactionResponse, and then promotes the "bad response" transaction into the BadTransactionResponse business service. Kim also associates the BadTransactionResponse business service with the GreatBank2 application, a required step because the GreatBank2 application is set specifically to Shift-JIS. Then Kim navigates to the BadTransactionResponse service, enables, reviews, and then syncs it. Kim now knows that CA CEM will find all transactions containing the Japanese equivalent of "bad transaction", even if the server provides a "200" response saying that the transaction was good. And if the transaction header contains "bad transaction", then CA CEM will create a defect. With the CA CEM deep monitoring of the Great Bank Japan web customers, Kim is confident that any web site transaction issues will be discovered 24 x 7.
CA Application Performance Management for SOA Scenario Forward Incorporated has implemented service oriented architecture (SOA) due to the increasing complexity of the web applications deployed at their firm. Forward is using SOA to increase their business process flexibility and facilitate expansion. Forward has converted their business applications to business services, which are available to both their end users and partners. Partners to Forward can add value to these business services and re-sell them. In order to monitor the performance of this complex environment, Forward has implemented CA Application Performance Management for SOA (CA APM for SOA).
Chapter 4: CA APM Product Scenarios 63
CA Application Performance Management for SOA Scenario
In addition, Forward has invested in TIBCO BusinessWorks (TBW), which allows their business to connect, mediate, and manage business processes dynamically. To monitor TBW performance, Forward has also installed the CA APM for SOA TBW agent and Enterprise Manager extensions. Jo, who is an Application Support Specialist, uses CA APM for SOA to monitor the Forward critical business services, including the Trade Broker business service that the Forward IT staff calls "TradeBroker". One day Jo receives an alert message from CA APM for SOA stating that the Average Response Time for the TradeBroker buy business service is exceeding its danger threshold. A second alert states that the TBW middleware that supports TradeBroker also has a danger status. Jo opens the CA APM for SOA console, and chooses the Forward custom TradeBroker Overview dashboard, which monitors all aspects of TradeBroker. All the alerts for the components supporting the buy business service are green except the TBW component, which is red. Red alerts mean that a CA APM for SOA TBW threshold level has been exceeded. Jo double-clicks the TBW alert to investigate further. The TBW Home dashboard opens and displays a red alert for the Business Processes Response Time. Jo now knows this business-critical metric has crossed the danger threshold. Wondering what could be causing the slowdown, Jo double-clicks the Business Processes Response Time red alert. This brings up the TBW Business Processes Overview dashboard. In quickly scanning the dashboard, Jo notices the 10 Slowest Business Processes bar chart. Jo sees that the Average Response Time for the Route to Trade business process is red and has increased significantly. Jo double-clicks the Route to Trade business process to drill down and investigate the root cause. This opens the Investigator tree and shows data about the business process components that comprise the business process. Jo clicks the Route to Trade business process node in the Investigator tree. The Overview tab displays graphs for the Introscope metrics for this business process, including Average Response Time and Responses Per Interval. Additionally Jo can also view the activities and tasks that make up the business process. Jo clicks on the SOA Dependency Map to check the dependencies for the Route to Trade business process. On the SOA Dependency Map, Jo can clearly see the web services that the business process is calling. The SOA Dependency Map also overlays run time performance metrics on top of each map node, allowing Jo to easily see how the business process components work in real time and where each transaction is spending time. The SOA Dependency Map also presents different levels of view based on the required visibility. To triage further, Jo clicks the Traces tab, which opens in the Summary View. Jo sees that the TBW business process transaction has traversed multiple layers of the Forward SOA environment. CA APM for SOA has correlated this TBW transaction as it moved from service to service and component to component. Jo can clearly see the TBW cross-tier tracing: this call goes from the TIBCO web service client to the TBW business process to a backend web service residing on an application server.
64 Overview Guide
CA Application Performance Management for SOA Scenario
Jo switches to Sequence view, which shows the order of processing segments for a business process transaction and response times of each segment. Segments are the process execution steps that make up a transaction. In TIBCO BusinessWorks, these segments are the activities and tasks you use to define the business process. In a Transaction Trace, the Sequence View displays all the segments of the business process showing the chain of execution. The Sequence View is an optimized Transaction Trace view specifically for SOA transactions, which tend to be asynchronous or multi-threaded. By looking at this Transaction Trace, Jo confirms that the majority of the transaction time has been taken up by one of the activities that form the Route to Trade Business Process. Jo opens a high-priority ticket in the Forward Service Desk. By including the details discovered using CA APM for SOA, Jo is confident that the Middleware Services group can quickly fix this problem.
Chapter 4: CA APM Product Scenarios 65
Appendix A: CA APM Guides and Help System For information about accessing CA APM documentation and the books included in the CA APM documentation set, see Product Documentation. This section contains the following topics: The CA Support Online Knowledge Base (see page 67) Additional CA APM Product and Information Resources (see page 69)
The CA Support Online Knowledge Base The CA Support Online Knowledge Base has the most up-to-date information for using CA Introscope® and related products. The CA Support Online Knowledge Base contains troubleshooting information, articles on common issues, and white papers on a range of CA APM, CA Introscope®, and CA CEM subjects.
Accessing the Knowledge Base To access the CA Support Online Knowledge Base, you need a username and password. Contact CA Support for more information about obtaining a Knowledge Base username and password. You can access the CA Support Online Knowledge Base here: http://support.ca.com.
Searching and Browsing Knowledge Base Articles You can search the Knowledge Base for answers to questions about specific CA APM products, or you can browse through different articles. Appendix A: CA APM Guides and Help System 67
The CA Support Online Knowledge Base
Most Popular Knowledge Base Articles Here are examples of some of the top most popularly searched Knowledge Base articles.
68 Overview Guide
■
CA APM Known Issues
■
Duplicated System level CPU,Memory,Disk metrics when using .Net agent
■
Official CA Wily Releases
■
APM Database installation error
■
Performance Tuning Guidelines for CEM
■
APM 9.0: CA Embedded Entitlements Manager (CA EEM) and CA Introscope® integration
■
Receiving the following ERROR "Failed to initialize event handler library" for a new Site Minder Manager installation
■
What operating systems are supported for APM 9.0 PostgreSQL
■
Excel Integration toolkit not working
■
Fixing Corrupt Transaction Trace Database
■
How to disable the "Db is not reachable, will continue checking Connections could not be acquired from the underlying database!" WARN message
■
Hot-Deployable Settings for the Enterprise Manager
■
CEM Content Error Problems
■
Transaction Trace Correlation into CEM with a Defect via GUID
■
PATCH::7.0.P1::Agent, Enterprise Manager, and LeakHunter Issues
■
.Net Agent Installation Problems
■
List of All 91 Supported Probe Builder Directives
Additional CA APM Product and Information Resources
Additional CA APM Product and Information Resources In addition to CA APM documentation, as a customer you can access or find out about these information sources: ■
CA APM Community site (see page 69)
■
CA Education services (see page 69)
■
CA Professional Services (see page 70)
■
CA Support (see page 70)
■
CA APM Customer Forum
CA APM Community Site You can join the CA APM Global User Community, where users of CA APM can collaborate and network with other users.
CA Education Services CA Education provides courses that are designed to transfer CA APM application performance management expertise directly to your staff, allowing your organization to become best-in-class in performance and availability management. To access this resource: ■
U.S.: go to http://www.ca.com/us/it-training-education.aspx.
■
Call U.S.: 1-800-237-9273.
■
International: go to http://www.ca.com/education/content.aspx?cid=224425
Appendix A: CA APM Guides and Help System 69
Additional CA APM Product and Information Resources
CA Professional Services CA Professional Services can help you with: ■
Accelerating deployment through proven procedures and deep technology expertise.
■
Maximizing performance with proactive audit and analysis.
To access this resource: ■
go to: http://support.ca.com
■
call U.S.: 1-800-225-5224.
CA Support CA Support provides: ■
Telephone, email, or both support regarding the use and deployment of CA APM products
■
24x7 Support for critical incidents (production down)
■
Online Support Incident submittal and tracking
■
Access to the online CA Support Online Knowledge Base
If you have support questions about the following areas: ■
CA APM product integrations
■
CA APM products
■
Other CA Technologies products
To access this resource:
70 Overview Guide
■
Go to: http://support.ca.com
■
call U.S.: 1-800-225-5224.
Index A About CA APM • 15 Accessing the Knowledge Base • 67 Additional CA APM Product and Information Resources • 69 Additional Extensions Provided With Your License • 35 Agents • 19 APM Database • 21, 26 APM Status Console • 20
B Baselines Database • 21 Business Value • 42, 43, 44, 45, 46, 47, 49, 51
C CA APM Community Site • 69 CA APM Environment Options • 27 CA APM Guides and Help System • 67 CA APM Product Architecture • 39 CA APM Product Scenarios • 53 CA APM Scenario • 53 CA Application Performance Management for SOA • 39 CA Application Performance Management for SOA Scenario • 63 CA CEM and Web Transactions • 27 CA CEM Automatic Transaction Discovery Speeds Monitoring from Test to Production Environments • 61 CA CEM Components • 25 CA CEM Integration With CA CMDB • 49 CA CEM Integration With CA NSM • 50 CA CEM Integration With CA Service Desk • 51 CA CEM Integration With CA SiteMinder • 50 CA CEM Integration With Other CA Technologies Products • 49 CA CEM Scenarios • 59 CA Education Services • 69 CA EEM and Business Service-Based Security Provide Flexible Permissions • 59 CA Introscope® Alerts and Reports Output • 22 CA Introscope® and CA CEM • 13 CA Introscope® Components • 18
CA Introscope® Integration With CA Cloud Monitor • 48 CA Introscope® Integration With CA CMDB • 42 CA Introscope® Integration With CA eHealth • 45 CA Introscope® Integration With CA Insight Database Performance Monitor (DPM) • 47 CA Introscope® Integration With CA NSM • 46 CA Introscope® Integration With CA Performance Center • 48 CA Introscope® Integration With CA SOI • 41 CA Introscope® Integration With CA Spectrum Infrastructure Manager • 43 CA Introscope® Integration With Other CA Technologies Products • 41 CA Introscope®-Only Environment • 34 CA Professional Services • 70 CA SOI Integration Features • 42 CA Support • 70 CA Technologies Product References • 3 CEM Console • 26 Clustered Environment • 29 Console • 19 Contact CA Technologies • 5
D Dynamic Instrumentation Adding, Removing, and Exporting Instrumentation Using the Transaction Tracer • 57
E eHealth Integration Features • 45 Enterprise Manager • 18, 25
H How CA Introscope® Monitors Java and .NET Applications • 22
I Infrastructure Aware Application Triage Environment • 31 Integrating With Other CA Technologies Products • 41 Integration Features • 43, 44, 46, 47, 49, 50, 51
Index 71
Introducing CA Application Performance Management • 11 Introscope Scenarios • 53 Investigator • 20
M Monitoring Defects in Multibyte Applications • 62 Most Popular Knowledge Base Articles • 68 Multiple-Cluster Environment • 30
R Recording an Agent-Only Banking Business Transaction to Monitor Customer Transaction Times • 54
S Searching and Browsing Knowledge Base Articles • 67 SmartStor • 21 Standalone Environment • 28
T The CA Support Online Knowledge Base • 67 TIM • 26 Transaction Events Database • 22
U Understanding the CA APM Environment • 15 Unified End-User Experience Monitoring Environment • 33 Using the Application Triage Map to See What is Up and Running • 55
W WebView • 21 Welcome to CA Technologies Application Performance Management • 11 What Does CA CEM Do? • 24 What Does CA Introscope® Do? • 16 What is CA CEM? • 24 What is CA Introscope®? • 16 Workstation • 19
72 Overview Guide
