apm_9.5--transaction generator implementation guide

8/11/2019 APM_9.5--Transaction Generator Implementation Guide

1/107

Transaction Generator Implementation

GuideRelease 9.5

CA Application PerformanceManagement


2/107

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, withoutthe 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 totheir respective companies.


3/107

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 ServerAgents (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 forIBM 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)


4/107

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)


5/107

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. Athttp://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 [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/supporthttp://www.ca.com/supporthttp://www.ca.com/supportmailto:[email protected]:[email protected]:[email protected]://www.ca.com/docshttp://www.ca.com/docshttp://www.ca.com/docshttp://www.ca.com/docsmailto:[email protected]://www.ca.com/support


6/107


7/107

Contents 7

Contents

Chapter 1: The CA APM Transaction Generator 11

CA APM TG monitoring architecture .......................................................................................................................... 11

Addressing the 3 A.M. problem .......................................................................................................................... 11

CA APM TG features ................................................................................................................................................... 12

Load ramping ...................................................................................................................................................... 12

Script creation and maintenance ........................................................................................................................ 13

Integration with CA Introscope ......................................................................................................................... 13

Integration with the CA Customer Experience Manager .................................................................................... 14

Chapter 2: Installing the CA APM Transaction Generator 15Before you begin ........................................................................................................................................................ 15

Operating system requirements ......................................................................................................................... 15

Additional operating system support for the CA APM TG agent ........................................................................ 16

Recommended minimum hardware requirements ............................................................................................ 16

Installing the CA APM Transaction Generator ........................................................................................................... 17

CA APM TG components ..................................................................................................................................... 17

Installing CA APM TG on Windows...................................................................................................................... 18

Installing CA APM TG on Linux ............................................................................................................................ 20

Displaying CA APM TG information in CA Introscope Investigator ................................................................... 21

Managing CA APM TG user access in a standalone configuration ...................................................................... 24

Displaying CA APM TG agent availability in CA CEM ........................................................................................... 26

CA APM TG agent startup settings ............................................................................................................................. 26

Installing CA APM TG-specific CA Introscope components ...................................................................................... 27

Installing CA Introscope tab views .................................................................................................................... 28

The Command line and the CA APM TG agent ........................................................................................................... 28

Linux DHCP considerations ......................................................................................................................................... 29

Chapter 3: Configuring the CA APM Transaction Generator Agent 31

Overview of configuring agents ................................................................................................................................. 31

Setting Hierarchy ................................................................................................................................................. 32

The CA APM TG Agent Configuration ......................................................................................................................... 32

The Dashboard tab .............................................................................................................................................. 33

The Connect to Agent tab .................................................................................................................................. 35

Configuring the CA APM TG agent ...................................................................................................................... 37

Using Configuration Tab buttons ........................................................................................................................ 41

Groups and scripts...................................................................................................................................................... 42


8/107

8 Transaction Generator Implementation Guide

The Scripts By Group tab ..................................................................................................................................... 43

The All Scripts tab................................................................................................................................................ 47

Working with scripts in the Script Requests page ............................................................................................... 49

Viewing script request details ............................................................................................................................. 50

Testing a script .................................................................................................................................................... 51

Sending scripts to CA CEM .................................................................................................................................. 52

Load ramping ...................................................................................................................................................... 52

Viewing status messages .................................................................................................................................... 55

Chapter 4: Creating and Editing CA APM TG Scripts 57

Starting the Script Editor ............................................................................................................................................ 57

Creating a script .................................................................................................................................................. 58

Using the Script Recorder ........................................................................................................................................... 59

Configuring the Script Recorder .......................................................................................................................... 59

Starting the recording session............................................................................................................................. 63

Logically grouping requests using Set Request ID ............................................................................................... 67

Monitoring web services ..................................................................................................................................... 68

Using a script template .............................................................................................................................................. 69

Manually creating scripts ........................................................................................................................................... 70

Specifying script parameters ............................................................................................................................... 71

Specifying requests ............................................................................................................................................. 71

Specifying request tags ....................................................................................................................................... 72

Specifying conditions .......................................................................................................................................... 73

Checking syntax ................................................................................................................................................... 74

Deploying scripts to multiple agents .......................................................................................................................... 74

Copying a single script at a time ......................................................................................................................... 74

Manually copying multiple scripts ...................................................................................................................... 74

Securing scripts .......................................................................................................................................................... 76

Securing access to the Script Editor ........................................................................................................................... 77

XML tag syntax ........................................................................................................................................................... 78

XML special character substitutions........................................................................................................................... 83

Script samples ............................................................................................................................................................ 83

Basic script sample .............................................................................................................................................. 84

Script conditions and content variables .............................................................................................................. 84

Script reserved variables ..................................................................................................................................... 86

Reserved variable sample ................................................................................................................................... 87 samples ................................................................................................................................................ 88

Stopping a script using the tag or stop attribute .................................................................................... 89

Chapter 5: Viewing CA APM TG Metrics 91

Viewing CA APM TG data with CA Introscope .......................................................................................................... 91


9/107

Contents 9

CA APM TG agent metrics in CA Introscope ...................................................................................................... 92

Other metrics ...................................................................................................................................................... 92

CA APM TG-specific tab views ............................................................................................................................. 95

Viewing CA APM TG data with CA CEM ...................................................................................................................... 96

Identifying CA APM TG transactions ................................................................................................................... 96

CA APM Transaction Generator to CA CEM integration terminology ................................................................. 96

Appendix A: Configuring the RTM Server 99

Appendix B: CA APM TG command line utility (WTGUtil) 101

Basic command description ..................................................................................................................................... 101

WTGUtil Command syntax ................................................................................................................................ 102

Examples ........................................................................................................................................................... 103

Trace messages ................................................................................................................................................. 103

Index 105


10/107


11/107


Chapter 1: The CA APM Transaction

Generator

CA Application Performance Management Transaction Generator (CA APM TG) is an

intelligent, programmable agent that helps you monitor the availability, health, and

performance of web sites and web services from the perspective of a user attempting to

access web sites. The CA APM TG agent generates synthetic transactions that you can

monitor using CA Customer Experience Manager (CA CEM) and CA Introscope. Use the

load ramping feature of CA APM TG to generate a load against a web application to test

how well the application handles changes in the load.

When operational issues arise during business hours, any amount of down time can

mean a significant loss of revenue and a significant reduction in customer satisfaction.

By using synthetic transactions to identify problems during off-hours, you can find andfix problems before real users and customers are affected.

This section contains the following topics:

CA APM TG monitoring architecture(see page 11)

CA APM TG features(see page 12)

CA APM TG monitoring architecture

The CA APM TG agent uses scripts to run synthetic transactions against LAN or WAN

