apm_9.5 infrastructure mgmt integ

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.

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 NetQoS 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 NetQoS 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 NetQoS Performance Center/CA Performance Center

This integration allows you to view CA APM application data on the NetQoS Performance Center. See How to Connect CA APM to NetQoS 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.

P o r t 5 0 0 1

P o r t 5 0 0 1

P o r t 5 0 0 1

P o r t 5 4 3 2

P o r t 5 4 3 2

P o r t 8 0

P o r t 8 0 8 1

P o r t 5 0 0 1

P o r t 5 4 3 2

P o r t 5 2 5 0

P o r t 8 0 8 0

P o r t 8 0

P o r t 8 0

C E M C o n s o le

In t r o s c o p e

W o r k s ta t io n

In tr o s c o p e

W e b V ie w

E E M

M O M

C o lle c to r

C o lle c to r

A P M

d a ta b a s e

P o rts in u s e :

8 0

5 0 0 1

5 2 5 0 (E E M )

5 4 3 2

5 4 4 3 ( if H T T P S

w h e r e 5 0 0 1 is u s e d )

8 0 8 0

8 0 8 1

A g e n t

P o r t 8 0 8 0

P o r t 8 0

P o r t 8 0 8 0

P o r t 8 0

P o r t 8 0

P o r t 8 0

A p p lic a t io n D e liv e r y A n a ly s is

(A D A )

N e tQ o S P e r fo r m a n c e

C e n te r

M u lt i-P o r t C o lle c to r

N O T E : T h e p o r t d ir e c t io n s in d ic a t e

t h e in it ia t io n o f c o n v e r s a t io n o n ly ,

n o t t h e t r a ff ic f lo w . A u n i-

d ir e c t io n a l p o r t m a y h a v e d a ta

p a s s in g in b o t h d ir e c t io n s .

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 NetQoS 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 NetQoS 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 NetQoS 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://:8081

where 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.

As an administrator, perform the following steps:

1. Run installer program (see page 46).

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

3. Synchronize time (see page 49).

4. Verify the connection (see page 50).



Prerequisites

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

CA Application Delivery Analysis 9.1 or newer

NetQoS Performance Center 6.1/CA Performance Center 2.0

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

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=

Enterprise Manager port number

com.wily.apm.adaconnector.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=

com.wily.apm.adaconnector.ada_hostName1=

Name of the installer program

com.wily.apm.adaconnector.ada_processName1=

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=

is an index of your ADA Manager. The first ADA Manager corresponds to , second Management console corresponds to , 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:

\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 NetQoS 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.



Verify the Connection

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

Data Transfer Time




By default, the following metrics are disabled:

Data Transfer Time




To enable these metrics, use the com.wily.apm.adaconnector.ada_enhancedmetrics_enabled1= 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 NetQoS 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 illustratio

apm_9.5 infrastructure mgmt integ

Documents

ca software

ca database performance

ca copyright notices

proprietary information

applicable license agreement

software products

available copies

internal use