ca application performance management performance center 2 3 00-linux... · ca application...

Integration for CA Infrastructure Management Guide

Release 9.5

CA Application Performance Management

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

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

CA Technologies Product References

This document references the following CA Technologies products and features:

■ CA Application Performance Management (CA APM)

■ CA Application Performance Management ChangeDetector (CA APM ChangeDetector)

■ CA Application Performance Management ErrorDetector (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 (CA APM for IBM WebSphere Application Server)

■ CA Application Performance Management for IBM WebSphere Distributed Environments (CA APM for IBM WebSphere Distributed Environments)

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

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

■ CA Application Performance Management for IBM WebSphere Process Server (CA APM for IBM WebSphere Process Server)

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

■ CA Application Performance Management for Microsoft SharePoint (CA APM for Microsoft SharePoint)

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

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

■ CA Application Performance Management for Oracle WebLogic Portal (CA APM for Oracle WebLogic Portal)

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

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

■ CA Application Performance Management for TIBCO BusinessWorks (CA APM for TIBCO BusinessWorks)

■ CA Application Performance Management for TIBCO Enterprise Message Service (CA APM for TIBCO Enterprise Message Service)

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

■ CA Application Performance Management for webMethods Broker (CA APM for webMethods Broker)

■ CA Application Performance Management for webMethods Integration Server (CA APM for webMethods Integration Server)

■ CA Application Performance Management Integration for CA CMDB (CA APM Integration for CA CMDB)

■ CA Application Performance Management Integration for CA NSM (CA APM Integration for CA NSM)

■ CA Application Performance Management LeakHunter (CA APM LeakHunter)

■ CA Application Performance Management Transaction Generator (CA APM TG)

■ CA Cross-Enterprise Application Performance Management

■ CA Customer Experience Manager (CA CEM)

■ CA Embedded Entitlements Manager (CA EEM)

■ CA eHealth® Performance Manager (CA eHealth)

■ CA Insight™ Database Performance Monitor for DB2 for z/OS®

■ CA Introscope®

■ CA SiteMinder®

■ CA Spectrum® Infrastructure Manager (CA Spectrum)

■ CA SYSVIEW® Performance Management (CA SYSVIEW)

Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ CA Support policies and guidelines

■ Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected].

To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

http://www.ca.com/support

mailto:[email protected]

http://www.ca.com/docs

http://www.ca.com/docs

Contents 7

Contents

Chapter 1: Introduction 11

Unified End-User Experience Monitoring................................................................................................................... 11

Solution Architecture ................................................................................................................................................. 12

Deployment Considerations ....................................................................................................................................... 14

Port Considerations .................................................................................................................................................... 15

Single Sign-On ............................................................................................................................................................ 16

CA SiteMinder Support ............................................................................................................................................... 16

More Information ....................................................................................................................................................... 17

Chapter 2: Component Overview 19

Multi-Port Monitor ..................................................................................................................................................... 19

Data Flow in the Converged Appliance ............................................................................................................... 20

Application Delivery Analysis Manager ...................................................................................................................... 20

NetQoS Performance Center/CA Performance Center .............................................................................................. 21

TIM ............................................................................................................................................................................. 21

Enterprise Manager.................................................................................................................................................... 22

APM Database ............................................................................................................................................................ 23

CEM Console .............................................................................................................................................................. 24

Workstation ................................................................................................................................................................ 24

WebView .................................................................................................................................................................... 25

Java Agent .................................................................................................................................................................. 26

.NET Agent .................................................................................................................................................................. 26

Chapter 3: Integration Scenarios 27

How to Connect CA APM to Multi-Port Monitor ........................................................................................................ 27

Prerequisites ....................................................................................................................................................... 30

TIM on the Multi-Port Monitor ........................................................................................................................... 30

Standalone TIM Options ..................................................................................................................................... 31

Install TIM on the Multi-Port Monitor ................................................................................................................ 32

Configure Hardware Filters ................................................................................................................................. 33

Configure TIM Monitoring on Logical Port .......................................................................................................... 36

TIM in Multi-Process Mode ................................................................................................................................. 37

Configure TIM for Multi-Process Mode .............................................................................................................. 39

Associate TIM with an Enterprise Manager ........................................................................................................ 41

(Optional) Configure Web Server Filters ............................................................................................................. 42

Synchronize Monitors ......................................................................................................................................... 44

8 Integration for CA Infrastructure Management Guide

Verify the Connection ......................................................................................................................................... 44

How to Connect CA APM to Application Delivery Analysis ........................................................................................ 45

Prerequisites ....................................................................................................................................................... 46

Run the Installer Program ................................................................................................................................... 46

Start the ADA-APM Service ................................................................................................................................. 49

Synchronize Time ................................................................................................................................................ 49


How to Connect CA APM to CA Performance Center ................................................................................................ 51

Prerequisites ....................................................................................................................................................... 53


Start the APM-CAPC Service................................................................................................................................ 55

Configure Alerts on APM WebView .................................................................................................................... 55

Import the APM Views into CA Performance Center .......................................................................................... 56

Register APM as a Data Source ........................................................................................................................... 57

Add the APM Menu Items to Application Health ................................................................................................ 58

Enable HTTPS Support (Optional) ....................................................................................................................... 59


How to Connect CA APM to NetQoS Performance Center ........................................................................................ 60

Prerequisites ....................................................................................................................................................... 62


Start the APM-CAPC Service................................................................................................................................ 64

Configure Alerts on APM WebView .................................................................................................................... 64

Update the CA Performance Center Database ................................................................................................... 65

Register CA APM as a Data Source ...................................................................................................................... 66

Enable HTTPS Support (Optional) ....................................................................................................................... 67


Chapter 4: Triaging Scenarios 71

How to Triage Application and Infrastructure Issues Starting from CEM Console ..................................................... 71

Determine your Triaging Options ........................................................................................................................ 72

Continue Triaging from Multi-Port Monitor ....................................................................................................... 76

Continue Triaging from APM WebView .............................................................................................................. 77

How to Triage Application and Infrastructure Issues Starting from APM WebView .................................................. 77



Continue Triaging from NPC/CAPC ..................................................................................................................... 85

Network Data Time Lag ....................................................................................................................................... 85

Tool Tip Data ....................................................................................................................................................... 86

How ADA Calculates Network and Server Health ............................................................................................... 86

How to Triage Application Issues Starting from NPC ................................................................................................. 87


Contents 9


Continue Triaging from NPC/CAPC ..................................................................................................................... 98

Appendix A: Troubleshooting 99

CA APM Application Data Not Available on NPC ........................................................................................................ 99

CA APM Application Data Not Available on CAPC .................................................................................................... 100

TIM Stops Working ................................................................................................................................................... 100

Infrastructure Data not Available on CEM Console .................................................................................................. 103

More Information Buttons on Workstation Do Not Work ....................................................................................... 103


Chapter 1: Introduction

This section contains the following topics:

Unified End-User Experience Monitoring (see page 11) Solution Architecture (see page 12) Deployment Considerations (see page 14) Port Considerations (see page 15) Single Sign-On (see page 16) CA SiteMinder Support (see page 16) More Information (see page 17)

Unified End-User Experience Monitoring

Unified End-User Experience Monitoring is the integration between CA APM and CA Infrastructure Management. The integration provides visibility into application level data that is related to application usage for an end user. The components that you choose to integrate determines what information is available on the various consoles and user interfaces.

The integration options are:

CA APM to Multi-Port Monitor

This integration allows you to view high-level network performance information on the CEM console. See How to Connect CA APM to Multi-Port Monitor (see page 27) for more information.

CA APM to CA Performance Center/CA Performance Center

This integration allows you to view CA APM application data on the CA Performance Center. See How to Connect CA APM to CA Performance Center (see page 60) or How to Connect CA APM to CA Performance Center (see page 51) for more information.

CA APM to CA Application Delivery Analysis

This integration allows you to view infrastructure data on APM WebView. See How to Connect CA APM to CA Application Delivery Analysis (see page 45) for more information.

Solution Architecture



The Unified End-User Experience Monitoring solution provides many deployment options, depending on the size and complexity of your network. This section outlines two possible scenarios.

In smaller environments where a single Multi-Port Monitor is sufficient, your deployment architecture may look similar to the following diagram.

Figure 1: Deployment architecture with a single multi-port monitor.

In more complex environments where multiple Multi-Port Monitors are required, you can scale up to:

■ Ten Enterprise Manager Collectors

■ Five Multi-Port Monitors

■ Five standalone TIMs

■ Three ADA Managers, 200 Java or .Net agents



More complex environments typically require a clustered CA APM environment with multiple Multi-Port Monitors. In a clustered CA APM environment, multiple Enterprise Managers (called Collectors when clustered) collect all agent metrics. You can subscribe to metrics from all the Enterprise Manager Collectors and the Manager of Managers (MOM) Enterprise Manager. In addition, the MOM manages cluster functions. For example, the MOM handles all Workstation requests for data and gathers those requests from the collectors. Your deployment architecture may look similar to the following diagram.

Figure 2: Clustered deployment architecture.

Deployment Considerations


Deployment Considerations

Before you install or upgrade, carefully plan your deployment. The following list outlines some important steps to consider:

■ Evaluate your existing environment and determine how and where you plan to deploy the necessary components.

■ Identify the characteristics of the environment you want monitored.

■ Understand and consider your SPAN or mirror port options for the converged appliance. The Multi-Port Monitor must be connected, via a SPAN or mirror port, to the key switches carrying application traffic to your network.

Note: For more information on mirror port in relation to the converged appliance, see the CA Multi-Port Monitor User Guide.

■ Understand and consider your mirror port options for the standalone TIM. A standalone TIM must be connected to a mirrored port or a network tap. This configuration ensures that TIM can monitor your network traffic without interfering with your data transmission.

Note: For more information on mirrored ports and network taps in relation to the standalone TIM, see the CA APM Configuration and Administration Guide.

■ Gather server IP addresses and application port numbers. The IP addresses and application ports you want monitored in your enterprise network are needed to configure the switch SPAN or mirror sessions.

■ Consider any firewalls that could prevent communications between the collector appliance and ADA Manager.

Note: For the ports and protocols used by Multi-Port Monitor, see the CA Multi-Port Monitor User Guide.

■ Review the CA APM Installation and Upgrade Guide to understand the requirements for the following CA APM components:

– APM database

– Enterprise Manager

– CEM console

– Workstation

– Stand-alone TIM

■ Review the CA APM .NET Agent Implementation Guide for .NET agent installation requirements.

■ Review the CA APM Java Agent Implementation Guide for Java agent installation requirements.

Port Considerations


Port Considerations

CA APM and CA Infrastructure Management components require certain ports through which communication takes place. The following diagram shows these components and ports.

Port 5001

Port 5001

Port 5001

Port 5432

Port 5432

Port 80

Port 8081

Port 5001

Port 5432

Port 5250

Port 8080

Port 80

Port 80

CEM Console

Introscope Workstation

Introscope WebView

EEM

MOM

Collector

Collector

APM database

Ports in use:8050015250 (EEM)54325443 (if HTTPS –

where 5001 is used)80808081

Agent

Port 8080Port 80

Port 8080

Port 80

Port 80

Port 80

Application Delivery Analysis (ADA)

NetQoS Performance

CenterMulti-Port Collector

NOTE: The port directions indicate the initiation of conversation only,

not the traffic flow. A uni-directional port may have data

passing in both directions.

Note: When TIM is installed on Multi-Port Monitor, it communicates with the MOM Enterprise Manager through Multi-Port Monitor on port 80. Port 8080 is used by MOM Enterprise Manager to communicate with Multi-Port Monitor.

Single Sign-On


Single Sign-On

Single Sign-On is the authentication scheme used by CA Performance Center (NPC)/CA Performance Center (CAPC) and all supported data sources. After users are authenticated to NPC/CAPC, they can navigate among the consoles and registered data sources without signing in a second time.

By enabling navigation among separate product interfaces, Single Sign-On provides a seamless drill-down experience for operators. For example, the first time you navigate from CEM console to TIM, you are required to sign on using credentials configured on ADA or NPC/CAPC (if ADA is bound to a NPC/CAPC). After the initial sign-on, you are not required to log on again when navigating between the two components.

Note: Single Sign-On is not supported with CA APM Workstation or WebView. You must sign on using the CA APM Workstation/WebView credentials each time you navigate to it.

NPC/CAPC uses a distributed architecture. An instance of the Single Sign-On web site is automatically installed on every server where a supported data source or NPC/CAPC is installed. If two data source products are installed on the same server, they use the same instance of the Single Sign-On web site. The distributed architecture lets users log in to individual CA data source products by logging in to the servers where these products are running.

Note: For more information about Single Sign-On, see the CA Performance Center Administrator and User Guide.

CA SiteMinder Support

If you have SiteMinder installed on your application servers, then configure TIM to allow for transaction monitoring. If TIM is not configured properly, it will ignore all transactions originating from those application servers.

Note: For more information on configuring TIM for transaction monitoring with SiteMinder, see the CA APM Configuration and Administration Guide.

More Information


More Information

You can refer to the following documentation and resources:

■ CA APM Installation and Upgrade Guide

Intended for the deployment team and system administrators. This guide provides installation and upgrade information for the following components:

■ APM database

■ Enterprise Manager/MOM

■ Workstation

■ Stand-alone TIMs

■ CA APM Configuration and Administration Guide

Intended for system administrators. This guide provides configuration and administration information (minus defining application transaction content) for the following components:

■ APM database

■ Enterprise Manager/MOM

■ Workstation

■ Stand-alone TIMs

■ CA APM Transaction Definition Guide

Intended for system administrators. This guide covers information related to establishing and maintaining business applications, business services, and transaction definitions.

■ CA APM Java Agent Implementation Guide

Intended for system administrators. This guide covers information related to installing and configuring Java agents.

■ CA APM .NET User Guide

Intended for system administrators. This guide covers information related to installing and configuring .NET agents.

■ CA APM Workstation User Guide

Intended for system administrators and system analysts. This guide covers information related to using the Workstation to triage your application.

■ CA APM WebView scenarios

Task oriented scenarios intended for system administrators and system analysts. These scenarios cover information on using the WebView to triage your applications.