web sites and web services for an organization. When you send these scripts to CA CEMfor monitoring, CA CEM automatically creates business processes and business

transactions from the scripts. CA CEM then monitors the synthetic transactions to

determine the overall health of the selected web sites and web services and to

proactively address issues within a web site or web application before real users are

affected. For more information about integrating CA APM TG with CA CEM, seeViewing

CA APM TG data with CA CEM (see page 96)

Addressing the 3 A.M. problem

The 3 A.M. problem occurs when maintenance of web sites and web services is

performed during off hours, while there is little to no traffic to a specific web site orapplication. If a problem occurs during maintenance, it is often not detected until the

start of the business day due to a lack of monitoring. This leads to loss of revenue and

bad customer experience.


12/107

CA APM TG features


When no one is using a web site or web application, CA CEM and CA Introscope cannot

measure its availability and performance because no transactions are being monitored.

When a problem occurs, IT support personnel have no information to begin

investigating the problem and finding the solution. CA APM TG helps you address the 3

A.M. problem.

The synthetic transactions you create with CA APM TG are an essential component of an

overall application monitoring strategy. Should a problem occur during off hours,

synthetic transaction data viewed through the CA Introscope Workstation or CEM

console indicates where a problem is located and how to best resolve the situation.

With the alert capabilities of CA Introscope and the incident reporting features of CA

CEM, you can assess the problem before the start of business and implement a solution

before any real users are impacted.

CA APM TG features

CA APM TG is easily integrated into a web application monitoring system using CA

Introscope and CA CEM. The features described in this section make CA APM TG an

excellent addition to your IT application suite. The following sections describe these

features:

Load ramping(see page 12)

Script creation and maintenance(see page 13)

Integration with CA Introscope(see page 13)

Integration with the CA Customer Experience Manager(see page 14)

Load ramping

You can also use CA APM TG synthetic transactions to test a new application under load

using the CA APM TG load ramping feature. This feature simulates load on the servers to

determine if the application can perform adequately under production load demands.

When application performance issues occur, one of the first questions that application

and IT support personnel ask is: "Which other users are experiencing the same

problem?" Knowing the scope of a problem helps you to prioritize the problem and

determine which other teams to involve in a search for the solution. The challenge

facing global enterprises is that it is always off hours for business somewhere in the

world. With CA APM TG synthetic transactions, you can determine web application

performance from all locations, ensuring top performance and customer satisfaction.


13/107

CA APM TG features


Script creation and maintenance

Web sites and web applications are becoming more complex, using intricate

technologies to execute complicated requests. Manually creating scripts to monitor web

applications utilizing newer and newer technologies leads to script errors and incorrectdata being reported.

Create scripts by recording your actions on a specific web site using the CA APM TG

Script Editor. As you navigate through the site, the click stream events are recorded in a

script. Save the scripts to the CA APM TG agent and deploy them. The saved scripts run

against the web sites and web applications creating data that you can monitor using CA

Introscope and CA CEM.

As IT organizations continually deploy new versions of web applications, script

maintenance also becomes key. The CA APM TG Script Editor allows you to edit, update,

and maintain scripts with ease. This decreases the number of false alarms and

guarantees up-to-date information for all monitored web sites and applications.

CA APM TG scripts can also automatically create business processes and transactions in

CA CEM. When scripts are migrated from CA APM TG to CA CEM, a new business

process is automatically created and populated with business transactions from the

script, resulting in a substantial time savings.

For more information about script creation and maintenance, seeCreating and Editing

CA APM TG Scripts(see page 57).

Integration with CA Introscope

CA Introscope enables you to monitor complex web applications in production

environments, detect problems before they affect your customers, and resolve these

issues quickly and collaboratively. CA Introscope provides comprehensive end-to-end

transaction visibility and diagnostic capabilities across your entire infrastructurethe

application itself, application servers, web servers, messaging middleware, databases

and transaction serverswithout degrading performance.

CA APM TG script information can viewed in the CA Introscope Investigator. For more

information about using CA Introscope with CA APM TG, seeViewing CA APM TG

Metrics(see page 91). For more information about using CA Introscope, see the CA

APM Configuration and Administration Guide.


14/107

CA APM TG features


Integration with the CA Customer Experience Manager

CA CEM enables both business managers and IT personnel to understand and respond

to the online experience of each customer. Whether they are external customers,

suppliers, or employees, CA CEM creates actionable information that allows you tooptimize the experience for all end-users and ensure that your applications are fully

serving your business needs.

The CEM console tracks and monitors synthetic transactions generated by CA APM TG,

automatically creating business transaction definitions for the synthetic transactions. All

synthetic transactions are marked as synthetic in the CEM console, allowing you to

easily identify and use the transactions to proactively address issues within a web site or

web application.

For more information about integration with CA CEM, seeCA CEM configuration(see

page 18).


15/107

Chapter 2: Installing the CA APM Transaction Generator 15

Chapter 2: Installing the CA APM

Transaction Generator

This chapter describes how to install the CA APM TG. The following topics are discussed:


Before you begin(see page 15)

Installing the CA APM Transaction Generator(see page 17)

CA APM TG agent startup settings(see page 26)

Installing CA APM TG-specific CA Introscope components(see page 27)

The Command line and the CA APM TG agent(see page 28)

Linux DHCP considerations(see page 29)

Before you begin

In order to monitor transactions generated by CA APM TG, you must first have CA CEM

or CA Introscope installed.

You must have the following system requirements for your environment before

installing the CA APM TG.

Operating system requirements(see page 15)

Additional operating system support for the CA APM TG agent(see page 16)

Recommended minimum hardware requirements(see page 16)

Operating system requirements

The following operating systems are supported by all components of CA APM TG:

Windows 2003 Server with Service Pack 2

Windows XP Professional with Service Pack 3


16/107

Before you begin


Additional operating system support for the CA APM TG agent

The following operating systems are supported by all components of CA APM TG:

Windows 2003 Server Windows XP Professional

Additional operating system support for the CA APM TG agent

Red Hat Enterprise Linux ES

Red Hat Enterprise Linux AS

SUSE Linux Enterprise Server

For more information about specific supported versions, please see the CA APM

Compatibility Guide.

Recommended minimum hardware requirements

The following hardware requirements are the minimum required for CA APM TG

installation.

Windows

A Pentium III 866 MHz processor

At least 1 GB of RAM

At least 300 MB of hard disk storage

Note: Storage use varies depending on the configuration of the CA APM TG agent.

Although installation requires less than the recommended amount, more storage space

is needed for the proper operation of CA APM TG.

Linux

A Pentium III 500 MHz processor

At least 512 MB of RAM