More Information


■ CA APM Sizing and Performance Guide

Intended for system administrators. This guide covers information related to hardware sizing and system performance based on your sizing decisions.

■ CA Multi-Port Monitor Installation Guide

Intended for system administrators. This guide covers information related to installing the Multi-Port Monitor software.

■ CA Multi-Port MonitorUpgrade Guide

Intended for system administrators. This guide covers information related to upgrading the Multi-Port Monitor software.

■ CA Multi-Port Monitor User Guide

Intended for system administrators and analysts. This guide covers information related to configuring, administering, and using the Multi-Port Monitor.

■ CA CA Performance Center Installation Guide

Intended for system administrators. This guide covers information related to installing the NPC/CAPC software.

■ CA CA Performance Center Administrator and User Guide

Intended for system administrators and analysts. This guide covers information related to administering and using the NPC/CAPC.

■ CA Application Delivery Analysis Installation Guide

Intended for system administrators. This guide covers information related to installing the CA Application Delivery Analysis software.

■ CA Application Delivery Analysis Administrator Guide

Intended for system administrators. This guide covers information related to configuring and administering CA Application Delivery Analysis.

■ CA Application Delivery Analysis User Guide

Intended for analysts. This guide covers information related to using the CA Application Delivery Analysis user interface.


Chapter 2: Component Overview


Multi-Port Monitor (see page 19) Application Delivery Analysis Manager (see page 20) NetQoS Performance Center/CA Performance Center (see page 21) TIM (see page 21) Enterprise Manager (see page 22) APM Database (see page 23) CEM Console (see page 24) Workstation (see page 24) WebView (see page 25) Java Agent (see page 26) .NET Agent (see page 26)

Multi-Port Monitor Multi-Port Monitor is a hardware appliance which includes the following:

■ High-performance capture card

■ 4-disk RAID array used for the system and database

■ 12-disk RAID array used to store packets Multi-Port Monitor is a high capacity collector that groups multiple packet collections into one appliance. Multi-Port Monitor includes both hardware and software components. The hardware component is a 16 disk server that captures and processes traffic flowing into and out of a switch. The software component is an administrative web interface that allows you to perform maintenance tasks, check the status of collection on the device, and build custom views.

When TIM is running on the Multi-Port Monitor, the appliance is sometimes called a converged appliance to differentiate it from Multi-Port Monitor without TIM. The converged appliance supports both ADA and TIM to perform non-intrusive, passive monitoring of networks, servers, and applications. It is now a collector appliance for both CA APM and ADA. The converged appliance connects to your switches, collects SPAN traffic, and sends that information to TIM and ADA. These two engines then send the information to their respective consoles, CEM console and ADA Manager.

Application Delivery Analysis Manager


Important! For the Multi-Port Monitor (without TIM installed), you can SPAN from different points on the network, each into its own logical port on the Multi-Port Monitor. For the converged appliance, you must choose one logical port for TIM and SPAN the web traffic from the WAN to it. This traffic is processed for TIM as well as ADA. Use the other logical ports for other SPANs, ideally from the access-layer switches closest to the servers. The non-TIM logical ports are processed for ADA only.

Note: See the Multi-Port Monitor User Guide and Multi-Port Monitor Installation Guide for more information on the appliance.

Data Flow in the Converged Appliance

This diagram shows the flow of packets, session data, network data, and TIM defects within the Multi-Port Monitor converged appliance. Notice that the converged appliance has two RAM disks. One disk is dedicated to storing TCP packets for ADA processing. The second disk is dedicated to storing HTTP data for TIM processing.

Application Delivery Analysis Manager ADA is a passive packet collector with a physical server and web-based user interface called the ADA Manager. ADA performs the following functions:

NetQoS Performance Center/CA Performance Center


■ Looks at TCP data and focuses on network-level metrics at the session level

■ Pulls collection files from collection devices and imports them into the database

■ Classifies data (by evaluating against threshold) into normal, degraded, or excessive and stores the result

■ Maintains incident list and observation counts

■ Calculates performance metrics at 5 minute intervals and sends them to the ADA Manager

■ Defines and associate servers, networks, and applications and pushes the configuration information to the collection device

■ Displays collected and processed data on report pages and views

NetQoS Performance Center/CA Performance Center

CA CA Performance Center (NPC)/CA Performance Center (CAPC) is a web-based reporting interface that displays performance data from products in the CA Performance Center suite, CA APM, and supported third-party products. NPC/CAPC reports provide views of performance and device data in various formats to help you effectively manage your networks, applications, and devices.

When you integrate CA APM with NPC/CAPC, the following application-related information is available on NPC/CAPC:

■ List of applications, business services, and business transactions monitored by CA APM and their health statuses in a selected time range

■ Trend of all the applications, business transactions component (BTC) metrics, and customer experience metrics (shown as RTTM on the CA APM user interface) for the selected time range

■ Details of incidents/defects for the selected business transaction

■ Link to the specific client subnet and server associated with a defect for further investigation into the infrastructure

TIM

The TIM records and observes HTTP and HTTPS packets on SPAN ports, identifies user logins and the related transactions, and monitors and reports defects and other statistics. TIM calculates all these metrics and sends them to the CEM console.

Enterprise Manager


Two instances of TIM are available, standalone TIM and TIM installed on the Multi-Port Monitor. Both instances monitor SPAN data and collect metrics on web-based transactions. When TIM is installed on the Multi-Port Monitor, the converged appliance provides visibility into application usage at the application and infrastructure data level. The following table outlines key differences between the two TIMs.

TIM on the Multi-Port Monitor Standalone TIM

Runs on 64-bit CentOS Linux 5.5 Runs on 64-bit Red Hat Linux 5.5

Runs in multi-process mode to increase throughput Runs in single-process mode

Reads packets from files written by the Multi-Port Monitor capture layer

Reads packets directly from the NIC

Time is derived from the packet timestamps. The Napatech card (using the Napatech clock) time-stamps packets as they enter the Multi-Port Monitor.

Time is derived from the system time (wall clock)

Napatech or network card not required because the Multi-Port Monitor has its own Napatech card installed.

Requires purchase of a Napatech or network card.

Uses the following default log-on credentials:

User name: nqadmin

Password: nq


User name: cemadmin

Password: quality

Enterprise Manager

The Enterprise Manager runs services that are distributed across different Collectors. Some of these services are TIM Collection, Stats Aggregation and Database Cleanup. When deployed with a single Enterprise Manager, it is called a standalone environment. When deployed with multiple Enterprise Managers, it is called a clustered environment where one Enterprise Manager is the MOM. Enterprise Manager clustering allows the MOM to manage other Enterprise Managers. Each of the managed Enterprise Managers, called Collectors, collects agent metrics and in turn, relays those metrics to the MOM.

Enterprise Managers can be deployed in different ways depending on the size and complexity of the enterprise system. The roles of specific Enterprise Managers depend on how they are deployed in standalone or clustered CA APM environments.

Enterprise Managers/MOMs are configured using the CEM console and text files. Some data processed by Enterprise Managers/MOMs are viewable from the CEM console and others are viewable from the CA APM Workstation/WebView.

APM Database


For more information about the CEM console, see

CEM Console (see page 24)

For more information on CA APM Workstation, see

Workstation (see page 24)

APM Database

You have the option between PostgreSQL or Oracle for your APM database platform. Several factors can influence your database platform choice. For example, the PostgreSQL database is easy to install and requires minimal configuration and ongoing management. The PostgreSQL database can also be installed automatically from the Enterprise Manager installer. This database typically does not require a separate database administrator to install or maintain data integrity and control user access. However, the PostgreSQL database does have some limitations that make it unsuitable for some deployment scenarios or organizations.

In general, consider the following factors when deciding between PostgreSQL or Oracle as your database platform. These factors can also influence your planned migration from PostgreSQL to Oracle for the APM database.

■ If you do not already have a database instance installed, you can use the Enterprise Manager installer to install PostgreSQL without any pre configurations.

■ If you want to minimize database maintenance and keep the configuration of your environment as simple as possible, using the PostgreSQL database provides an easier alternative to using an Oracle database.

■ If you are managing the APM database without the support of a database administrator group, the PostgreSQL database requires less management overhead, specialized knowledge and database-specific skills.

■ If your organization has standardized on a specific vendor's database, you may be required to use that database platform.

■ If you have existing database administrator resources and procedures in place for a specific database platform, you may be able to best leverage those resources by using that database platform.

■ If you do not have an existing database administrator, it may be more difficult for you to install, configure, and manage Oracle than a PostgreSQL database.

■ If your organization has complex database configuration requirements, you may need more advanced configuration and management options than PostgreSQL provides.

CEM Console


■ If you are monitoring a high-volume production environment, you may require a more robust and scalable database than PostgreSQL provides.

Note: For more information on the APM database, see the CA APM Installation and Upgrade Guide.

CEM Console The CEM console is a user interface used to:

■ record and define business transactions, which are then used to create transaction definitions

■ produce and view business transaction-related reports

■ view defect data and transaction definitions, group transactions into services and manage CA APM user access to Enterprise Manager data

Within the Unified End User Experience Monitoring solution, the roles and responsibilities of the CEM console do not change significantly, with the following exceptions:

■ Network health data is available from the Defect Details page

■ You can use the defect and network information to identify a potential performance issue and navigate directly to Multi-Port Monitor

The CEM console is installed as part of the Enterprise Manager installation.

Workstation

You use the Workstation to view metric data in different forms. Authorized users can perform administrative and configuration functions. The Workstation presents information in these windows:

Console

Shows data in dashboards, which contain Data Viewers.

Investigator

Presents tree views and map views of agents, applications, resources, and metrics.

Management Module Editor

Presents a tree view of Management Modules and elements, allowing you to create and edit Management Modules.

WebView


Dashboard Editor

Enables users with write permission for a Domain (or SuperDomain) to create and edit Data Viewers and other dashboard objects such as imported images, shapes, lines, and text.

Data Viewers

Visual presentation of data based on the type.

If you integrate CA APM with CA Application Delivery Analysis, then infrastructure health data is available on the Workstation Investigator and Console. Additionally, direct access to CA Performance Center is available from the Network Status Information dashboard.

Note: For more information about the Workstation, see the CA APM Workstation User Guide.

WebView

APM WebView is an alternative to the Workstation, but without the administrative functions. Use APM WebView to view metric data in different forms. APM WebView presents information in these windows:

Console

Shows data in dashboards, which contain Data Viewers.

Investigator

Presents tree views and map views of agents, applications, resources, and metrics.

Management

Presents a tree view of Management Modules and elements, allowing you to create and edit Management Modules.

If you integrate CA APM with CA Application Delivery Analysis, then infrastructure health data is available on the Investigator and Console. Additionally, direct access to NPC/CAPC is available from the Network Status Information dashboard.

Java Agent


Java Agent

The Java agent collects performance data from applications running on Java Virtual Machines (JVMs) and the application server. Java agent also collects performance and availability data from the surrounding computing environment. The Java agent uses probes in the application byte code to gather this data and sends it to the Enterprise Manager. The ProbeBuilder Directive (PBD) files control which data the probes monitor. You can change the PBD files to suit the monitoring needs of your environment. Several standard PBDs are included when you install the Java agent, as well as specific PBDs for your application server. Fine-tuning the tracers and directives in the PBD files delivers the metric information you want to monitor for your environment.

The Enterprise Manager processes and analyzes the data received from the Java agent. You can access this information from the CA APM Workstation. Using the Workstation, you can review the information and set up actions and alerts based on the data received.

Note: See the CA APM Java Agent Implementation Guide for more information.

.NET Agent

The .NET agent is an application management solution for Managed Enterprise .NET applications that provides visibility to the component level. The .NET agent monitors mission critical .NET applications running in the Microsoft Common Language Runtime (CLR) environment.

An agent collects application and environment metrics and relays them to the Enterprise Manager. An application that reports metrics to an Introscope agent is referred to as instrumented. After you install and configure the .NET agent on a system, the applications that run there are automatically instrumented at start-up.

By default, only IIS ASP.NET applications active on a system are instrumented. You can instrument any .NET application, including IIS ASP.NET applications as well as stand-alone .NET executables. You can also instrument only a sub-set of applications or specific applications.

The instrumentation process is performed using ProbeBuilding technology. This technology uses tracers, defined in ProbeBuilder Directive (PBD) files, to identify the metrics an agent gathers from applications and the CLR at runtime. The .NET agent then sends this metric information to the Enterprise Manager.

Note: See the CA APM .NET Agent Guide for more information.


Chapter 3: Integration Scenarios


How to Connect CA APM to Multi-Port Monitor (see page 27) How to Connect CA APM to Application Delivery Analysis (see page 45) How to Connect CA APM to CA Performance Center (see page 51) How to Connect CA APM to NetQoS Performance Center (see page 60)

How to Connect CA APM to Multi-Port Monitor

Connecting CA APM to Multi-Port Monitor allows you to view high-level network performance information related to the application being monitored. For the defect you are viewing, network data from the Multi-Port Monitor database is imported to the CEM console and saved in the APM database. This data is rendered in the CEM Defect Details page along with the defects generated by TIM. You can use the defect and network information to identify a potential performance issue and navigate directly to Multi-Port Monitor.

Note: There can be a short delay (approximately 4 to 5 minutes) between the time a defect is generated and when the network data is available on the CEM Defect Details page. For example, if a defect was generated 2 minutes ago and network health information on the CEM Defect Details page is unavailable, wait a few minutes and refresh the view. The delay is due to the periodic loading of the network data into the Multi-Port Monitor metrics database.



The following illustration describes how as an administrator you connect CA APM to Multi-Port Monitor.



As an administrator, perform the following steps:

1. Install TIM on the Multi-Port Monitor (see page 32).

2. Configure hardware filters (see page 33).

3. Configure TIM monitoring on logical port (see page 36).

4. Configure TIM for multi-process mode (see page 39).

5. Associate TIM with an Enterprise Manager (see page 41).

6. (Optional) Configure web server filters (see page 42).

7. Synchronize monitors (see page 44).

8. Verify the connection (see page 44).

Prerequisites

Before you begin, verify that you have installed and configured:

■ Multi-Port Monitor 2.2

■ APM database 9.1 or newer

■ Enterprise Manager 9.1 or newer

■ CA APM Workstation 9.1 or newer

■ CA APM WebView (optional)

■ One of the following:

– CA APM .NET agent 9.0 or newer

– CA APM Java agent 9.0 or newer

TIM on the Multi-Port Monitor

TIM lets System Administrators configure Multi-Port Monitor appliances to function as converged appliances. The converged appliance lets you collect TCP and HTTP data and passes these packets to TIM and CA Application Delivery Analysis (if you have this product in your environment). The Multi-Port Monitor converged appliance provides visibility into application and infrastructure performance metrics related to application usage by end-users.



Important! For the Multi-Port Monitor (without TIM installed), you can SPAN from different points on the network, each into its own logical port on the Multi-Port Monitor. For the converged appliance, you must choose one logical port for TIM and SPAN the web traffic from the WAN to it. This traffic is processed for TIM as well as ADA. Use the other logical ports for other SPANs, ideally from the access-layer switches closest to the servers. The non-TIM logical ports are processed for ADA only.

The following table identifies the differences between TIM installed on the Multi-Port Monitor and standalone TIM.

TIM on the Multi-Port Monitor Standalone TIM

Runs on 64-bit CentOS Linux 5.5 Runs on 64-bit Red Hat Linux 5.5

Runs in multi-process mode to increase throughput Runs in single-process mode

Reads packets from files written by the Multi-Port Monitor capture layer

Reads packets directly from the NIC

Time is derived from the packet timestamps. The Napatech card (using the Napatech clock) time-stamps packets as they enter the Multi-Port Monitor.

Time is derived from the system time (wall clock)

Napatech or network card not required because the Multi-Port Monitor has its own Napatech card installed.

Requires purchase of a Napatech or network card.


User name: nqadmin

Password: nq


User name: cemadmin

Password: quality

Standalone TIM Options

If you have existing standalone TIMs, you have the following options:

1. Keep the standalone TIMs, upgrade them to version 9.1 or newer, and reconfigure each TIM (including the new TIM on Multi-Port Monitor) to monitor specific network traffic and load balance the traffic among the TIMs.

Note: Standalone TIMs have less integration with ADA. Data collected by both the standalone TIMs and TIM on Multi-Port Monitor generate defects shown on the CEM console. However, you can only link to session analysis data from defects generated by the TIM on Multi-Port Monitor. The Multi-Port Monitor must process the SPAN data for both CA APM and ADA to enable the integration.

2. Remove your stand-alone TIMs and move the SPAN for them to the new TIM on Multi-Port Monitor. See the CA Multi-Port Monitor User Guide.



For more information on configuring TIM monitoring and load balancing, see

(Optional) Configure Web Server Filters (see page 42)

Install TIM on the Multi-Port Monitor

Install TIM on the Multi-Port Monitor to enable it to collect TCP and HTTP data. The following two install files are CentOS-specific images that are required for the Multi-Port Monitor and must be installed in the following order:

1. Third-party image: APMCOSTRDPRTxxxx.img

2. TIM image: APM_COSTIMCMxxxx.img

Access these two files from the CA APM software download area on CA Support or the TIM software DVD bundle.

Before you start the installation, verify that Multi-Port Monitor is configured and connected to the network.

Follow these steps:

1. Log on to the Multi-Port Monitor using your administrator credentials or the following credentials if you have not changed the default:

Username = nqadmin

Password = nq

2. Click the System Setup tab.

3. Click the Install Software tab.

The Install Software page opens.

4. Install the third-party software.

a. Click Browse and navigate to the TIM install files.

b. Select the APMCOSTRDPRTxxxx.img file.

c. Click Upload and Install.

d. Read and accept the License Agreement.

Accept the EULA to continue.

e. The software installation log appears. If you see errors, contact CA Support.

The third-party software is installed.





5. Install the TIM software.

a. Click the Install Software tab.

b. Click Browse and navigate to the TIM install files.

c. Select the APM_COSTIMCMxxxx.img file.

d. Click Upload and Install.

e. Read and accept the License Agreement.

Accept the EULA to continue.

f. The software installation log appears. If you see errors, contact CA Support.

The TIM software is installed.

6. (Optional) Click the System Setup tab to see a list of the installed packages or the Administration tab to enable TIM Monitoring on a Multi-Port Monitor logical port.

7. Reboot the Multi-Port Monitor.

Configure Hardware Filters

For the CA APM to Multi-Port Monitor integration, web traffic monitored by TIM must have full packets. Define full packet capture by editing the "HTTP-full packets" default filter from the Multi-Port Monitor web UI.

You can create, enable, disable, and modify predefined filters and the filters you create.

Follow these steps:

1. Click Administration, Logical Ports in the web interface.

The Logical Ports page opens.

2. Click the Filters link in the Edit Filters column for the logical port you want to filter.

The Logical Ports: Hardware Filters page opens.



3. To create a filter, click New. The Logical Ports: New Hardware Filter page opens.

a. Complete the following fields:

■ Filter Enabled. Applies the filter on the logical port whose name is indicated. If selected, the filter is applied after you restart the nqcapd process.

■ Filter Name. The name of the filter you are creating or editing. The filter name is shown on the Hardware Filters page for the logical port to which it is applied.

■ Filter Priority. Priority determines which filters take precedence when filter criteria overlap. That precedence is undefined when two or more overlapping filters have the same priority. Values range from 0 (highest priority) to 62 (lowest priority). The default priority is 10.

Filter priority settings can be used with packet slicing. For example, you want to keep more bytes of each HTTP packet. You specify a filter for TCP and Port 80, with slicing set to 'TCP headers + 50 bytes' and Priority set to 1. You then specify another filter for TCP, with slicing set to 'TCP headers + 1 byte' and Priority set to 10. In this scenario, more payload bytes are kept for HTTP traffic than for other TCP traffic.

■ Packet Slicing Mode. Options for capturing only selected parts of each packet. The hardware filters let you capture packets for protocols other than TCP/IP. However, Multi-Port Monitor collects performance metrics only for TCP traffic. Volume metrics are collected for all traffic types.

Capture full packet: All information is captured from each packet that passes the filter.

Capture fixed size: Some bytes are captured from every packet. In the Packet Slicing Size field, supply the number of bytes to capture.

Capture headers plus size: All Layer 2, Layer 3, and Layer 4 headers are captured, plus the fixed number of payload bytes from the Packet Slicing Size field. Layer 2 headers include Ether II, LLC, SNAP, and Raw headers, and VLAN, ISL, and MPLS tags. Layer 3 headers include IPv4 (including IPv4 options), IPv6, and IPX headers. Layer 4 headers include TCP, UDP, and ICMP headers.



■ Include only Protocols. Limits the protocols to capture and process. Only the selected protocols are included in monitoring. If no check boxes are selected, all protocols are included.

Transport Control Protocol, TCP, is the main protocol that CA Application Delivery Analysis monitors.

User Datagram Protocol, UDP, is used for transport of the data that real-time or streaming applications send.

Internet Control Message Protocol, ICMP, is used for error messaging among servers and for CA Application Delivery Analysis traceroute investigations.Limits the protocols to capture and process. Only the selected protocols are included in monitoring. If no check boxes are selected, all protocols are included.

■ VLANs. The identifiers of the virtual local area networks (VLANs) to monitor or exclude from monitoring. List the identifiers of VLANs whose traffic passes through the indicated logical port. Separate multiple VLANs with commas and no spaces. Select Exclude to discard traffic from the VLANs you listed.

■ Subnets. The subnets to monitor or exclude from monitoring. Supply a valid IPv4 address and subnet mask, or a valid IPv6 address and prefix bits. Do not combine IPv4 and IPv6 addresses in the list. Select Exclude to discard traffic from the subnets you listed.

Use the following format for IPv4 addresses: x.x.x.x/n, where x.x.x.x is the IPv4 subnet address in dotted notation and n is the number of bits to use for the mask.

Use the following format for IPv6 addresses: x:x:x:x:x/n where x:x:x:x:x is the colon-separated IPv6 subnet address and n is the number of prefix bits. You can use standard abbreviated IPv6 addresses. For example, 2001:ba0:1a0::/48

Tip: To filter for IPv4 and IPv6 subnets, create one hardware filter for the IPv4 subnets and another hardware filter for the IPv6 subnets.

■ IP Addresses. The IPv4 or IPv6 addresses, or range of addresses, of individual hosts to monitor or exclude from monitoring. Separate multiple addresses with commas and no spaces. Separate ranges with a hyphen and no spaces. Do not combine single addresses and ranges in the list. Do not combine IPv4 and IPv6 addresses in the same list or range of addresses. Select Exclude to discard traffic from the addresses you listed.

Use dotted notation for IPv4 addresses. For example, 10.9.7.7, or 10.9.8.5-10.9.8.7.

Use colon-separated IPv6 addresses. You can use standard abbreviated IPv6 addresses. For example, 2001:f0d0:1002:51::4

Tip: To filter for IPv4 and IPv6 addresses, create one hardware filter for the IPv4 addresses and another hardware filter for the IPv6 addresses.



Ports. The TCP ports or port ranges to monitor or exclude from monitoring. Separate multiple port numbers with commas and no spaces. For a range of ports, use the following format: 2483-2484. Select Exclude to discard traffic from the ports you listed.

b. (Optional) Click Advanced to use regular expressions to create more precise filters. For more information, see Use Regular Expressions for Precise Filtering.

c. Click Save. The new filter appears on the Logical Ports: Hardware Filters page.

4. To modify or enable a filter, click Edit. The Logical Ports: Edit Hardware Filter page opens.

a. Complete the fields as described in step 3a.

b. (Optional) Click 'Show Details' to view your selections as a regular expression

c. Click Save. The filter appears on the Logical Ports: Hardware Filters page.

5. Restart the nqcapd process if you enabled a filter.

Configure TIM Monitoring on Logical Port

TIM monitors mirrored ports from one logical port. To map multiple physical ports to one logical port, mirror the web traffic from the WAN to the logical port. This traffic is processed for TIM and CA Application Delivery Analysis (if you have this product in your environment). Use the other logical ports for other port mirroring, ideally from the access-layer switches closest to the servers. The non-TIM logical ports on the Multi-Port Monitor are processed for CA Application Delivery Analysis only.

Follow these steps:

1. Open a browser window and log in to the Multi-Port Monitor web interface.

The Multi-Port Monitor web interface opens.

2. Click the Administration tab.

The Logical Ports page opens. The default settings for the available ports are shown.

1. Click the Filters link in the Edit Filters column to apply hardware filters to the port.

2. Provide the following information:

Name

Specifies the name of the logical port you want TIM to monitor.

The name helps to identify the source of the traffic you are monitoring. For example, use the name or location of the switch you are monitoring.



Enabled

Enables the port for monitoring.

Confirm that the check box labeled Enabled is selected.

Save Packets to Disk

(Optional) Saves captured data packets on the Multi-Port Monitor hard disk drive. With this option, the data may be available for export to PCAP on the Analysis page. By default, the Multi-Port Monitor keeps the packet for six hours.

TIM Monitor

Associates with the logical port you are configuring.

Select the check box associated with the logical port you are configuring.

Physical Ports

Assigns one or more of the available Physical Ports to the logical port.

The available ports depend on the capture card configuration you purchased from CA Technologies.

Logical port numbering begins at 0. The capture layer performs the mapping of physical ports to logical ports. The mapping process is transparent to TIM.

3. Click Save.

4. Restart the nqcapd process.

Perform this task on the Multi-Port Monitor Processes page.

5. (Optional) Check the status of the logical ports by viewing the Capture Card Logical Port Status table on the System Status page.

The Status column shows an Error status if there is a problem with starting the logical port, such as a syntax error in a hardware filter associated with that port.

TIM in Multi-Process Mode

When TIM is installed on the Multi-Port Monitor, it can utilize the multiple CPUs and load balance the traffic among multiple processes. Running in multi-process mode increases TIM throughput significantly. Exact throughput numbers vary based on many factors, such as the traffic being monitored, how you define transactions, and more.



In multi-process mode, TIM splits network traffic among multiple processes called worker processes. For TIM in multi-process mode to work effectively, do the following:

■ Distribute monitored traffic as evenly as possible between worker processes.

■ Verify that the same worker process monitors all packets belonging to same business transaction instance.

In different network configurations, these guidelines can be achieved by different means. CA Technologies provides several flexible ways to distribute traffic between workers. Options are:

Client IP address

Network traffic is assigned to worker processes based on the client IP address. This is the default and CA Technologies recommended option. Consider the other options if your network configuration does not make this option viable. For example, if all traffic appears to come from the same client IP address, such as when TIM is positioned behind a proxy server, then consider the other configuration options. The default configuration for this example is shared=client. Load balancing on TIM is not possible with this network configuration, so consider using the server IP address option.

Sever IP address

Network traffic is assigned to worker processes based on the server IP address, for example shared=server. This option requires that a single server handles all transactions in a business transaction.

Mixed

Traffic can be assigned to worker processes based on a combination of client and server IP addresses. If there is a discrepancy between the server rule and client rule, then the server rule takes precedence.

Use the Load Balancer Configuration file to define how you want TIM to load balance your clients or servers.

Note: Standalone TIMs run in single-process mode.

For information on editing the configuration file, see

Edit Load Balancer Configuration File (see page 39)



Examples: Configuration Options to run in Multi-Process Mode

The following examples show configuration options for setting up TIM in multi-process mode. Make these configuration changes on the balancer configuration file (balancer.cnf), located in /etc/wily/cem/tim/config/. Restart TIM to activate these configuration changes.

Example 1

If you have a client with HTTP transactions belonging to the 138.42.123.*/24 subnet, use the following configuration to assign the worker process 0 to this subnet: client=138.42.123.*/24 worker=0.

Example 2

If you have a server in the 138.42 subnet, use the following configuration to assign the worker process 0 to this subnet: server=138.42.0.0/16 worker=0.

Configure TIM for Multi-Process Mode

Configuring TIM for multi-process mode allows it to utilize the multiple CPUs and load balance the traffic among multiple processes. This configuration is a two step process.

1. Edit the load balancer configuration file (see page 39).