At least 300 MB of hard disk storage

Note:Storage use varies depending on the configuration of the CA APM TG agent.

Although installation requires less than the recommended amount, more storage space

is needed for the proper operation of CA APM TG.

One 10/100 MB network interface card (NIC)


17/107

Installing the CA APM Transaction Generator



You must get the installation package from the CA APM software download area onCA

Support.The following installation packages are available for the CA APM TG:

CA APM TG installation package for Windows

CA APM TG installation package for Linux

The CA APM TG consists of the following components:

CA APM TG agent(see page 17)

CA APM TG Script Editor(see page 17)

CA APM TG Administration Server and Agent Configuration Interface(see page 17)

For more information, seeCA APM TG components(see page 17).

CA APM TG components

The CA APM TG consists of the following components:

CA APM TG agent

The CA APM TG agent runs synthetic transactions against web sites and web services.

For more information, seeThe CA APM TG agent Configuration(see page 32).

CA APM TG Script Editor

The CA APM TG Script Editor lets you view, create, modify, and delete scripts. You also

use the Script Editor to record synthetic transactions to scripts that are then loaded into

the CA APM TG agent for execution. For more information, seeCreating and Editing CA

APM TG Scripts(see page 57).

Note:The CA APM TG Script Editor runs only on Windows platforms.

CA APM TG Administration Server and Agent Configuration Interface

The CA APM TG Administration Server and Agent Configuration Interface administer the

CA APM TG agent. The CA APM TG Administration Server can be configured to use login

credentials from:

CA CEM configuration(see page 18)

Standalone configuration(see page 18)
http://www.ca.com/supporthttp://www.ca.com/supporthttp://www.ca.com/supporthttp://www.ca.com/supporthttp://www.ca.com/supporthttp://www.ca.com/support


18/107



CA CEM configuration

The CA APM TG Administration Server can be configured to use the same login

credentials as the CEM console, allowing the system administrator to manage a single

set of credentials. Users benefit by having to remember a single username andpassword for both the CEM console and the agent configuration.

To use the same credentials as the CEM console, install the CA APM TG Administration

Server component on a Windows or Linux platform with network access to Enterprise

Manager. Contact the CEM console administrator regarding the management of user

credentials.

Note:For more information about installing the CA APM TG Administration Server, see

Installing CA APM TG on Windows(see page 18) orInstalling CA APM TG on Linux(see

page 20).

Standalone configuration

The CA APM TG Administration Server can be deployed in a standalone configuration in

which it reads user information from a simple text-based security file into memory for

authentication and authorization. This simple configuration allows you to get

acquainted with the operation of CA APM TG quickly. It is not intended for production

use. For information about managing user access in a standalone configuration, see

Managing CA APM TG user access in a standalone configuration(see page 24).

For a standalone configuration, install the CA APM TG Administration Server component

on a Windows or Linux platform. For more information about installing the CA APM TG

Administration Server, seeInstalling CA APM TG on Windows(see page 18) orInstalling

CA APM TG on Linux(see page 20).

Installing CA APM TG on Windows

The following section explains how to install CA APM TG on Windows. CA APM TG files

should have already been downloaded before you begin these steps. For more

information, seeInstalling the CA APM Transaction Generator(see page 17) for details.

Note:You must have Administrator privileges to install CA APM TG.

To install the CA APM TG on Windows:

1. Click setup.exeto begin CA APM TG installation.

2.

The InstallShield setup launches. Select where to install CA APM TG, or accept the

default location and click Next.


19/107



3. Select the components you want to install. The following components are available

for installation:

Transaction Generator: Use the plus (+) symbol to open the Transaction

Generator tree and select the components to install. Selecting the check box

next to the Transaction Generator selects all the sub-components for

installation. Some sub-components have configuration options.

The following sub-components are available for installation:

Agent:Installs the CA APM TG agent. To configure RTMCServer, proxy

server and secure (SSL) proxy server information, click Configuration.

The CA APM TG agent uses the RTMCServer process to access web

applications. You can change the port used by the CA APM TG agent to

communicate with the RTMCServer process. RTMCServer can be

configured later using the RTM Configuration tool. Navigate to Start > CA

APM Transaction Generator > RTM Configuration.

:Installs a CA APM TG agent named . Tochange the name of the CA APM TG agent, click Configuration. For more

information about configuring the CA APM TG agent, seeConfiguring the

CA APM TG agent at installation(see page 19).

Script Editor:Installs the Script Editor. The Script Editor allows you to

record and edit scripts used to monitor web applications.

Administration Server:Installs the administration server, a J2EE application

that provides the Administration Interface for the CA APM TG agent. Click

Configureto select a port option or to configure the CA APM TG Administration

Server to use the same user credentials as the CEM console. The Enterprise

Manager host name and port will be required if configuring to share credentials

with CA CEM.

Note:Only one administration server is needed per CA APM TG installation.

Multiple CA APM TG agents can be accessed through a single Administration

Interface.

4.

Click Nextwhen you have selected and configured the CA APM TG components for

installation. A confirmation dialogue opens, presenting your installation

information. Click Start Setupto begin the installation, Backto return to the

previous screen to select other options, or Cancelto cancel the installation.

Configuring the CA APM TG agent at installation

When you install a CA APM TG agent, you can configure the name of the agent, or you

can accept the default agent name.

If you do not assign a specific name at the time of installation, renaming the agent later

requires you to uninstall and then reinstall the agent.


20/107


21/107



5. Launch the install file:

./install.setup install

The install script launches, asking you which components you want to install,

directory paths, and other configuration information. You can accept the defaults or

supply different information. The following components are available for

installation:

CA APM Transaction Generator AgentIf you accept the defaults, the CA APM

Transaction Generator Agent apmtg_site1 is installed using port 7700, the

RTMCServer port is 7201, and no proxy server or secure proxy server is used.

You can also configure the CA APM Transaction Generator Agent to send

Information to Introscope. If you choose to not enable this feature at this time,

you can configure it later.

CA APM Transaction Generator Administration ServerThe CA APM

Transaction Generator Administration Server will be on port 9090 and will be

deployed in a standalone configuration. You can select to use the same

credentials as the CEM console. The Enterprise Manager host name and portwill be required if configuring to share credentials.

6.

Once installation is complete, you mustlog out and log back in again.

Note:There is a problem with using the Script Editor (which only runs on Windows)

when connecting to a CA APM TG agent running on Linux that is using DHCP to

acquire an IP address as opposed to using a static IP. For details, seeLinux DHCP

considerations(see page 29)

Displaying CA APM TG information in CA Introscope Investigator

When this feature is enabled, CA APM TG sends information about the status of the CA

APM TG agent and its scripts to CA Introscope where this data appears in the

Investigator tree. You can enable and configure this feature during the installation of the

CA APM TG agent or after the CA APM TG agent has been installed. For details, see:

Integrating with CA Introscope on Windows(see page 21)

Integrating with CA Introscope on Linux(see page 23)

Integrating with CA Introscope on Windows

The following sections explain how to enable the CA Introscope integration on the CA

APM TG agent running on Windows. You can enable and configure the CA Introscope

integration either during or after the installation.

Enabling and configuring CA Introscope during installation(see page 22)

Enabling and configuring CA Introscope after installation(see page 22)


22/107



Enabling and configuring CA Introscope during installation

1. While installing the CA APM TG agent, expand the agent installation component

and highlight the default instance name apmtg_site1.

2.

Click the Configurationbutton.

3. In the Introscope Metric Datagroup, check Enable Introscopeand enter the

Introscope EM Hostand Introscope EM Port.

Note:The installer attempts to verify that the Enterprise Manager is present on the

specified host and port. However, if the Enterprise Manager is not currently running,

you are given the option to continue with these settings or to change them.

Enabling and configuring CA Introscope after installation

The following section describes how to enable the CA Introscope integration if you

chose not to enable CA Introscope during the installation, but want to enable it later.

1.

From a command prompt, change the directory to:

\Introscope\config

2. Edit the IntroscopeEPAgent.properties file and set the following variables to the CA

Introscope Enterprise Manager hostname and port:

introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=emhostname

introscope.agent.enterprisemanager.transport.tcp.port.DEFAULT=emport

3. Start the CA Introscope integration either manually or automatically using the

following steps.

To manually start the CA Introscope integration:

1. From a command prompt, change the directory to:

\Introscope

2. Run StartAgent.bat to activate the CA Introscope integration in the active console

window.

3. Log in to the CA APM TG agent Configuration UI and configure the agent to send

data to CA Introscope:

a. Navigate to Connect to Agent > AgentPort > Configuration tab > Configure

Agent.

b. On the Configure Agentpage, set Send Data to Introscopeto Yes.


23/107



To automatically start the CA Introscope integration:


\WTGService

2.

Edit the wtgservice.ini file and add iscopeto the [LAUNCH] section.

Note:Rebooting (or stopping and restarting wtgservice) activates the CA

Introscope integration.

3. Log in to the CA APM TG Agent Configuration UI and configure the agent to send

data to CA Introscope:

a.

Navigate to Connect to Agent > AgentPort > Configuration tab > Configure

Agent.

b. On the Configure Agentpage, set Send Data to Introscopeto Yes.

Integrating with CA Introscope on Linux

The following sections explain how to enable the CA Introscope integration on the CA

APM TG agent running on Linux. You can enable and configure the CA Introscope

integration either during or after the installation.

Enabling and configuring CA Introscope during installation(see page 23)

Enabling and configuring CA Introscope after installation(see page 23)

Enabling and configuring CA Introscope during installation

While installing the CA APM TG agent, you are asked if you want to send CA APM TG

metrics to CA Introscope. If you reply yes, you are prompted for the CA Introscope

Enterprise Manager host address and port. After rebooting Linux, the CA Introscope

interface component starts automatically.

Enabling and configuring CA Introscope after installation

The following section describes how to enable the CA Introscope integration if you

chose not to enable CA Introscope during the installation, but want to enable it later.


/Introscope/config

2.

Edit the IntroscopeEPAgent.properties file and set the following variables to the

Introscope hostname and port:

introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=emhostname

introscope.agent.enterprisemanager.transport.tcp.port.DEFAULT=emport

3.

Start the CA Introscope integration either manually or automatically using the

following steps.


24/107



To manually start the CA Introscope integration:


\Introscope

2.

Execute the StartAgent.sh script with the start option:./StartAgent.sh start.

3.

Log in to the CA APM TG Agent Configuration UI and configure the agent to send

data to CA Introscope.


Agent.

b. On the Configure Agent page, set Send Data to Introscopeto Yes.

To automatically start the CA Introscope integration:


/install_files/scripts

2. Create the startup script by executing MkStartIScope with the install option:

./MkStartIScope i

Note:Rebooting activates the CA Introscope integration.

3. Log in to the CA APM TG Agent Configuration UI and configure the agent to send

data to CA Introscope.


Agent.

b. On the Configure Agent page, set Send Data to Introscopeto Yes.

Managing CA APM TG user access in a standalone configuration

When deployed in a standalone configuration, the CA APM TG Administration Server is

delivered with two pre-defined user names: cemadmin and wtgoperator. The cemadmin

user has the administrator role, and the wtgoperator has the operator role. The Security

page is where administrators create other users, which you can designate as having

administrator rights (or not).

Note:In a standalone configuration, the CA APM TG Administration Server reads user

information from a simple text-based security file into memory for authentication and

authorization. This is a simple configuration that allows you to get acquainted with the

operation of CA APM TG quickly. It is not intended for production use.


25/107



If CA APM TG Administration Server is configured to share credentials with CA CEM,

contact the CA CEM administrator regarding the management of user credentials.

There are two panes on the Security page:

List of Userswhere you view, edit, or delete users

User Informationwhere you add new users

To create a new user account:

1. On the Dashboardtab, click the Securitylink (top right corner).

Note: The Security page is only available when the CA APM TG Administration

Server is configured for standalone operation. The Security page is only available to

CA APM TG Administrators.

2.

Enter the appropriate information in the User Informationpane to add a new user:

User NameThe login user name for the new CA APM TG user.

RolesSelect the administrator role to allow this user full access to the CA

APM TG Agent Configuration. Select the operator role to give this user limited

access.

Account EnabledBy default, the new user is enabled; clear the check box if

you do not want to enable this user account.

PasswordMust be at least 6 characters. Passwords are case sensitive.

Reset buttonClears the current user information.

Save User buttonSaves the user information.

3.

Click Save User.

To edit a user account:

In the List of Users, click the User Name link to display this account in the User

Information pane.

You can modify the roles, enable or disable the account, and change the password.

To delete a user:

In the List of Users, select the check box next to the user name and click Delete.

The user name is deleted.


26/107

CA APM TG agent startup settings


Displaying CA APM TG agent availability in CA CEM

You can send information about the availability of the CA APM TG agent to the CEM

console. If the CA APM TG agent is unavailable, CA APM TG notifies CA CEM and the

event appears in the CEM console under System > Events. When the CA APM TG agentis once again available, CA APM TG sends another notification. You can enable this

feature after installing the CA APM TG agent.

To enable CA APM TG agent notification in CEM console:

In the wtg.properties file, specify the IP address and port number of the CA CEM