2. Enable the multi-process mode (see page 40).

Edit Load Balancer Configuration File

Edit the Load Balancer Configuration file to define how you want TIM to load balance your clients or servers. This is a plain text file and you must use a text editor to make any changes.



Follow these steps:

1. Log in to the converged appliance (Multi-Port Monitor running TIM) directly using the attached keyboard and monitor. You can also log in from a remote system using a secure shell (SSH) client such as PuTTY, which runs on Windows.

1. Press Alt+F2 on the initial screen if you are using the attached keyboard and monitor.

The Linux login screen opens.

2. Log in with the following credentials:

■ User name: netqos

■ Password: The password you created when you installed the Multi-Port Monitor software.

The 'netqos' user name and password provide superuser access.

The Linux command line interface opens.

2. Open the balancer.cnf file using a text editor.

The file is located in /etc/wily/cem/tim/config/balancer.cnf.

Do not use a Word processor or other programs that add formatting information.

3. Edit the file using the "sudo" prefix. The configuration file can only be edited with superuser access and "sudo" prefix.

For example, use the following command if you are using the vi editor:

$ sudo vi /etc/wily/cem/tim/config/balancer.cnf

4. Save the file.

5. Restart TIM.

You must restart TIM to apply the edits.

Enable/Disable Multi-Process Mode

Enable/disable the multi-process mode from the TIM configuration window. The mode is enabled by default.

Follow these steps:

1. Log on to the Multi-Port Monitor UI, select System Setup.

2. Select Tim x.x.x.x build xx.

The Tim Setup page opens.

3. Select Configure TIM Settings

The Tim Settings page opens.

4. Select Parallel/UseWorkers.



5. Change the New Value field accordingly.

1 means multi-process mode is enabled.

0 means multi-process mode is disabled.

6. Restart TIM.

You must restart TIM to make this change effective.

Associate TIM with an Enterprise Manager

This task is relevant to both the TIM on the Multi-Port Monitor and standalone TIMs (if applicable).

Enable TIMs so that they can monitor transactions. The Enterprise Manager does not receive data from disabled TIM monitors. If you have clustered Enterprise Managers, then enable the TIMs from the MOM Enterprise Manager.

These are some examples of when you enable TIMs:

■ When setting up a TIM and associating it with an Enterprise Manager.

■ After upgrading the TIMs and/or Enterprise Manager.

■ After a configuration is imported.

Follow these steps:

1. Open a web browser and enter the address of the server that hosts the Enterprise Manager. If using a clustered environment, specify the address of the MOM:

http://<IP_Address>:8081

where <IP_Address> is the IP address or DNS name for the MOM or a standalone Enterprise Manager. For example:

http://192.168.1.54:8081

http://cem.company.com:8081

To use a DNS name, your DNS administrator must have configured it.

Note: The default port is 8081. It is defined in the IntroscopeEnterpriseManager.properties file as introscope.enterprisemanager.webserver.port=8081 and can be changed.

2. Enter the user name and password.

The CEM console appears.

3. Select Setup, Monitors.



4. If the TIM does not appear in the list:

a. Click New.

b. Enter the name and IP address of the TIM.

c. Select the Multi-Port Monitor Enabled check box if TIM is listening on Multi-Port Monitor ports.

This task is only applicable if you are deploying the Multi-Port Monitor.

d. Click Save.

5. Select the check box next to each required TIM and click Enable.

Communication between the Enterprise Manager and the TIMs is then enabled. Additional tabs appear in the CA CEM console.

(Optional) Configure Web Server Filters

This task is optional. Perform this task if you still see too much network traffic after you have configured hardware filters. In this case, you need to further restrict the traffic monitored by TIM to specific servers by configuring web server filters. If TIM gets overloaded, recording might not work.

Multi-Port Monitor uses the web server filter configured for TIM running on the appliance to define what data it forwards to TIM.

Follow these steps:

1. Log on to CEM.

2. Select Setup > Web Server Filters.



3. Click New.

4. Type a Name that describes the network portion for TIM monitoring. For example, WebFarmCorp1.

5. In the Monitor list, select the TIM to assign to monitor this portion of the network.

Each TIM monitors an IP address range by default. If you want to monitor using a specific MAC address instead, go to step 6.

a. Fill in the From IP Address field.

Type the IP address of the Web server at the low end of the range. If there is only one server to monitor, type the specific IP address.

b. Fill in the To IP Address field.

Type the IP address of the Web server at the high end of the range. If there is only one server to monitor, type the specific IP address.

c. Fill in the Port field.

■ If the TIM is to monitor transactions only on a specific port, type the port number.

■ If the TIM is to monitor all transactions on all ports, type 0 (the default).

d. In most cases, TIMs should monitor specific servers in the network rather than overlapping servers. However, in special circumstances, you can allow overlapping IP addresses.

If you want to configure more than one monitor for an IP address or range, select Save without checking for overlapping IP Addresses.

6. If you want to monitor a specific MAC address instead of by IP address range:

a. Click the Address Type of MAC Address.

b. Type the specific MAC Address of the device you want to monitor. For example: 12:eb:a0:32:51:4c.



7. Click Save to configure the TIM monitor as specified.

Synchronize Monitors

You synchronize monitors to send the current domain configuration file to all enabled TIMs and agents.

Follow these steps:

1. Log on to the CEM console.

2. Select Setup > Monitors.

3. If any required monitors are disabled, enable them.

4. Click Synchronize All Monitors.

All the enabled monitors are synchronized and the related icon appears in the upper right. This task sends the updated transaction definitions to all enabled TIMs on your network. The TIMs immediately start monitoring the transactions you have defined. Synchronizing all monitors also causes the CEM console to send transaction and tracing information to the Enterprise Manager.

Verify the Connection

For the defect you are viewing, network data from the Multi-Port Monitor database is imported to the CEM console. This data is rendered in the CEM Defect Details page along with the defects generated by TIM.

Look for network data on the CEM Defect Details page to confirm the CA APM connection to Multi-Port Monitor.

Follow these steps:

1. Log onto the CEM console.

2. Select CEM, Incident Management, Defect.

3. Do one of the following:

1. Select a defect from the list.

2. Search for a specific defect.

4. Review the network health metrics associated with the selected defect.

Network metrics such as CT Observed, DTT, ENRTT, TCP Conversation Analysis, and more are available. In the TCP Conversation Analysis field, a link to Multi-Port Monitor is available.

See the How to Triage Application and Infrastructure Issues Starting from CEM Console scenario for information on these metrics.

How to Connect CA APM to Application Delivery Analysis



Connecting CA APM to CA Application Delivery Analysis (ADA) allows you to view infrastructure data on APM WebView. Enterprise Manager periodically calls web services on the ADA Manager for these metrics and renders them on APM WebView. Enterprise Manager also stores these metrics in the SmartStor for historical reporting.

The following illustration describes how as an administrator you connect CA APM to CA Application Delivery Analysis.


1. Run installer program (see page 46).

2. Start the ADA-APM service (see page 49).

3. Synchronize time (see page 49).




Prerequisites


■ CA Application Delivery Analysis 9.1 or newer

■ CA Performance Center 6.1/CA Performance Center 2.0








Run the Installer Program

The CA APM Integration for CA Application Delivery Analysis installer program contains two installable components, CAPC Integration Pack and CA Application Delivery Analysis Extension for APM. Instructions in this section show you how to install the CA Application Delivery Analysis Extension for APM. This installable component enables communication between CA Application Delivery Analysis and CA APM.

Install the installable component on the Enterprise Manager or MOM (if you have a clustered CA APM environment).

You need the following information to complete the installation:

■ Enterprise Manager host name

■ Enterprise Manager port number

■ Host name or IP address of the servers to which the CA Application Delivery Analysis Extension for APM installable component connects

Follow these steps:

1. Download the CA APM Integration for CA Application Delivery Analysis installer program from the CA APM software download area on CA Support.

2. Navigate to your local version of the Integration Pack installer program and double-click it.

The installer opens.

3. Click Next on the Welcome screen.





4. Read and accept the End User License Agreement.

Accept the agreement to continue.

5. Specify where you want the integration pack files installed and click Next.

6. Select the CA Application Delivery Analysis Extension for APM installable component.

7. Click Next.

8. Specify the Enterprise Manager hostname and port to which this installable component will connect and click Next.

9. Specify the hostname or IP address of all the CA Application Delivery Analysis consoles to which this installable component will connect and click Next.

10. Specify whether to configure the CA Application Delivery Analysis Extension for APM as a Windows service and click Next.

In a Windows OS environment, the CA Application Delivery Analysis Extension for APM installable component installs the ADA-APM service.

11. Review your settings and click Install.

CA Application Delivery Analysis Property Files

After you install the CA Application Delivery Analysis Extension for APM, the ADAExtensionForAPM folder contains the ADAConnector files. These files let you verify configuration settings and update default settings if necessary.

The following configuration settings are part of the CA Application Delivery Analysis Extension for APM installable component, but you can verify and update them using these properties:

Enterprise Manager host name

com.wily.apm.adaconnector.em.host=<EM host name>

Enterprise Manager port number

com.wily.apm.adaconnector.em.port=<EM port>

Host names or IP addresses

This information reflects the values of all the ADA Manager to which the CA Application Delivery Analysis Extension for APM installable component is connected

com.wily.apm.adaconnector.adawssoap_address_source1=<addr>

com.wily.apm.adaconnector.ada_hostName1=<host name>

Name of the installer program

com.wily.apm.adaconnector.ada_processName1=<ADAExtensionforAPM>

The ADAExtensionforAPM value represents the process name as seen on the Workstation.



The ADAConnector files make the following configuration settings available:

Enhanced metrics

The queries for these infrastructure metrics are disabled by default. Enable the query if you want to make the following infrastructure metrics available on the Workstation:

■ Data Transfer Time

■ Network Round Trip Time

■ Retransmission Delay

■ Server Response Time

Sample property:

com.wily.apm.adaconnector.ada_enhancedmetrics_enabled2=<true|false>

<enabled2> is an index of your ADA Manager. The first ADA Manager corresponds to <enabled1>, second Management console corresponds to <enabled2>, and so on.

CA Application Delivery Analysis web service query

The wait period between the ADA data time bin and web service query. The default wait time is 5 minutes. The ADA Manager can connect to several collectors, such as Multi-Port Monitors and single port ADA collectors. To allow for aggregation of the collected data, ADA time bins are 5-minutes wide and end at 5-minutes boundaries, for example, 7:00, 7:05, and so on. ADA Manager updates its database every 5-minutes. The wait period value in this property shifts the query from exact 5-minutes boundaries by the specified time frame. For example, defining the wait period as 2-minutes shifts the ADA time bins to 7:02, 7:07, and so on.

CA Technologies recommends that you do not change the default value unless instructed by CA Support.

Note: Updating this property does not change the web service call frequency. This frequency is fixed at 5-minutes intervals.

Sample property (units are in milliseconds):

com.wily.apm.adaconnector.adawebservice.wait=120000

SmartStor data feed interval

Data feed interval from ADA to Enterprise Manager.

The default interval is 15 seconds. CA Technologies recommends that you do not change the default value unless instructed by CA Support.


com.wily.apm.adaconnector.smartstorfeed.interval=15000



SmartStor data feed wait time

The wait period between the CA Application Delivery Analysis web service query and Enterprise Manager starting its data feed.

The default wait time is 10 seconds. CA Technologies recommends that you do not change the default value unless instructed by CA Support.


com.wily.apm.adaconnector.smartstorfeed.wait=10000

Start the ADA-APM Service

After you install the CA Application Delivery Analysis Extension for APM installable component, start the ADA-APM service.

Windows OS

Start the ADA-APM service in Windows Services.

This service does not start automatically. You start it manually after the installation.

Linux/UNIX OS

Start the CA Application Delivery Analysis Extension for APM using the following command:

<INSTALL_HOME>\ADAExtensionForAPM$./ADAConnector

Synchronize Time

Synchronize the clocks between the following machines to a common time source:

■ CA Application Delivery Analysis

■ Enterprise Manager or MOM

Synchronizing the clocks helps to ensure the integrity of CA APM application data on the CA Performance Center/CA Performance Center and infrastructure data on the APM WebView. If this task is not performed, time between the components can drift, leading to data inaccuracies or loss.

CA Technologies recommends synchronizing your entire network to a Network Time Protocol time source or a time server. If this is not possible, then at a minimum, you must synchronize the machines discussed.




Look for the out-of-the-box dashboard and certain network metrics to confirm the CA APM to CA Application Delivery Analysis connection.

Follow these steps:

1. Log on to either the APM WebView or Introscope Workstation.

2. Look for the Network Status Information dashboard on the Console.

3. Look for the following information for each client subnet and server on the Investigator, Metric Browser tab:

■ Network health status

■ Server health status





By default, the following metrics are disabled:





To enable these metrics, use the com.wily.apm.adaconnector.ada_enhancedmetrics_enabled1=<true|false> property in the ADA property file. See the How to Connect CA APM to Application Delivery Analysis scenario for information on this property file.

From the Network Status Information dashboard, you can navigate directly to CA Performance Center/CA Performance Center. In addition to this out-of-the-box dashboard, the infrastructure metrics are also available for you to create custom dashboards.

Note: For more information about creating dashboards, see the CA APM Workstation User Guide.

How to Connect CA APM to CA Performance Center



Connecting CA APM to CA Performance Center allows you to view CA APM application data on the CA Performance Center. Application data flows from the Enterprise Manager to the CA Performance Center.

CA APM is connected to the CA Performance Center using the CAPC Integration Pack installable component. This installable component installs the APM-CAPC service and provides CA APM data in a format that CA Performance Center can understand and display.



The following illustration describes how as an administrator you connect CA APM to CA Performance Center.




1. Run the installer program (see page 53).

2. Start the APM-CAPC service (see page 55).

3. Configure alerts on APM WebView (see page 55).

4. Import APM views into CA Performance Center (see page 56).

5. Register APM as a data source (see page 57).

6. Add the APM menu items to application health (see page 58).

7. Enable HTTP support (optional) (see page 59).


Prerequisites


■ CA Performance Center 2.0.00








■ Alerts on the APM WebView or Workstation application triage map elements