host that you are sending the notifications to.

The wtg.properties file is under %WTG_HOME%\Tomcat\webapps\wtg\WEB-INF

and contains:

CEM.Tess.Host=127.0.0.1

CEM.Tess.HostPort=80

# CEM Tang notification interval. Set to -1 to disable CEM Tang notification.CEM.Tang.Notification.Interval=-1

The notification interval is specified in seconds. The status of agents in the known

agents list is checked at this interval.

Note: If you are using shared CA CEM credentials, the CEM.Tess.Hostproperty is

already set. In that case you just need to set the CEM.Tang.Notification.Interval

property.

To disable CA APM TG Agent notification in CA CEM:

Set the CEM.Tang.Notification.Intervalto -1 to disable CEM Tang notification.

CA APM TG agent startup settings

You can define settings that control CA APM TG agent behavior. You specify these

settings in the CA APM TG agent initialization file, wtgagent.ini, located in the

/wtgagent_namedirectory. These settings are read in when the CA APM

TG agent starts. Some settings are set based on selections made at installation and

should not be modified.

Note:The IntroscopeSend parameter is set during installation and is only in effect the

first time the agent starts. After that, CA Introscope settings are controlled from the

Configure Agent page in the CA APM TG Administration Interface. For more information

about this tab, seeConfiguring the CA APM TG agent(see page 37).


27/107

Installing CA APM TG-specific CA Introscope components


The following CA APM TG agent Startup Setting entries can be modified:

LogFileSizeLimit=10000000 and LogFileRetain=5

These entries control the size in bytes of the daily activity logs and how many days

of logs should be retained. When a log exceeds the size limit, a new log is openedwith a filename containing a new timestamp. The LogFileSizeLimit is not applicable

for XML format logs.

The LogFileSizeLimit file can be found in the /wtgagent_name

directory. The LogFileRetain file can be found in the wtgagent.ini directory.

TraceFileSizeLimit=10000000 and TraceFileRetain=5

These entries control the size in bytes of the CA APM TG agent trace logs and how

many days of logs should be retained. When a log exceeds the size limit, a new log

is opened with a filename containing a new timestamp

Location=

Optional location information can be specified to identify a particular CA APM TGagent. The entered string appears in the CA APM TG Administration Interface under

the Configuration tab, and as a CA APM TG agent metric in the CA Introscope

Investigator tree. For more information, seeConfiguring the agent(see page 37).

ListenPort=7700

The port that the agent will use to communicate with the CA APM TG

Administration Server.

IntroscopeMetrics=

Specify which CA APM TG metrics to send to CA Introscope. SeeOther metrics(see

page 92)

RTMAddress=localhost and RTMPort=7201

This is the address and port to be used when connecting to RTMCServer. This is the

CA APM TG process that polls monitored scripts. If the port is changed here then it

must also be changed in the rtmfile located in the /WTGService

directory.

Installing CA APM TG-specific CA Introscope components

To use CA Introscope to monitor and display CA APM TG information, install and

configure the CA Introscope components described inInstalling CA Introscope tab

views(see page 28).


28/107

The Command line and the CA APM TG agent


Installing CA Introscope tab views

CA APM TG uses tab views in the CA Introscope Investigator to summarize metric

information. You can view the same metrics data by browsing the Investigator tree

nodes. The CA APM TG-specific tab view file must be copied to the Enterprise Managerinstallation location.

To install CA Introscope tab views:

1. From the CA APM TG install image, open the IntroscopeFiles\TypeViews directory.

Windows: Copy the WTGAgent-TV9.xml file.

Linux: Copy the WTGAgent-TV9.xml file from the Linux install tar file.

2. Paste the copied files into this directory:

\ext\ddtv

Note:You may have to create the ddtvfolder if it does not already exist in the ext

directory. Any CA Introscope Workstation that is open shows the tab views after

reconnecting to the Enterprise Manager.

The Command line and the CA APM TG agent

After the CA APM TG agent is installed, you can start, check the status, and stop the CA

APM TG agent by executing different commands from the command line. You can use

the same commands on all platforms.

Note:On Windows the CA APM TG agent runs as a service so the recommended way of

starting and stopping is via the Windows Service Control Manager.

To start the CA APM TG agent:

At the command prompt, enter:

wtgagent start

where is the name of the agent. This name must match the name

assigned to the agent at installation.

The following message appears:

wtgagent : - Started

If the agent is already running when you issue the command, then the following

message appears:

wtgagent - Already Running


29/107

Linux DHCP considerations


To check the CA APM TG agent status:


wtgagent status

where is the name of the CA APM TG agent. This name must matchthe name assigned to the CA APM TG agent at installation.


wtgagent : - Running

The following message appears if the agent is not running:

wtgagent : - Not Running

To stop the CA APM TG agent:


wtgagent stop

where is the name of the CA APM TG agent. This name must match

the name assigned to the CA APM TG agent at installation.


wtgagent : - Stopping

wtgagent : - Stopped

The following message appears if the CA APM TG agent has already stopped:

wtgagent : - Not Running


There is a problem when using the Script Editor (which only runs on Windows) when

connecting to a CA APM TG agent running on Linux that is using DHCP to acquire an IP

address as opposed to using a static IP.

If you have a static IP address, the /etc/hosts file is specified as in this example:

127.0.0.1 localhost.localdomain localhost

111.222.123.4 mylinux.ca.com mylinux

This works fine with the Script Editor, which needs to communicate with the JAVA RMI

component of CA APM TG to access scripts on the agent machine.

If you are using DHCP, the /etc/hosts is specified as in this example:

127.0.0.1 mylinux.ca.com localhost.localdomain localhost mylinux

By default Linux is configured to look in the /etc/hosts file first before accessing the DNS

to resolve a name to an IP address. The CA APM TG remote Java RMI component on

Linux listens for connections on an IP address it gets by resolving the host name. In the

case of the Linux default settings, the host name resolves to 127.0.0.1, which is the

loopback address, so any Script Editor from another machine trying to connect will fail.


30/107



Linux can be configured to first access the DNS when resolving addresses by editing the

/etc/nsswitch.conf file and specifying the hosts entry as in this example:

hosts: dns files

The result is that the host name resolves to the IP address provided by DHCP andconnections are successful.

Whether Linux is configured to use a certain name or the name is assigned by DHCP, the

requirement remains that a machine name must exist. This can be confirmed from a

terminal session by typing:

hosthame

The result should be a name, not just localhost.localdomain. After making the

modification to nsswitch.conf and restarting, execute the following command using the

name returned by hostname:

host

should result in the IP address assigned by DHCP, not 127.0.0.1.


31/107


Chapter 3: Configuring the CA APM