■ Agents to monitor business transactions, business services, and business components


The CA APM Integration for CA Application Delivery Analysis installer program contains two installable components, CA Performance Center Integration Pack and CA CA Application Delivery Analysis Extension for APM. Instructions in this section show you how to install the CA Performance Center Integration Pack. This installable component enables communication between CA Performance Center and CA APM.






■ Enterprise Manager web server port number

■ CA APM Workstation user name

■ CA APM Workstation password

■ Enterprise Manager services user name and password

■ Web server port that the CA Performance Center Integration Pack installable component uses

Follow these steps:








6. Select the CA Performance Center Integration Pack installable component.

7. Click Next.

8. Specify the Enterprise Manager hostname and webserver port and click Next.

9. Specify the CA Introscope® and TESS account of the Enterprise Manager and click Next.

10. Specify whether to configure the CA Performance Center Integration Pack as a Windows service and click Next.

In a Windows OS environment, the CA Performance Center Integration Pack installable component installs the APM-CAPC service.

11. Specify the web server port for use by the CA Performance Center Integration Pack and click Next.


After you install the CA Performance Center Integration Pack installable component, the CAPCIntegrationPack folder appears in the directory specified in step 5. The folder contains the webapps folder, which provides the extracted Jetty Web Server and apm-capc-integration folders.





Start the APM-CAPC Service

After you install the CA Performance Center Integration Pack, start the APM-CAPC service.

Windows OS

Start the APM-CAPC service in Windows Services.


Linux/UNIX OS

Start the CA Performance Center Integration Pack using the following command:

<INSTALL_HOME>\CAPCIntegrationPack\bin$./jetty.sh start

Configure Alerts on APM WebView

Alerts on APM WebView allow you to set thresholds on metrics and to execute actions when metrics cross thresholds. Many objects in the application triage map can display alerts. These alerts reflect the worst-case status of any baseline metrics for those objects.

Create alerts to make application, business service, and business transaction health status indicators available on CA Performance Center.

Follow these steps:

1. In WebView, click Investigator, Triage Map.

2. Navigate the tree to the alert that you want to edit, for example:

By Frontend|Application_Name|Backend Calls|file%customer-records

3. Right-click the component and select Edit Alert For Name from the context menu.

The Edit Alert For Name dialog appears.

4. In the left pane, select a metric that you want to contribute to the alert status.



5. Select the type of problem that you want to trigger the alert from the Problem drop-down list:

Value Too High

Triggers the alert when the metric value exceeds the threshold.

Value Too Low

Triggers the alert when the metric value drops below the threshold.

Specific Bad Value

Triggers the alert when the metric value is equal to the threshold. Then the threshold is referred to as bad value rather than a threshold value.

Unexpected Value

Triggers the alert when the metric value is not equal to the threshold value. Then the value is referred to as an expected value rather than a threshold value.

6. Click the Summary Metrics tab. Set the Threshold Values and Sensitivity Levels for Danger and Caution alerts, and click Apply.

Danger

Triggers the alert when the metric value exceeds the threshold. Alerts appear in red.

Caution

Triggers the alert when the metric value approaches the threshold. Alerts appear in yellow.

7. Click Apply.

8. Repeat Steps 4 through Step 7 for each metric.

9. Click OK.

Import the APM Views into CA Performance Center

Copy the integration XML files and import the APM view definitions into the CA Performance Center database.

Follow these steps:

1. Navigate to the following location:

<CAPC Integration Pack Home>\CAPCIntegrationPack\CAPC_2_0

2. Copy the apm directory from the CAPC_2_0 folder to the plugins folder in the following location:

<CAPC-HOME>/PerformanceCenter/SQL/plugins



3. From a command prompt, execute the following command to import the views into the CA Performance Center database:

<CAPC-HOME>/PerformanceCenter/Tools/bin/npcshell.sh dbmigrate –package

com.ca.im.plugin.apm –path <CAPC-HOME>/PerformanceCenter/SQL/plugins/apm

Register APM as a Data Source

CA Performance Center can only receive information from a registered data source.

Follow these steps:

1. Log in to CA Performance Center as a user with administrative privileges.

2. Select Admin, Settings, and click Data Sources.

The Data Source List page appears.

3. Click Add.

The Add Data Source page appears.

4. Select Application Performance Management from the Source Type list.

Note: The Source Type list shows all CA Technologies products that can be registered as CA Performance Center data sources, including products not installed in your environment and some third-party integrations. Supported data sources from other companies are listed only after you complete the required configuration. The Application Performance Management data source supports definition of a single enabled data source. If you want to add another data source, delete the existing data source.

5. Enter the Host Name of the data source.

The host name is the IP address or DNS host name of the server where the database for this data source is installed. For the CA APM data source, enter the IP address of the host where the CA Performance Center Integration Pack installer program is installed.

6. Select the protocol to use to contact the data source. The default protocol for a CA APM data source is HTTP.

Select https if your network is using SSL for communications. Verify that you have configured the system correctly before you select the https option.

Note: If you plan to use SSL for communications between CA Performance Center and the data source products, see the CA Single Sign-on Guide. Specific to the CA APM data source, if you select the https option here, also enable SSL communication between the Enterprise Manager and the integration web services.



7. Supply the port to use when contacting the data source. The port depends on the protocol you selected in the previous step. The default port is 8082 for the Application Performance Manager data source.

Note: Consult the Single-Sign-On Guide for more information if you plan to use SSL for communications between CA Performance Center and the data source products.

8. Enter a Display Name for the data source. By default, the data source type and the host name are combined to create the name of the data source.

Example: <datasourcename>@<hostname>

Note: Web Console address is not applicable to CA APM.

9. Click Save if you have finished registering data sources.

CA Performance Center lists the data sources registered in the Data Source List.

Add the APM Menu Items to Application Health

In CA Performance Center, add the following CA APM dashboard menu items to the Application Health menu:

■ APM - Applications Status

■ APM - Business Services Status

Menu items can be added for the default tenant or for any existing tenant. After the menus are set for existing tenants, new tenants can automatically access the menus without the need for these steps.

Follow these steps:

1. Log in as an administrator with the Default Tenant or another Tenant administrator account.

2. Select Admin, User Settings, and click Menus.

The Manage Menus page displays the current list of menus.

3. Select Application Health and click Edit.

4. Select the APM – Application Summary and/or the APM – Business Services Summary dashboards in the Available list. To select multiple dashboards, use Shift + Click.

5. Click the right arrow.

6. The dashboard moves to the Selected list.

7. Click Save.

The menu items are set.



Enable HTTPS Support (Optional)

You can enable the HTTPS protocol for added security using the Secure Sockets Layer (SSL), which provides communication between CA APM and CA Performance Center as follows:

■ Obtain a server certificate. Some administrators can also choose to use client certificates for additional security. Configuring a website in IIS to use SSL, server certificates, and client certificates is outside the scope of this document. However, the following Microsoft article gives an in-depth discussion of the use of these IIS website security features.

SSL and Certificates (IIS 6.0): http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/559bb9d5-0515-4397-83e0-c403c5ed86fe.mspx?mfr=true

■ Configure the CA APM data source (see page 57) with HTTPS support to enable HTTPS communication between the CA Performance Center and CAPC Integration Pack.

■ Edit the apm-capc-integration.properities file (see page 59) to enable HTTPS communication between the Enterprise Manager and CAPC Integration Pack installable component.

Edit apm-capc-integration.properties File

Editing the apm-capc-integration.properties file enables HTTPS communication between the Enterprise Manager and the CAPC Integration Pack installable component.

Follow these steps:

1. Open the apm-capc-integration.properties file in a text editor from the following location:

<INSTALLATION_HOME>\CAPCIntegrationPack\resources

2. Locate the property: com.apm.npc.em.transport.protocol, and specify the value <https>.

3. Locate the property: javax.net.ssl.keyStore, and specify the value <KEYSTORE LOCATION FOR SSL CONNECTION>.

4. Locate the property: javax.net.ssl.keyStorePassword, and specify the value <KEYSTORE PASSWORD FOR SSL CONNECTION>.

5. Locate the property: javax.net.ssl.trustStore, and specify the value <TRUSTSTORE LOCATION>.

6. Locate the property: javax.net.ssl.trustStorePassword, and specify the value <TRUSTSTORE PASSWORD>.

The properties are set.

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/559bb9d5-0515-4397-83e0-c403c5ed86fe.mspx?mfr=true


How to Connect CA APM to NetQoS Performance Center



CA Performance Center displays application health and performance status data in a drill-down fashion for a selected time period. When CA APM is registered as a data source on CA Performance Center, you can access application data from the Applications Summary report or Business Services Summary report. From these reports, you can drill down to the incidents and defects.

Look for data in the out-of-the-box reports to confirm the CA APM connection to CA Performance Center.

Follow these steps:

1. Log onto the CA Performance Center.

2. From the CA Performance Center Reports menu, you see the following CA APM related reports:

■ APM--Applications Summary

■ APM--Business Services Summary

3. You see the health status of business applications in the Applications Summary report.

4. You see the health status of business services for the selected application in the Business Services Summary report.


Connecting CA APM to CA Performance Center (NPC) allows you to view CA APM application data on the NPC.

CA APM is connected to the NPC using the CAPC Integration Pack installable component. This installable component installs the APM-CAPC service and provides CA APM data in a format that NPC can understand and display.



The following illustration describes how as an administrator you connect CA APM to NPC.




1. Run the installer program (see page 62).

2. Start the APM-CAPC service (see page 55).

3. Configure alerts on APM WebView (see page 64).

4. Update the CA Performance Center database (see page 65).

5. Register APM as a data source (see page 66).

6. Enable HTTP support (optional) (see page 67).

7. Verify the Connection (see page 68).

Prerequisites


■ CA Performance Center 6.1 or newer








■ Alerts on the APM WebView or Workstation application triage map elements

■ Agents to monitor business transactions, business services, and business components


The CA APM Integration for CA Application Delivery Analysis installer program contains two installable components, CA Performance Center Integration Pack and CA Application Delivery Analysis Extension for APM. Instructions in this section show you how to install the CA Performance Center Integration Pack. This installable component enables communication between CA Performance Center and CA APM.






■ Enterprise Manager web server port number

■ CA APM WebView or Workstation user name

■ CA APM WebView or Workstation password

■ Enterprise Manager services user name and password

■ Web server port that the CAPC Integration Pack installable component uses

Follow these steps:








6. Select the CA Performance Center Integration Pack installable component.

7. Click Next.

8. Specify the Enterprise Manager hostname and webserver port and click Next.

9. Specify the CA Introscope® and TESS account of the Enterprise Manager and click Next.

10. Specify whether to configure the CA Performance Center Integration Pack as a Windows service and click Next.

In a Windows OS environment, the CA Performance Center Integration Pack installable component installs the APM-CAPC service.

11. Specify the web server port for use by the CA Performance Center Integration Pack and click Next.


After you install the CA Performance Center Integration Pack installable component, the CAPCIntegrationPack folder appears in the directory specified in step 5. The folder contains the webapps folder, which provides the extracted Jetty Web Server and apm-capc-integration folders.





Start the APM-CAPC Service

After you install the CA Performance Center Integration Pack, start the APM-CAPC service.

Windows OS

Start the APM-CAPC service in Windows Services.


Linux/UNIX OS

Start the CA Performance Center Integration Pack using the following command:

<INSTALL_HOME>\CAPCIntegrationPack\bin$./jetty.sh start

Configure Alerts on APM WebView

Alerts on the Workstation allow you to set thresholds on metrics and to execute actions when metrics cross thresholds. Many objects in the application triage map can display alerts. These alerts reflect the worst-case status of any baseline metrics for those objects.

Create alerts to make application, business service, and business transaction health status indicators available on CA Performance Center.

Follow these steps:

1. In WebView, click Investigator, Triage Map.

2. Navigate the tree to the alert that you want to edit, for example:

By Frontend|Application_Name|Backend Calls|file%customer-records

3. Right-click the component and select Edit Alert For Name from the context menu.

The Edit Alert For Name dialog appears.

4. In the left pane, select a metric that you want to contribute to the alert status.



5. Select the type of problem that you want to trigger the alert from the Problem drop-down list:

Value Too High

Triggers the alert when the metric value exceeds the threshold.

Value Too Low

Triggers the alert when the metric value drops below the threshold.

Specific Bad Value

Triggers the alert when the metric value is equal to the threshold. Then the threshold is referred to as bad value rather than a threshold value.

Unexpected Value

Triggers the alert when the metric value is not equal to the threshold value. Then the value is referred to as an expected value rather than a threshold value.

6. Click the Summary Metrics tab. Set the Threshold Values and Sensitivity Levels for Danger and Caution alerts, and click Apply.

Danger

Triggers the alert when the metric value exceeds the threshold. Alerts appear in red.

Caution

Triggers the alert when the metric value approaches the threshold. Alerts appear in yellow.

7. Click Apply.

8. Repeat Steps 4 through Step 7 for each metric.

9. Click OK.

Update the CA Performance Center Database

This task updates the CA Performance Center database with the apm_integration.sql script. The script adds the CA APM data source to the list of available data sources. Additionally, it adds other CA APM-specific information to the database that are necessary for displaying application data on the CA Performance Center.

To run the SQL script:

1. Copy the apm_integration.sql file from CAPCIntegrationPack folder to the CA Performance Center machine.

This folder is created when you installed the CA APM Integration Pack for CA Application Delivery Analysis installer.



2. Open a Windows command prompt.

3. Execute: cd <location of the apm_integration.sql>

4. Execute: mysql

5. Execute: source <path>\apm_integration.sql

The CA Performance Center database is updated.

Register CA APM as a Data Source

CA Performance Center can only receive data from registered data sources.

Note: For more information about managing data sources and the number of data sources that a single CA Performance Center instance can support, see the CA Performance Center Administrator and User Guide.

Follow these steps:

1. Log in to CA Performance Center as a user with administrative privileges.

2. Select Admin, CA Settings, and click Data Sources.

The Data Source List page opens.

3. Click New.

The Add New Data Source page opens.

4. Select the type of data source you want to add from the Source Type list.