Transaction Generator Agent

This chapter describes how to configure the CA APM Transaction Generator (CA APM

TG) agent using the CA APM TG agent Configuration. The following topics are discussed:


Overview of configuring agents(see page 31)

The CA APM TG Agent Configuration(see page 32)

Groups and scripts(see page 42)

Overview of configuring agentsThe configuration of a CA APM TG agent determines which scripts a CA APM TG agent

uses to poll Web sites and also determines the polling parameters and provides various

script handling capabilities.

You connect to a CA APM TG agent using the CA APM TG agent tab. After installing an

agent, you can configure the agent and set the agent defaults.

Here is an overview of the CA APM TG agent configuration process:

1. Optionally configure the agent settings or accept the default settings. To change the

settings for all the scripts, seeSetting CA APM TG agent defaults(see page 40). To

change settings for a group, seeConfiguring a group(see page 46).

2. Determine which web sites and web services need CA APM TG synthetic

transactions to facilitate your application monitoring strategy. Optionally, you can

create groups to facilitate the monitoring of the web sites and web services, such as

creating groups for specific sites or services. For more information, seeGroups and

scripts(see page 42).

3.

Create the scripts for this monitoring process. For more information, seeGroups

and scripts(see page 42). Scripts detail procedures you want the CA APM TG agent

to perform against monitored web sites and web services. For information on script

creation, seeCreating and Editing CA APM TG Scripts(see page 57).

4. Update the scripts in the agent. Connect to the CA APM TG agent and click the

Update Modified Scriptsbutton on either the All Scriptstab or the Group Scripts

page (Scripts By Group > GroupName).

5.

Set agent default information. When you know more about the work being done,

you can choose suitable default settings. For more information, seeSetting

Hierarchy(see page 32).


32/107

The CA APM TG Agent Configuration


Setting Hierarchy

A hierarchy exists for the settings of scripts, groups of scripts, and all the scripts on an

agent. The CA APM TG agent uses groups to organize scripts. A script uses as its defaults

the settings of the group to which it belongs, unless script-specific settings areconfigured in the Script Editor. A group uses as its defaults the settings of the agent it is

associated with, unless group-specific settings are configured on the Configure Group

page. You can configure both scripts and groups to use different settings, depending on

the desired polling outcome. You can keep the default agent settings or modify them

(recommended).

The configuration of a CA APM TG agent determines which scripts the agent executes,

how the agent gathers resource data, and how the agent determines the status of the

script. The Configuration tab on the CA APM TG agent View page displays the current

settings and polling statistics.

Interval settings allow you to fine tune the performance of the CA APM TG agent. TheCA APM TG agent default and polling interval settings determine the error status for the

groups and scripts associated with the CA APM TG agent. The polling interval values are

global in scope and apply to every group and script a CA APM TG agent monitors, unless

the group or script is configured with different settings. The default interval values

should be adjusted to match the worst acceptable response time.


The CA APM TG Agent Configuration displays two tabs that you can use to connect to

the CA APM TG agent you want to configure:

The Dashboard tab(see page 33)displays the users CA APM TG Shortcuts and the

List of Known Agents for quick access to CA APM TG agents

The Connect to Agent tab(see page 35)allows you to connect to new CA APM TG

agents and to edit the List of Known Agents

For details, seeThe Dashboard tab(see page 33) andThe Connect to Agent tab(see

page 35).

When the CA APM TG Agent Configuration is configured in a standalone configuration,

the system displays a Security link to enable the administrator to manage users. For

more information, seeManaging CA APM TG user access in a standalone configuration

(see page 24).


33/107



To connect to the Agent Configuration:

1. Open a web browser.

Enter the URL for the CA APM TG Agent Configuration. The URL depends on how

and where the CA APM TG Administration Server is installed. Typically it is the nameof the machine the CA APM TG Administration Server is installed on, the port

number, and the application path. SeeInstalling the CA APM Transaction Generator

(see page 15) for details.

In the following example, the CA APM TG Administration Server machine is wtgtest,

the port number is 9090, and the application path is wtg.

http://wtgtest:9090/wtg

2.

Enter the user name and password for the CA APM TG Agent Configuration.

The initial username and password depends on how the Administration Server is

configured. When sharing CA CEM credentials, the CA CEM System Administrator is

also a CA APM TG Administrator, and all other CA CEM users are CA APM TG

Operators.

When CA APM TG is installed on the CA Introscope Enterprise Manager, the CA

Introscope Administrator is also a CA APM TG Administrator. Contact your CA APM

TG Administrator for access information.

In a standalone configuration, the initial username and password for an

Administrator is cemadmin / quality. For a CA APM TG Operator, the initial

username and password is wtgoperator / quality.

The Dashboard tab

The CA APM TG dashboard displays your saved CA APM TG shortcuts and the list of

known agents.

CA APM TG Shortcuts(see page 34)allow you to navigate directly to saved

locations within the Agent Configuration for easier access to important information.

List of Known Agents(see page 35)displays the current status of an agent and

allows you to quickly connect to known agents

For details, seeCA APM TG Shortcuts(see page 34) andList of Known Agents(see

page 35).


34/107



CA APM TG Shortcuts

For quicker access to pages with information of particular interest to you, add the pages

to your list of shortcuts in the CA APM TG Shortcuts pane in the Dashboard tab. When

the Add to CA APM TG Shortcuts link appears on a page of the Agent Configuration, youcan add that page to the shortcut list.

To add an item to the CA APM TG Shortcuts:

1. Navigate to the CA APM TG agent tab that you want to add to the shortcuts list:

Scripts By Group tab

All Scripts tab

Status Messages tab

Configuration tab

Note: By default, each user already has a shortcut to the Connect to Agent tab.

2.

Click the Add to CA APM TG Shortcutslink at the top right of the page.

3. The Add to CA APM TG Shortcutspage opens.

The name of the page to be added and the agent host name are in the Namefield

by default. You can accept the default shortcut name, or rename the shortcut to a

unique name of your choice. To revert to the default name, click Reset.

4. Click Save.

A confirmation message displays on the page to indicate that the shortcut was

added.

5. Click the Returntolink to return to the previous page.

The next time you visit the Dashboard, the new shortcut will be in your CA APM TG

Shortcuts list.

To remove an item from the CA APM TG Shortcuts:

1. Navigate to the Dashboardin the CA APM TG agent Configuration.

2. In the CA APM TG Shortcutssection, click the Editbutton to display the Edit CA

APM TG Shortcutspage.

3. Select the check box next to the shortcut link to be removed.

You can select more than one link at a time.

4.

Click Delete.

The shortcuts are deleted from your Shortcut list.


35/107



List of Known Agents

The List of Known Agents displays a list of known agents and their status. If your agent is

in this list, click on the link in the Agent Port column to access the agent. Use the

Refresh button to display the current Error Status. Use the Edit button to delete agentsfrom the list. The Edit button is only available to CA APM TG Administrators. For

information about error status, seeChecking the error status of agents. (see page 36)

The Connect to Agent tab

The CA APM TG Connect to Agent tab enables you to connect to a CA APM TG agent.

There are two panes on the Connect to Agent tab:

Connect to Agentallows you to connect to any CA APM TG agent when you know

its host and agent port. Use this pane to connect to an agent that is not on the List

of Known Agents. To connect to a CA APM TG agent that is not on the List of KnownAgents, seeConnecting to an Agent(see page 35).

List of Known Agentsdisplays the current status of an agent and allows you to

quickly connect to known agents. For more information, seeList of Known Agents

(see page 35).

Connecting to an Agent

To use the Agent Configuration to configure a CA APM TG agent, you must first connect

to the CA APM TG agent. Once you connect to a CA APM TG agent in the Agent

Configuration, you can access the agent by clicking a link in the List of Known Agents on

the Dashboard or the Connect to Agent tab.

To connect to a CA APM TG agent the first time:

1. Navigate to the Connect to Agenttab in the Agent Configuration.

2. In the Agent Hostfield in the top section, enter the name of the machine where the

CA APM TG agent was installed.

3.

In the Agent Portfield, enter the port for the agent.

4. Click OK.

The system attempts a connection to the CA APM TG agent. If the connection is

successful, the CA APM TG agent View page displays and this CA APM TG agent is added

to the List of Known Agents. The next time you visit the Dashboard or Connect to Agenttab, this agent appears in the list. See alsoThe CA APM TG agent View page(see

page 36).


36/107



The CA APM TG agent View page

The CA APM TG agent View page displays the following tabs:

Scripts By Group:Displays information about the groups on the agent. Controls for

creating, deleting, and displaying the scripts in a group are here. For more

information on the Scripts By Group tab, seeThe Scripts By Group tab(see

page 43).

All Scripts:Displays all the scripts associated with the agent. For more information

on scripts, seeViewing all scripts in all groups(see page 48).

Status Messages:Displays recent messages for the selected agent. You can specify

the number of messages to display on the Configure Agent page. The default is 100.

Use the Clear Last Messagebutton on this tab to clear the Last Message field at the

bottom of all CA APM TG agent view pages. For more information, seeViewing

status messages(see page 55).

Configuration:Displays the current settings of the agent. Controls for setting

default parameters for the agent, resetting counters, and for sending scripts to CA

CEM are here. For more information about default settings, seeConfiguring the CA

APM TG agent (see page 37) andUsing Configuration Tab buttons(see page 41).

Checking the error status of agents

The List of Known Agents indicates the current error status for each agent listed. The

error statuses are:

this indicator lets you know the agent is running normally.

this indicator lets you know the agent is running and has detected an error

with one or more scripts. Script errors include the HTTP status code error and aresponse that exceeds the specified timeout value.

the indicator lets you know the status of the agent is unknown, which usually

means the agent is not running or cannot communicate with the CA APM TG

Administration server.

Removing agents

The following section explains how to remove agents from the List of Known Agents.

To remove a CA APM TG agent from the List of Known Agents:

1.

Navigate to the Connect to Agents tab.

2. Select the agent in the List of Known Agents and click Delete.

The agent is removed from the List of Known Agents.


37/107



To remove all CA APM TG agent:

Select the check box next to the column heading Selectand click Delete. All agents

will be removed from the List of Known Agents.

Note: Because the List of Known Agents is shared by all users of this CA APM TGagent Configuration, only a CA APM TG Administrator can delete CA APM TG agents

from the List of Known Agents.

Troubleshooting connecting to an agent

This table provides some tips that might help you troubleshoot connecting to a CA APM

TG agent.

Symptom: The CA APM TG agent doesnt appear to be running.

Possible Solution: Make sure the agent you are trying to connect to is up and

running. To display the status of a CA APM TG agent, run the following command on

the agent machine:

wtgagent status

where is the name of the agent. For example:

wtgagent status apmtg_site1

Symptom: The agent host machine isnt reachable.

Possible Solution: To check if the agent host machine is reachable, run the

following command:

ping

where is the name of the machine running the agent.

Configuring the CA APM TG agent

This section describes how to configure the CA APM TG agent to work with CA CEM and

CA Introscope, in addition to setting general settings about polling and logging.

To set agent configuration settings:

1. Connect to the CA APM TG agent you want to configure.

SeeConnecting to an agent(see page 35) for more information.

2. Once the CA APM TG agent has been connected, navigate to the Connect to Agent

> AgentPort > Configuration tab > Configure Agent, whereAgentPortis the port of

the agent being configured. The Configure Agent page opens.

3. Set the default values for the CA APM TG agent and click Save. To return the

settings to a previously saved state, click Reset.

Complete the fields found on the Configure Agent page. For more information

about these fields, seeCA APM TG agent configuration fields and descriptions(see

page 38).


38/107



CA APM TG agent configuration fields and descriptions

When you configure the CA APM TG agent, you can set properties for these

components:

CA CEM Integration

Enterprise Manager Host NameThe IP address or name of the Enterprise

Manager. This is required if you want to send scripts to CA CEM for automatic

creation of business services.

Enterprise Manager Host PortThe host port of the Enterprise Manager. This

is required if you want to send scripts to CA CEM for automatic creation of

business services.

CA CEM Application NameThe name of the application in CA CEM to

associate with scripts that are sent to CA CEM and the business services that

are created from them. If left blank, the default CA CEM application is used. If

you enter an application name that does not exist on CA CEM, it will be

created. You can change the application name at any time in CA CEM.

Note: To send all scripts to CA CEM, seeUsing Configuration Tab buttons(see

page 41). To send a single script to CA CEM, seeWorking with scripts in the

Script Requests page(see page 49).

CA Introscope Integration

Send Data To CA IntroscopeThis setting determines if the CA APM TG agent

sends information to CA Introscope. By default, the CA APM TG agent does

not send data to CA Introscope unless you configure it to do so. This can be

done during CA APM TG agent installation or using the Agent Configuration.

When this feature is disabled, no data is sent to CA Introscope. CA APM TG

continues to drive synthetic transactions, but does not send information to CA

Introscope. When this feature is enabled, monitored scripts and script

information are reported and are available to view in CA Introscope. Enable

this feature by selecting Yes.

General Settings

Counter Auto Reset Interval (Days)Determines how often counters are reset.

Initial Concurrent PollsThe initial number of concurrent polls performed by