Note: The Source Type list shows all CA Technologies products that can be registered as CA Performance Center data sources, including those not installed in your environment and some third-party integrations. Supported data sources from other companies are listed only after you complete the required configuration. If a data source type is not listed, check to see whether you have already registered the maximum number of data sources for that type.

5. Enter the Host Name of the data source.

The host name is the IP address or DNS host name of the server where the database for this data source is installed. For the CA APM data source, enter the IP address of the host where the CAPC Integration Pack installable component is installed.



6. Select the protocol to use to contact the data source. The default protocol for a CA APM data source is HTTP.

Select https if your network is using SSL for communications. Verify that you have configured the system correctly before you select the https option.

Note: If you plan to use SSL for communications between CA Performance Center and the data source products, see the CA Single Sign-on Guide. Specific to the CA APM data source, if you select the https option, you must also enable SSL (see page 67) communication between the Enterprise Manager and the integration web services.

7. Supply the port to use when contacting the data source. The port number depends on the protocol you selected in the previous step. The default CA APM port is 8082.

Consult the Single-Sign-On Guide for more information if you plan to use SSL for communications between CA Performance Center and the data source products.

8. Confirm the Web Console address. If it is not the same as the Host Name, clear the Same as above check box and provide the Web Console information:

9. (Optional) Enter a Display Name for the data source.

By default, the data source type and the host name are combined to create the name of the data source. You can supply another name here.

Example: Instead of [email protected], you can name the data source APM_SantaFe.

10. Click Save if you have finished registering data sources.

CA Performance Center lists the data sources you have registered in the Data Source List.

Enable HTTPS Support (Optional)

You can enable the HTTPS protocol for added security using Secure Sockets Layer (SSL). To use SSL for communication between CA APM and CA Performance Center, do the following:

■ Obtain a server certificate. Some administrators may also choose to use client certificates for additional security. Configuring a website in IIS to use SSL, server certificates, and client certificates is outside the scope of this document. However, the following Microsoft article gives an in-depth discussion of the use of these IIS website security features.

SSL and Certificates (IIS 6.0): http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/559bb9d5-0515-4397-83e0-c403c5ed86fe.mspx?mfr=true

■ Configure the CA APM data source (see page 66) with HTTPS support to enable HTTPS communication between the CA Performance Center and CA Performance Center Integration Pack installable component.





■ Edit the apm-capc-integration.properities file (see page 59) to enable HTTPS communication between the Enterprise Manager and CAPC Integration Pack installable component.

Edit apm-capc-integration.properties File

Editing the apm-capc-integration.properties file enables HTTPS communication between the Enterprise Manager and the CAPC Integration Pack installable component.

Follow these steps:

1. Open the apm-capc-integration.properties file in a text editor from the following location:

<INSTALLATION_HOME>\CAPCIntegrationPack\resources

2. Locate the property: com.apm.npc.em.transport.protocol, and specify the value <https>.

3. Locate the property: javax.net.ssl.keyStore, and specify the value <KEYSTORE LOCATION FOR SSL CONNECTION>.

4. Locate the property: javax.net.ssl.keyStorePassword, and specify the value <KEYSTORE PASSWORD FOR SSL CONNECTION>.

5. Locate the property: javax.net.ssl.trustStore, and specify the value <TRUSTSTORE LOCATION>.

6. Locate the property: javax.net.ssl.trustStorePassword, and specify the value <TRUSTSTORE PASSWORD>.

The properties are set.


CA Performance Center displays application health and performance status data in a drill-down fashion for a selected time period. When CA APM is registered as a data source on CA Performance Center, you can access application data from the Applications Summary report or Business Services Summary report. From these reports, you can drill down to the incidents and defects.

Look for data in the out-of-the-box reports to confirm the CA APM connection to CA Performance Center.



Follow these steps:

1. Log onto the CA Performance Center.

2. From the CA Performance Center Reports menu, you see the following CA APM related reports:

■ APM--Applications Summary

■ APM--Business Services Summary

3. You see the health status of business applications in the Applications Summary report.

4. You see the health status of business services for the selected application in the Business Services Summary report.


Chapter 4: Triaging Scenarios


How to Triage Application and Infrastructure Issues Starting from CEM Console (see page 71) How to Triage Application and Infrastructure Issues Starting from APM WebView (see page 77) How to Triage Application Issues Starting from NPC (see page 87)

How to Triage Application and Infrastructure Issues Starting from CEM Console

Network data on the CEM console provides the diagnoser with high-level network performance information related to the application being monitored. You can then determine if network issues are contributing to the problem being triaged and drill into the Multi-Port Monitor for session level data. If metrics indicate that the network is not a concern, you can connect to the APM WebView to investigate and triage the application.



The following diagram shows a possible triaging scenario.

As a diagnoser, perform the following steps:

1. Determine your Triaging Options (see page 72).

2. Continue Triaging from Multi-Port Monitor (see page 76).

3. Continue Triaging from APM WebView (see page 77).

Determine your Triaging Options

When you see infrastructure concerns related to your applications, determine some triaging options to help guide your next steps.

Follow these steps:

1. Log onto the CEM console.

2. Select CEM, Incident Management, Defect.



3. Do one of the following:

1. Select a defect from the list.

2. Search for a specific defect.

4. Review the network health metrics associated with the selected defect.

For example, if you see high network round-trip time or packet loss, you might choose to connect to the Multi-Port Monitor. From there, you can investigate the network infrastructure in more detail.

See Network Metrics on the Defect Details Page (see page 73) for information on the network health metrics.

Network Metrics on Defect Details Page

When CEM identifies a defect, it queries Multi-Port Monitor for the session-level TCP information and saves it as part of the defect details. When you drill into a defect, this TCP information is made available on the CEM console.

Each field displays the average value of all TCP sessions for the application between the web server and client IP for the 15 minutes leading up to the defect time. Use the link on the TCP Conversation Analysis field to see the metrics for the individual TCP sessions.

The following network information is available on the Defect Details page:

NCT Obs

Connection Time Observations. The number of monitored TCP connections occurring during the selected time interval. A good indication of usage levels and a gauge of metric significance. For example, many observations can indicate an event that can affect users.

DTT

Data Transfer Time. Elapsed time between when the server starts responding and when it finishes sending data. Several factors affect this value, such as response size, available bandwidth, and interaction between the application and the network. Excludes the initial server response time and includes only NRTT if there is more data to send than fits in the TCP window. This value is related to the number of network round trips required to deliver all data and the delay per round trip.

ENRTT

Effective Network Round-Trip Time. Includes NRTT and Retransmission Delay, which is the delay that retransmissions cause for a transaction. Reflects the latency that users actually experience and serves as an indicator of the performance degradation that retransmissions cause.



NCT

Network Connection Time. The amount of time that it takes the client to confirm the server connection acknowledgment. In general, network latency causes delay in connection times. NCT serves as a baseline for carrier latency and comparison to NRTT values.

NRTT

Network Round-Trip Time. The amount of time it takes for a packet to travel to and from the server and clients on a network, excluding latency from retransmissions. Application and server processing times are excluded from this value. This value is often useful when compared to the NCT value.

NRTT Obs

Network Round Trip Time Observations. The number of round trip between the server and clients on a network during the selected time interval. A good indication of utilization levels, as well as a gage of metric significance. For example, a large number of observations indicates that an event might affect many users.

Retrans

Retransmission Delay. The additional delay in the NRTT that retransmission cause. Retransmissions are packets that are retransmitted after data loss. The data is expressed as an average across all observations, not the actual retransmission time for each transaction. The NRTT value increases when Retransmission Delay causes a delay in client acknowledgment. This metric does not reveal the impact of losses on the DTT because of TCP congestion. This metric reflects only data loss from the server to the clients, not from clients to the server.

SCT

Server Connection Time. The amount of time from when the server receives the SYN packet from the client until the server sends the first SYN/ACK. Opening a TCP connection involves exchanging three packets: SYN, SYN/ACK, and ACK. The TCP header has SYN (synchronize) and ACK (acknowledge) bits. The first packet has the SYN bit set. The second packet has both bits set. The third packet has only the ACK bit set. This exchange establishes the initial sequence numbers of the connection. SCT and NCT comprise the Connection Setup Time metric. For more information, see the ADA Sessions reports.

SRT

Server Response Time. The amount of time a server takes to respond to a client request. Server speed, application design, and volume of requests affect SRT.

TCP Bytes

TCP data volume in bytes. The total number of TCP bytes sent and received during the selected time period by the selected host or pair of hosts.



TCP Bytes From

TCP data volume in bytes. Total number of Application-Layer bytes that the selected server sent to or received from clients during the selected time period.

TCP Byte Loss Percent

Data loss, expressed as a percentage of TCP bytes sent and received.

TCP Byte Rate

TCP data volume in bytes. The data rate in bytes per second during the selected time period.

TCP Byte Rate From

TCP throughput in bits. The data rate in bits per second (bytes per second x 8) between the selected server and clients during the selected time period.

TCP Byte Rate Retransmtd

Ratio of retransmitted data to total data, percentage of data that was lost on the monitored network, and loss rate in bits per second.

TCP Conversation Analysis

Link to Multi-Port Monitor TCP Conversation report on the Analysis tab. The client network information on Multi-Port Monitor corresponds to the client network ID for the session requested by the CEM console. The initial view of the TCP Conversation report is sorted by Transaction Time. From this report, you can access the Server/Client Pair view to see all clients belonging to the same subnet as the client IP address that is talking to the given server.

Packet Loss Percent

Data loss, expressed as a percentage of TCP packets that were sent and received.

TCP Packet Rate

TCP throughput in packets. The data rate in packets per second during the selected time period. ADA reports use the term Data Rate.

TCP Packet Rate From

TCP throughput in packets. The data rate in packets per second from the selected server to clients, or from clients to the server, during the selected time period.

TCP Packet Rate Retransmtd

Ratio of retransmitted data to total data, percentage of data that was lost on the monitored network, and loss rate in packets per second.

TCP Packets

TCP data volume in packets. The total number of TCP packets that the selected host (or pair of hosts) sent and received during the selected time period.



TCP Retransmtd Bytes

The number of TCP bytes that were retransmitted due to data loss.

TCP Retransmtd Packets

The number of TCP packets that were retransmitted due to data loss.

Transaction Time

The amount of time from the moment a client sends the request (packet-level or transaction-level) to the moment the client receives the last packet in the response.

Transaction Time Observed

Transaction Time Observations. The number of monitored TCP transactions that occurred during the selected interval. A good indication of usage levels and a gauge of metric significance. For example, many observations can indicate an event that can affect many users.

Continue Triaging from Multi-Port Monitor

If the network metrics for the defect show degraded network/server performance (such as high network round-trip time or packet loss), one option is to connect to the Multi-Port Monitor via the TCP Conversation Analysis link. From the Multi-Port Monitor, you can investigate the infrastructure in more detail. Do one of the following to access the Multi-Port Monitor.

Follow these steps:

1. Select the link associated with the TCP Conversation Analysis field from the Defect Details page on CEM.

This link takes you to the TCP Conversation report in the Multi-Port Monitor. The initial view of the TCP Conversation report is sorted by Transaction Time. From this report, you can access the Server/Client Pair view to see all clients belonging to the same subnet as the client IP address that is talking to the given server.

See the Multi-Port Monitor User Guide for more information.

Follow these steps:

1. Log on to Multi-Port Monitor.

2. Select the Analysis tab.

3. Navigate to the relevant TCP Conversation report.

See the Multi-Port Monitor User Guide for more information.

How to Triage Application and Infrastructure Issues Starting from APM WebView


Continue Triaging from APM WebView

If the network metrics for the defect are within the expected range for your business, one option is to continue triaging the application from the APM WebView

Follow these steps:

1. Log on to the APM WebView.

2. Use the Console or Investigator to triage your issue.


Infrastructure data on the APM WebView allows support engineers to do the following:

■ View high-level client network and server health statuses and determine if immediate in-depth investigation of the infrastructure is warranted.

■ If warranted, you can connect directly to CA Performance Center (NPC)/CA Performance Center (CAPC) to investigate the specific client network or server.

■ If the infrastructure data shows acceptable performance but your applications are still showing degraded performance, you can investigate the application further using the APM WebView



The following diagram shows a possible triaging scenario.

As a diagnoser, perform the following steps:


2. Continue Triaging from NPC/CAPC (see page 85).



When you see infrastructure concerns related to your applications, determine some triaging options to help guide your next steps.

Follow these steps:




2. Navigate to one of the following dashboards or overview pages:

1. Select the Network Status Information dashboard from: Console, Dashboard drop-down list.

Use the health statuses of the client subnets and servers to determine your next steps. For example, if a critical client network or server is not performing well, select the associated More Information button to access the client subnet/server overview reports in CA Performance Center (NPC)/CA Performance Center (CAPC). The More Information buttons require a one time configuration. Configure the buttons from APM Workstation. See Configure More Information on Network Status Information Dashboard (see page 81).

See Network Status Information dashboard (see page 80) for more information on this dashboard.

2. Navigate to the overview data for all networks/servers you are monitoring: Investigator, Metric Browser tab, Networks or Server node, Overview tab.

Use the health status of each client subnet/server to determine your next steps. For example, if a critical client subnet or server has a health status of 2 (degraded), then you can log on to NPC/CAPC to get more detailed information.

See Overview - All Networks/Servers (see page 82) for more information on the health statuses.

3. Navigate to the overview data for a specific client subnet/server you are monitoring: Investigator, Metric Browser tab, Networks or Server node, a client subnet or specific server, Overview tab.

Use the health status information or other metrics to determine if a client subnet or server requires further investigation. For example, if the data shows that the server hosting your troubled applications is performing as expected, then you may choose to investigate the application in more detail using APM WebView.







See Overview - Specific Network/Server (see page 83) for more information on this overview data.



Network Status Information Dashboard

The Network Status Information dashboard is available from the WebView Console. It shows the 10 worst performing client subnets and servers with the associated health statuses. At a glance, you can see if a critical client network or server is not performing well and link to CA Performance Center (NPC)/CA Performance Center (CAPC) for more information. After configuring the More Information buttons from APM Workstation, double-clicking them takes you to the client subnet/server overview reports in NPC/CAPC. Each button requires a one-time configuration.