the agent. The agent schedules the Initial Concurrent Polls value p lus the

number of items in error status up to the Maximum Concurrent Polls value.

Maximum Concurrent PollsThe maximum concurrent polls to be performed

by the agent. The agent schedules the Initial Concurrent Polls value plus the

number of items in timeout status up to the Maximum Concurrent Polls value.

Status Message Table SizeDetermines how many entries are kept in the

message table. The message table contains entries for all script activity,

including adding, deleting, disabling scripts, and any resulting errors. You can

view the message table on the Status Messages tab.


39/107



Agent Log Settings

Agent Log FormatSpecifies the format for the monitored scripts logs. When

a poll completes for a script, statistics are written to a log. The monitored script

logs are in the \log\wtgagent_apmtg_site1directory. The

default is a text log with entries delimited by a vertical bar. If XML is selected,

the log is written in XML format.

Agent Log Trace LevelControls the level of detail in the CA APM TG agent

trace log. The following options are available:

Info

Warning

Critical

Debug

Debug2

Debug3

Note:The Debug settings are used for in-depth tracing of CA APM TG. If you

are working with CA APM Support to triage a problem, the support group may

request a specific debug level.

The trace log is located in the \wtgagent_apmtg_site1

directory.

CA APM TG agent performance settings example

The following is an example of how the CA APM TG agent uses the Initial Concurrent

Polls and Maximum Concurrent Polls settings.

Suppose the CA APM TG agent is monitoring 300 scripts; the Initial Concurrent Polls

value is set to 10, and the Maximum Concurrent Polls value is set to 30. Suppose 15

scripts are in timeout status. The CA APM TG gent polls as many as 25 scripts

concurrently. Now, suppose the number of scripts in timeout status climbs to 40. The

agent polls as many as 30 scripts concurrently.

The CA APM TG agent reaches "too busy" status when it is unable to complete the next

concurrent poll within the interval. To remedy the situation, you could adjust the

default polling intervals. Alternatively, you could increase the values for the Initial

Concurrent Polls and Maximum Concurrent Polls.

Note:When the Configuration Tab indicates a Busy Status of "Agent Is Too Busy," it

indicates that the CA APM TG agent is too busy to poll a URL at the requested interval.

Each time the CA APM TG agent is ready to poll an item, it checks the previous time

stamp to determine if the interval is greater than 110 percent of the specified interval.

For example, if the polling interval is 60 seconds, and 70 seconds have passed before the

CA APM TG agent performs the next poll, the CA APM TG agent increments the too-busy

count.


40/107



Setting CA APM TG agent defaults

The CA APM TG agent default settings are used when a new group is created either

automatically by specifying a group name in the Script Editor Recorder or by using

Create Group (seeCreating a group(see page 45)). Once created, the group settings canbe modified on the Configure Group page (seeConfiguring a group(see page 46) for

details). Use the Set Agent Defaults page to change the CA APM TG agent default

settings. There are two sections on the Set Agent Defaults page:

The Intervalsettings affect how often a script is run.

The Generalsettings affect script execution.

To set CA APM TG agent defaults:

1. Navigate to Connect to Agent > AgentPort > Configuration tab > Set Agent

Defaults. The Set Agent Defaultspage opens.

2. Set the desired default values. To return the settings to a previously saved state,

click Reset.

Interval Settings

Changing the default settings allows you to adjust the polling interval. For example, you

may not want to let 300 seconds pass between polls when a web site or service has a

timeout status. Adjust the Error Interval to indicate the number of seconds between

polls when a web site or service has a timeout status.

The IntervalSettingssection of the Set Agent Defaults page contains these fields:

Polling Interval (sec)Specifies the number of seconds between polls when the

script's status is Normal.

Error Interval (sec)Specifies the number of seconds between polls when the

script's status is Critical.

Timeout Value (ms)Specifies the expected response time, in milliseconds. If the

threshold is reached, the script's status changes to indicate an Error.


41/107



General Settings

The following table describes the fields in the GeneralSettingssection of the Set Agent

Defaults page:

Detail LevelSpecifies which URL components to request. Set the detail level of

monitoring for web pages. The following options are available:

Page+Frames:requests the page and any frames that may be on that page.

Page+Components: requests the page and all the image components on that

page.

PageOnly: requests only the initial page.

Max ConnectionsDetermines how many simultaneous connections are used for

requesting components when Detail Level is set to anything other than PageOnly.

Max Connections are limited to 20 total.

Note:Depending on network traffic, you may improve the polling performance by

increasing this value.

Bypass ProxyDetermines whether a proxy server is used when retrieving a URL.

Select Yes to bypass the proxy server defined in the RTMCServer configuration or

No to use the proxy server. The default setting is No.

Note:A proxy server may have been specified in the RTMCServer configuration in

order to access the internet, but some URLs may be on web servers within a

corporate network and not accessible to the proxy. You can avoid using proxy

servers by setting Bypass Proxy to Yes.

Using Configuration Tab buttons

Use buttons on the Configuration tab to perform immediate actions on the counters and

scripts associated with the agent:

Configure AgentClick to set the basic configuration values to for a CA APM TG

agent. For more information, seeConfiguring the CA APM TG agent(see page 37).

Set Agent DefaultsClick to set the default values for a CA APM TG agent. For more

information, seeSetting CA APM TG agent defaults(see page 40).

Reset CountersClick to reset the counters for all your groups. This sets all scripts

with critical counts back to zero, returning them to a Normal status.

Send All Scripts to CA CEMClick to send all scripts associated with the CA APM TG

agent to CA CEM for monitoring. The next time each script polls successfully, it issent to CA CEM for automatic business process creation.


42/107

Groups and scripts


Groups and scripts

Groups are containers for scripts. You can use groups to collect similar scripts, such as

scripts that refer to a specific web site or service or scripts that are monitored for

mission-critical functions. A group can contain any number of scripts. You specify the

name and description for a group and then add scripts to it. For more information, see

The Scripts By Group tab(see page 43) andViewing scripts in a group(see page 47).

Important! Scripts use the interval settings for the group to which they belong, unless

the script contains its own settings specified via an tag. To configure group

threshold and interval settings, seeConfiguring a group(see page 46).


43/107

Groups and scripts


The Scripts By Group tab

The Scripts By Group tab lists all groups associated with the selected CA APM TG agent,

including the group names and descriptions, error status, the number of scripts in the

group, the number of scripts with an error status, and the number of enabled scripts.

To display groups by status:

Click the relevant Showlink to display groups that have Normal, Error, or Disabled

status.

To search for groups:

1.

In the Search For dropdown list, choose to search by either th

apm_9.5--transaction generator implementation guide

Documents