The Y-axis represents the following:

The health status of each client subnet/server for the specified time frame (default view is for live data) as calculated by CA Application Delivery Analysis. Enterprise Manager/MOM takes the CA Application Delivery Analysis health status data and displays corresponding numerical values in the Workstation. Refer to the following table for a data mapping between the two systems.

CA Application Delivery Analysis Status WebView Status Value

Unavailable 4

Excessive 3

Degraded 2

Normal 1

Unrated 0

None -1 (The corresponding client subnet/server is not reporting into Enterprise Manager)

For more information on configuring the More Information button, see

Configure More Information on Network Status Information Dashboard (see page 81)

For information on how Application Delivery Analysis calculates network and server health status, see

How ADA Calculates Network and Server Health (see page 86)



Configure More Information on Network Status Information Dashboard

The More Information buttons take you to the CA Performance Center (NPC)/CA Performance Center (CAPC), specifically the Network Overview and Servers Overview reports. Links to these reports require a one-time configuration for each button. Configure the buttons on the APM Workstation.

Follow these steps:

1. Log on to the APM Workstation

2. On the Workstation Console widow, select Dashboard and Edit Dashboard.

The Editor view of the Network Status Information dashboard appears.

3. Right-click the More Information button and select Ungroup.

4. Right-click the More Information text and select Object Links...

The Object Links window appears.

5. Click Edit.

The Edit Object Link window appears.

6. Verify that the Web Link radio button is selected.

7. In the URL text box, replace <hostname> with the name of your NPC/CAPC server.\

Note: The URL defaults to accessing NPC. To access CAPC, change the default so it includes your CAPC port number (typically 8181) and the new address.

To access additional network information in CAPC, replace:

http://<hostname>/npc/default.aspx?pg=6001&mn=6001

with

http://<hostname>:CA Portal/pc/desktop/?pg=2000009&mn=3

To access additional server information in CAPC, replace:

http://<hostname>/npc/default.aspx?pg=7006&mn=6003

with

http://<hostname>:CA Portal/pc/desktop/?pg=2000010&mn=3

8. Click OK on both the Edit Object Link and Object Links windows.

9. Select File, Save on the Editor view of your report.

10. Close the Editor view.

You and all subsequent users of the Network Status Information dashboard can now directly access the associated overview reports in NPC/CAPC.



Overview - All Networks/Servers

Overview data associated with all the networks/servers being monitored is accessible from: APM WebView, Investigator, Metric Browser tab, Networks or Server node, Overview tab. The Overview page shows the following information, sorted by descending order of the Status metric value by default:

Network/Server Name

Name of the network/server as displayed in the tree hierarchy.

Status



Unavailable 4

Excessive 3

Degraded 2

Normal 1

Unrated 0


Default thresholds are defined for two Status metric values. Caution corresponds to the status value of 2. Danger corresponds to the status value of 3. When a metric value crosses the caution threshold, the Status cell background color shows yellow. When it crosses the danger threshold, the Status cell background color shows red. You can customize these thresholds by editing the ADAExtensionforAPM.tv.xml file. This file is located in the <EM_HOME>\ext\xmltv folder of the CA Application Delivery Analysis Extension for APM installer program.





Overview - Each Network/Server

This Overview page shows data associated with the client subnet or a specific server. This information is accessible from: APM WebView, Investigator, Metric Browser tab, Networks or Server node, a client subnet or specific server, Overview tab.







The Overview page shows the following information:

Status



Unavailable 4

Excessive 3

Degraded 2

Normal 1

Unrated 0




Data Transfer Time (ms) Data Transfer Time measures the time it takes to transmit a complete application response measured from the first response (the end of the Server Response Time) to the last packet sent in that request. The response time can be impacted by the design of the application, the performance of the server or the network. Excludes the initial server response time and includes only Network Round Trip Time if there is more data to send than fits in the TCP window.

Network Round Trip Time (ms) Network Round Trip Time measures the time that a packet takes to travel between the server and clients on a network, excluding loss. Application, server, and client processing time are excluded.

Retransmission Delay (ms) Retransmission Delay measures the elapsed time between the original packet send and the last duplicate packet send. Retransmission Delay is reported as an average across observations and not just for the retransmitted packets. If one packet in a set of 10 requires 300 ms of retransmission time, the Retransmission Delay is reported as 30 ms (300 ms/10 packets).

Server Response Time (ms)

Server Response Time measures the time it takes for a server to send an initial response to a client request or the initial server "think time." Increases in the Server Response Time generally indicate a lack of server resources such as CPU, memory, disk, or I/O, a poorly written application, or a poorly-performing tier in a multi-tier application.




If the status or metrics data show healthy networks/servers but the associated application performance is still degraded, one option is to continue triaging the application from APM WebView.

Follow these steps:


Use the Console or Investigator to triage your issue.



Continue Triaging from NPC/CAPC

If the health status or metrics data show degraded networks/servers, one option is to investigate infrastructure issues in more detail using CA Performance Center (NPC)/CA Performance Center (CAPC). Access NPC/CAPC using one of the following steps.

Follow these steps:

1. From the Network Status Information dashboard, select the associated More Information button to access the client subnet/server overview reports in NPC/CAPC.

2. Log on to NPC/CAPC and use the search function to get more information about the network/server.

See the CA Performance Center Administrator and User Guide for information on using NPC/CAPC.

Network Data Time Lag

Network and server data on APM WebView has an approximate 5 minutes time lag from the CA Application Delivery Analysis Management Console. The Management Console can connect to several collectors, such as Multi-Port Monitors and single port CA Application Delivery Analysis collectors. To allow for aggregation of the collected data, CA Application Delivery Analysis time bins are 5 minutes wide and end at 5 minute boundaries, for example 7:00, 7:05, and so on. CA Application Delivery Analysis Management Console updates its database every 5 minutes. As a result, the web services bridge between CA Application Delivery Analysis Management Console and CA APM retrieves network health data with a lag of up to 5 minutes for a 5 minute time range. For example, if the current time is 6:22 PM, then the data request would be for time starting at 6:15 PM and time ending at 6:20 PM. Data points on APM WebView between these two times will show the same result.

The following is a sample log message from the web service:

6/15/11 06:22:00.175 PM IST [INFO] [pool-1-thread-2] [ADAConnector] Calling ADA

web service...

6/15/11 06:22:00.175 PM IST [INFO] [pool-1-thread-2] [ADAConnector]

utcStartTime: 2011-06-15T18:15:00.000+0530

6/15/11 06:22:00.175 PM IST [INFO] [pool-1-thread-2] [ADAConnector] utcEndTime:

2011-06-15T18:20:00.000+0530



Tool Tip Data

Tool tips are available on APM WebView graphs, such as those on the Network Status Information dashboard and Overview pages. Hover your mouse over the data point on the graph to get more information from the tool tip. Note that the following tool tip field values correspond to the health status data value on the Y-axis for the selected time slice:

■ Value of the metric

■ Minimum and maximum values of the metric

CA Application Delivery Analysis collects data at 5 minutes intervals, but the integration bridge between CA Application Delivery Analysis and CA APM sends only one data point at 15 second intervals. Therefore, the Workstation displays the same data value until it gets a new one from CA Application Delivery Analysis. This causes the count on the number of data points reported in the selected time slice to always display 1. When CA APM agents send data, they send more than one data points at 15 second intervals. This allows APM WebView to average out the data and show different values for Value, Min and Max on application metrics.

How ADA Calculates Network and Server Health

CA Application Delivery Analysis rates the health of networks/servers by observing its TCP transactions and calculating the following:

■ Network metrics for each client network that communicates with the application. If the 5-minute average for a Network metric exceeds the threshold, and CA Application Delivery Analysis observed the metric a minimum number of times, CA Application Delivery Analysis rates the corresponding 5-minute interval for the client network as Degraded or Excessive and creates a Network incident.

■ Server metrics for each server that hosts the application. If the 5-minute average for a Server metric exceeds the threshold, and CA Application Delivery Analysis observed the metric a minimum number of times, CA Application Delivery Analysis rates the corresponding 5-minute interval for the server as Degraded or Excessive and creates a Server incident.

To rate performance data, the CA Application Delivery Analysis Management Console must collect 2 full business days of data. A business day is calculated from GMT midnight to midnight. For example, if the CA Application Delivery Analysis Management Console begins collecting data for a TCP session between a server port and client network on Monday at 3:30 p.m. EST, CA Application Delivery Analysis cannot rate the performance of the application on that network until 7:00 p.m. EST on Wednesday (midnight GMT). If the CA Application Delivery Analysis Management Console has not collected 2 full business days of data, CA Application Delivery Analysis classifies the TCP sessions between the server port and client network as Unrated.

How to Triage Application Issues Starting from NPC



Application data on the CA Performance Center (NPC)/CA Performance Center (CAPC) allows diagnosers to do the following from the NPC/CAPC UI:

■ Look at the health statuses of application and business services.

■ Drill down to defects and more detailed metrics.

■ If the application metrics show the expected performance for your business, you can look at the web server or client associated with the defect you are triaging.

The following illustration describes some options for how, as a diagnoser, you triage application issues starting from NPC/CAPC.

As a diagnoser, perform the following steps (steps 2 and 3 are dependent on the metrics for your application and your triaging decision):



3. Continue Triaging from NPC/CAPC (see page 98).




When you see application performance concerns on the NPC/CAPC UI, determine some triaging options to help guide your next steps.

Follow these steps:

1. Log on to NPC/CAPC.

2. Open one of the following dashboards from the Application Health menu: APM - Applications Summary or APM - Business Services Summary.

Use the health status information in the Status field to determine which application or business service requires further investigation.

See APM - Applications Summary dashboard (see page 90) for detailed information on this dashboard.

See APM - Business Services Summary dashboard (see page 91) for detailed information on this dashboard.

3. View the APM - Business Transactions Summary report by drilling down from the APM - Applications Summary or APM - Business Services Summary dashboard.

The Business Transactions Summary report shows the health status of business transactions for the selected business service. Use the health status information in the Status field to determine which business transaction requires further investigation.

See APM - Business Transactions Summary report (see page 91) for detailed information on this report.



4. View the APM - Metrics and Incidents Summary report by drilling down from the APM - Business Transactions Summary report.

The APM - Metrics and Incidents Summary report shows Business Transaction Component (BTC) metrics and customer experience metrics (shown as RTTM on the UI) for the selected business transaction.

Use the business transaction metrics component and customer experience metrics (RTTM) to determine how you want to proceed. For example, if the RTTM and BTC metrics show high average response times, errors per interval, and/or stall counts, you may choose to investigate the application in more detail by logging on to the Workstation. If the the RTTM and BTC metrics are within the expected range for your business, you may choose to select the Client IP Address or Web Server address associated with a defect. This option allows you to investigate network issues related to the defect.

See APM - Metrics and Incidents Summary report (see page 92) for detailed information on this report.

5. View the APM - Defects Summary report by drilling down from the APM - Metrics and Incidents Summary report.

The APM - Defects Summary report shows the last ten defects and their related details for the selected incident.

See APM - Defects Summary report (see page 95) for detailed information on this report.

How NPC/CAPC Displays Application Data

Application data on CA Performance Center (NPC)/CA Performance Center (CAPC) represents application health data that are collected by CA APM. A web services integration bridge makes the data available to NPC/CAPC. CA APM monitors application health by measuring the performance of individual methods executed by various application components. Probes inserted into application component byte code report data to agents, which in turn report data to the Enterprise Manager. Other subsystems, like JMX and PMI, also report data collected by agents. Enterprise Manager compiles this data into metrics—application performance as measured at many points in the application subsystems. CA APM makes associations between applications, business services, and business transactions based on observed transactions related to the application.

NPC/CAPC displays application health and performance status data in a drill-down fashion for a selected time period. When CA APM is registered as a data source on NPC/CAPC, you can access application data from the Applications Summary report or Business Services Summary report. From these reports, you can drill down to the defects.



Application health and performance status data are sectioned into the following categories:

Applications

Indicates the health status of the applications CA APM monitors. Selecting an application shows the business services being monitored.

Business Services

Indicates the health status of the business services for the selected application. Selecting a business service shows the business transactions CA APM monitors.

Business Transactions

Indicates the health status of the business transactions for the selected business service. Selecting a business transaction displays the customer experience metrics (shown as RTTM on the UI) and Business Transaction Component (BTC) Metrics and incidents.

Incidents

Represents the group of defects that are correlated based on transaction type and defect type. Selecting an incident shows the last N (where N = 10 max) defects.

Defects

Displays information specific to each defect. Selecting the web server IP address or client IP address associated with each defect takes you to the search result page for the respective server or client address.

Note: For information about CA Performance Center/CA Performance Center and its UI components, see the CA CA Performance Center Administrator and User Guide.

APM - Applications Summary Dashboard

The APM - Applications Summary dashboard page shows the health status of business applications. Access this dashboard from the Application Health menu.

CA APM monitors the performance and health of Java, J2EE, and .NET applications. The front-ends are referred to as applications.

A business application is a software program that automates a business service. CA APM monitors web transactions, which are the product of web applications. A business application is part of the transaction hierarchy.

The Application Status view on this dashboard shows the following information:

Applications

Lists the CA APM monitored applications. Only applications with defined business transaction components are displayed in this report. Select one to see the associated business services.



Status

The health status of the application for the specified time range. Use this information to determine which application requires further investigation. The colors represent:

■ White - No data because Enterprise Manager is not responding (no metric value)

■ Gray - No data (metric value: 0)

■ Green - Good (metric value: 1)

■ Yellow - Caution (metric value: 2)

■ Red - Danger (metric value: 3)

APM - Business Services Summary

The APM - Business Services Summary dashboard page shows the health status of business services for the selected application. Drill down from an application or navigate directly from the Application Health menu to access this dashboard.

A CA APM business service is a group of business transactions. Measurements are aggregated to this level in the transaction hierarchy.

The Business Service Status view on this dashboard shows the following information:

Business Services

Lists the business services for the selected application. Select one to see the associated business transactions.

Status

The health status of the business service for the specified time range. Use this information to determine which business service requires further investigation. The colors represent:






APM - Business Transactions Summary

The Business Transactions Summary report shows the health status of business transactions for the selected business service. Drill down from the APM - Applications Summary or APM - Business Services Summary to view this report.



The term business transaction describes a sequence of back-to-back, computer-generated transactions. They do not include user-generated transactions that can add varying client behavior (think time) to the transaction. A business transaction consists of an identifying transaction and a number of other related transactions which can be executed in order. Transactions can be designated as included, cache-able, or both. Business transactions are defined in the CEM console.

Note: For more information on defining and creating business transactions, see the CA APM Transaction Definition Guide.

The Business Transaction Status view on this report shows the following information:

Business Transactions

Lists the business transactions for the selected service. Select one to see the associated customer experience metrics (shown as RTTM on the UI) and Business Transaction Component (BTC) metrics and incidents.

Status

The health status of the business transactions for the specified time range. Use this information to determine which business transaction requires further investigation. The colors represent:






APM - Metrics and Incidents Summary

The APM - Metrics and Incidents Summary report shows Business Transaction Component metrics and customer experience metrics (shown as RTTM on the UI) for the selected business transaction. CA APM agents report Business Transaction Component metrics per business transaction. These metrics are sometimes called BLAME metrics. TIMs collect customer experience metrics per business transaction and send them to the Enterprise Manager.

See Business Transaction Component metrics (see page 93) for more information.

See Customer Experience metrics (see page 94) for more information.



Business Transaction Component Metrics

CA APM agent reports five Business Transaction Component metrics per business transaction. These five metrics are sometimes referred to as BLAME metrics. The BTC views include the following metrics:

Average Response Time (ms)

Response Time is the time it takes for a request to complete. This time provides a basic measurement of application response speed. Therefore:

■ Low response times are desirable.

■ High response times suggest a problem.

The Average Response Time metric averages the response times of all requests that were completed during an interval.

Note: The count for Average Response Time is identical to the value of Responses Per Interval.

Responses Per Interval

Responses Per Interval reflects the number of invocations finished in that interval. It is a measure of data throughput and thus of application performance. Generally:

■ A high number is desirable.

■ A low number is undesirable.

■ An unexpected spike in responses could indicate overuse of the external system, such as a denial of service attack on a website.

Concurrent Invocations

Invocations are requests handled by the application and its various parts. Concurrent invocations are the requests being handled at a given time.

CA APM calculates the Concurrent Invocations metric by counting the number of requests which were still being handled at the end of a particular interval.

■ A low Concurrent Invocations value is desirable.

■ A high Concurrent Invocations value suggests a problem.



Errors Per Interval

Errors are the number of exceptions reported by JVM and HTTP error codes. Examples of errors include:

■ a 404 Page Not Found status reported by the HTTP server

■ a SQL exception

■ a Java exception

A low error count is desirable.

Stall Count

Stalled requests are those which have not completed within a specified time threshold. If a request is counted as stalled, that does not mean it is hung and will never be completed, but that its execution exceeded the stall threshold.

■ A low count is desirable.

■ A high count is undesirable.

The default stall threshold is 30 seconds.

Information on stall events is stored in the Transaction Events database.

Customer Experience Metrics

TIMs collect customer experience metrics (shown as RTTM on the UI) per business transaction and send them to the Enterprise Manager. If more than one TIM monitors the same business transaction, these metrics are aggregated on the Enterprise Manager.

Customer experience includes the following metrics:

Average Response Time (ms)

For each interval, the average time it took to execute the business transaction, in milliseconds.

Total Defects Per Interval

Number of defects for all defect types for a business transaction, aggregated across TIMs.

Total Transactions Per Interval

Total number of transactions for the business transaction, aggregated across TIMs, per interval.



Defect Types

Customer experience metrics (sometimes shown as RTTM on the product UI) are grouped into several defect types. They can appear under any of these types, which are the default names of defects before users customize them.

Defect metrics will be collected for each defect type associated with the business transaction, including user-named transactions -- such as "Slow time for <BT_Name>".

Following are the default values for each defect type, where s = second.

Slow Time

Transaction Time > 5.000 s

Fast Time

Transaction Time < 0.005 s

High Throughput

Throughput > 100.0KB / s

Low Throughput

Throughput < 1.0KB/ s

Large Size

Transaction Size > 100.0KB

Small Size

Transaction Size < 0.1KB

Missing Transaction

Component Timeout = 10.000 s

How Customer Experience Metrics are Calculated

Customer experience transaction metrics are calculated using Javascript calculators on the Enterprise Manager

NOTE: Aggregated metrics are calculated only on a collector Enterprise Manager with a running TIM Collection Service and BTstats processor. These calculations are not run on a MOM Enterprise Manager.

Defects Summary Report

The APM - Defects Summary report shows the last ten defects and their related details for the selected incident.



A defect is the failure of a transaction to conform to customer expectations and transaction specifications. Defects are categorized as behavioral and response defects. If a transaction does not meet multiple specifications, then multiple defects are generated (for example, slow time and missing components).

The Defects Summary report shows the following information:

Defect ID

Identification number for each defect

Defect Name

Name associated with the defect

Business Services

The associated business service for the defect

Business Transaction

The associated business transaction for the defect

Date and Time

Date and time the defect occurred

Value

The baseline value at which if greater than or equal to, CA APM considers the transaction defective. Configure this baseline throughput value that triggers the defect from the following CEM console page:

Administration, Business Services, (a business service), (a business transaction), Business Transaction Specifications



Business Impact

The business impact is the measure that a defect or an incident has on the business.

CEM console assigns a business impact to each incoming defect, based on the defect associated with the business transaction, defect type, and user.

The business impact of a defect is calculated as follows:

Business transaction weight * defect type weight * user weight

For example, if the following impact level is assigned to each value:

business transaction weight = 4

defect type weight = 4

user weight = 4

Then 4 * 4 * 4 = 64

The business impact is 64.

This impact level … Is assigned this weight …

Minimum 1

Very low 2

Low 3

Medium 4

High 5

Critical 6

Trigger immediately 7

Login Name

The login name of the associated end user for the defect

User Group

Name of the affected user group for the defect

In CA APM, a user group allows you to configure settings for a collection of (monitored) users. You do not need to configure the settings for each individual user separately. User groups can be defined so you can easily identify (monitored) user populations that are likely be experiencing problems. A user belongs to only one user group.

Client IP Address

The client IP address of the end user affected by the defect

Click to access more detailed information about the client. You are directed to the search results page on NPC/CAPC for this client IP address.



Web Server IP Address

The IP address of the requesting web server associated with the defect

Click to access more detailed information about the web server. You are directed to the search results page on NPC/CAPC for this web server IP address.

Web Server MAC Address

The hardware address of the network card for the server associated with the defect


If the RTTM and BTC metrics in NPC/CAPC show high average response times, errors per interval, or stall count for your business, one option is to continue triaging from APM WebView. Use APM WebView to get more information about your application.

Follow these steps:


Use the Console or Investigator to triage your issue.

Continue Triaging from NPC/CAPC

If the RTTM and BTC metrics in CA Performance Center (NPC)/CA Performance Center (CAPC) are within the expected range for you business (but you still see performance concerns in the Applications or Business Services dashboard), one option is to investigate network issues related to the defect. You can use NPC/CAPC to perform this investigation.

Follow these steps:

1. From the APM - Defects Summary report, do one of the following:

1. Select the Client IP Address link to connect to NPC/CAPC and get more detailed information about the client.

2. Select the Web Server IP Address link to connect to NPC/CAPC and get more detailed information about the web server.

2. Use the detailed Client or Web Server information to triage network issues related to your application.

See the CA Performance Center Administrator and User Guide for information on network metrics.


Appendix A: Troubleshooting


CA APM Application Data Not Available on NPC (see page 99) CA APM Application Data Not Available on CAPC (see page 100) TIM Stops Working (see page 100) Infrastructure Data not Available on CEM Console (see page 103) More Information Buttons on Workstation Do Not Work (see page 103)

CA APM Application Data Not Available on NPC

Symptom:

After selecting the application-related reports (Business Services Summary or Applications Summary), I do not see any CA APM data in CA Performance Center.

Solution:

Verify the following:

■ You have installed CA Performance Center Integration Pack (see page 62) on the Enterprise Manager or MOM.

■ You have started the APM-CAPC service (see page 55).

■ You have updated the CA Performance Center database (see page 65).

■ You have registered APM as a data source (see page 66) in CA Performance Center.

■ You have created application triage map alerts (see page 64).

For instructions on registering data sources, see

Register CA APM as a Data Source (see page 66)

For information on configuring application map alerts, see

Configure Alerts on APM WebView (see page 64)

CA APM Application Data Not Available on CAPC


CA APM Application Data Not Available on CAPC

Symptom:

After selecting the application-related reports (Business Services Summary or Applications Summary), I do not see any CA APM data in CA Performance Center.

Solution:

Verify the following:

■ You have installed CA Performance Center Integration Pack (see page 53) on the Enterprise Manager or MOM.

■ You have started the APM-CAPC service (see page 55).

■ You have imported the APM views (see page 56) into CA Performance Center.

■ You have registered APM as a data source (see page 57) in CA Performance Center.

■ You have added the APM dashboards (see page 58) to the Application Health menu in CA Performance Center.

■ You have created application triage map alerts (see page 55).

For instructions on registering data sources, see

Register CA APM as a Data Source (see page 66)

For information on configuring application map alerts, see

Configure Alerts on APM WebView (see page 64)

TIM Stops Working

Symptom:

The TIM installed on the Multi-Port Monitor has stopped functioning properly. For example, it has stopped recording and generating statistics. Additionally, I see "skip old packets" messages in the TIM log.

Solution:

When Tim is installed on Multi-Port Monitor, the NapaTech card on Multi-Port Monitor marks the packet arrival time using the time on that card. If the system time on the Multi-Port Monitor and the NapaTech card time are significantly different, then TIM can stop functioning properly.

TIM Stops Working


Two possible use cases exist. Determine which use case applies to your situation.

1. TIM processing can sometimes lag behind the packet files generated by the Multi-Port Monitor. For example, if TIM is stopped and restarted or the Multi-Port Monitor is generating packet files faster than TIM can consume. Confirm TIM lag time by doing the following:

a. Confirm that the NapaTech card time synchronizes with your system time on Multi-Port Monitor.

b. Look at the Multi-Port Monitor System Status page and verifying that it does not display a warning message.

If you have confirmed these two scenarios, then there is likely nothing wrong with TIM. TIM does not process packet files that are older than 15 minutes (this default value can be changed). After it skips these old packet files, TIM resumes normal processing. TIM simply needs time to catch up with the Multi-Port Monitor generated files.

2. Compare the NapaTech card time to that of your system time on Multi-Port Monitor. Use the following command from the terminal to see the NapaTech card time:

/opt/napatech/bin/TimeConfig -cmd time_get

Use the following command from the terminal to see the system time on Multi-Port Monitor:

date

If the two times are different and the Multi-Port Monitor System Status page displays a warning message, then look at the times on the NapaTech card and Network Time Protocol (NTP) server.

Select the time zone at the following website to get NTP time:

http://www.time.gov/

Consider the following scenarios and determine which one applies to your situation.

Scenario 1

Conditions

– The Napatech card time is vastly different from the NTP time (more than 15 minutes)

– The system time on Multi-Port Monitor is minimally different from the NTP time (less than 5 seconds)

TIM Stops Working


Actions

– Synchronize the NapaTech time to the system clock by running the following command:

/opt/NetQoS/scripts/syncNapatechClock

– If the NapaTech time is different from the system time on Multi-Port Monitor by less than 5 minutes, then the NapaTech driver OS synchronization will gradually adjust the NapaTech clock. If the NapaTech time is different from the system time on Multi-Port Monitor by more than 5 minutes, then the NapaTech time will synchronize with the system time on the Multi-Port Monitor immediately.

Scenario 2

Conditions

– The NapaTech card time is minimally different from the NTP time.

– The system time on Multi-Port Monitor and CEM console time is vastly different from the NTP time.

Actions

– Adjust the CEM console time to synchronize with the NTP time.

– Wait and verify that the system time on Multi-Port Monitor is set by CEM and is also synchronized with the NTP time.

– Confirm that the ntpd process on Multi-Port Monitor is running. If it is not running, start it.

The ntpd process can stop automatically when the system time on the Multi-Port Monitor is different from the NTP time by more than 1000 seconds.

Scenario 3

Conditions

– The NapaTech card time is vastly different from the NTP time.

– The system time on the Multi-Port Monitor and CEM console time are also vastly different from the NTP time.

Actions

– Adjust the CEM console time to synchronize with the NTP time.

– Wait and verify that the system time on Multi-Port Monitor is set by CEM and is also synchronized with the NTP time.

– Confirm that the ntpd process on Multi-Port Monitor is running. If it is not running, start it.

– Synchronize the NapaTech time to the system clock by running the following command:

/opt/NetQoS/scripts/syncNapatechClock

Infrastructure Data not Available on CEM Console


Infrastructure Data not Available on CEM Console

Symptom:

Looking at defect details in which I know there should be associated network infrastructure information, I do not see this information.

Solution:

Verify that you have configured the following correctly:

■ The Multi-Port Monitor Enabled check-box on the CEM console UI (Monitors, Multi-Port Monitor machine) is enabled to initiate the web service call to the Multi-Port Monitor for the TCP data.

■ The defect was generated more than 5 minutes ago. There can be a delay of up to 5 minutes before the network health data is available in the Multi-Port Monitor database. If the defect was generated less than 5 minutes ago, wait a few minutes and then refresh the browser page.

More Information Buttons on Workstation Do Not Work

Symptom:

I cannot connect directly to CA Performance Center (NPC)/CA Performance Center (CAPC) from the Network Status Information dashboard on CA APM Workstation/WebView. The More Information buttons on this dashboard do not work.

Solution:

The More Information buttons take you to the NPC/CAPC (specifically the Network Overview and Servers Overview reports). Links to these reports require a one-time configuration for each button. See Configure More Information on Network Status Information Dashboard (see page 81) .

For instructions on configuring the More Information buttons, see

Configure More Information on Network Status Information Dashboard (see page 81)

ca application performance management performance center 2 3 00-linux... · ca application...

Documents