Glossary

Descriptions of key terms
apmdevops97
APM uses the following terms:
.NET agent
The
.NET agent
 collects metrics on Microsoft .NET applications.
.NET Framework
The Microsoft 
.NET Framework
 is a development and execution environment that allows different programming languages and libraries to work together. The .NET Framework is based on a runtime environment that is known as the Common Language (CLR). CLR uses programming languages such as C#.
agent
In an Introscope deployment, the 
agent
 collects application and environmental metrics and relays them to the Enterprise Manager. These applications can be any of the types: Java, .NET, PHP, or web applications. An application that reports metrics to an agent is referred to as being instrumented.
agent - Enterprise Manager network topology
The 
agent - Enterprise Manager network topology
 is the CA APM environment network structure. This topology specifies which agents or groups of agents can connect to:
  • Specific standalone Enterprise Managers
  • Collectors
  • Groups of Collectors
agent extension
An 
agent extension 
is program code (JAR or DLL and related PBD file) that extends the basic functionality of the agent. BizTrxHttpTracer and ServletHeaderDecorator or HTTPHeaderDecorator are agent extensions that are required for the integration of CA CEM and Introscope.
agent load balancing
Agent load balancing
 balances the metric load between Collectors in a clustered environment. Specific agents, which are assigned to the MOM, equalize the metric count among the Collectors by directing the agents to send their metric data to the least burdened Collector in the cluster.
alert
An 
alert
 is a saved set of threshold values for "Caution" and "Danger," with accompanying other properties. In Introscope, an alert is one of the base objects in a Management Module, which saves collections of these objects for reuse. An alert commonly has actions that are associated with it, but actions are themselves separate Management Module objects.
Distinguish between the alert itself (for example, the name of the alert that is associated with saved threshold values) and the following alert components:
  • Alert indicator, 
    which is a graphical display of alert status
  • Alert notification,
     which is one of the actions possible to associate with an alert.
Amazon EBS Storage
Amazon EBS
(Elastic Block Store) is a block-level storage volume that persists independently from the lifetime of an EC2 instance. CA APM recommends using this type of storage in your instance to allow you to stop and restart your instance at a later time.
Amazon Machine Image
An
Amazon Machine Image
(AMI) is an encrypted machine image, similar to a template, of the root drive of a computer.  AMIs contain the operating system. AMIs can also include software and layer of the application, such as database servers, middleware, and web servers. The AMI is stored in the Amazon Elastic Block Store or Amazon Simple Storage Service. 
APM database
The
 APM database
is a relational database that stores data from Introscope and CA CEM.
APM Status console
The 
APM Status console
 is an Introscope Workstation user interface for monitoring and addressing Enterprise Manager runtime health issues. CA APM administrators can view important status and events for a standalone or clustered Enterprise Manager. This functionality provides out-of-the-box monitoring capabilities that would otherwise require the administrator to configure alerts on Enterprise Manager supportability metrics.
Application Performance Management (APM)
CA 
Application Performance Management (APM) 
product. CA APM provides an application performance management strategy that lets you understand the end-user experience and measure Service Level Agreements (SLAs). You can map all transactions to the end-to-end infrastructure. You can also conduct incident triage and root-cause diagnoses in a complete and integrated solution.
See also: IntroscopeCA CEM
application supportability
Introscope measures 
application supportability
 by measuring the performance of various application components. Metrics provide information about JVM/CLR, web application, and backend systems.
CA APM provides supportability metrics so you can answer questions about the health of your applications. Application supportability is also known as application health.
application triage map
The 
application triage map
 presents a graphical view of your managed application, showing application health and errors. This map is automatically generated from the performance and analysis of Introscope metrics, errors, and events.
The application triage map allows you to see your applications from these perspectives: as frontend applications and their dependencies, and as business services and their dependencies.
You can customize the default view of your application by configuring the instrumentation (PBD) files.
App Synthetic Monitor (ASM)
CA App Synthetic Monitor (ASM)
 is a product that creates synthetic transactions to complement transaction monitoring in CA APM. ASM provides early warning of application availability issues.
automatic transaction trace
When smart instrumentation is enabled, highly optimized low overhead tracers collect an 
automatic transaction trace
 under specific trigger conditions. For example, when an error occurs or the ComponentTimeAutoTraceTriggerTracer tracer is deployed and a component response time is exceeded. Automatic transaction traces display deep visibility components and have characteristics that differ from nonautomatic transaction traces, such as manual and sample traces.
AutoProbe
Introscope 
AutoProbe
 automates the application instrumentation process by dynamically adding probes to the application at start-up time. Introscope probes provide the source data for Introscope metrics.
backend
An Introscope 
backend
 is an external system that a web application relies on for some portion of its processing. For example, a backend might be a database, a mail server, a transaction processing system, or a messaging system.
Introscope automatically identifies databases as backend systems by the name of the database. For other external systems, Introscope analyzes the socket activity of the application. Introscope names the backend based on the IP address and port that the application is communicating over.
See also: frontend
backend time
The 
backend tim
e is the measure of time that the suspected Blame component (for example, a database component) of the backend system takes to complete, based on Introscope reporting.
CA CEM is configurable as to which set of components represents backends. By default, CA CEM depends on the Introscope definition of a backend. The Introscope backend time is measured from the Java component that invokes the backend. Therefore, the time includes both the backend processing time and any network time spent communicating with the backend.
baseline
The 
baseline
 is an initial set of data that is used as a comparison or control. Both Introscope and CA CEM employ baseline algorithms to monitor web applications.
Introscope determines the color of an alert indicator in the Overview tab by evaluating current metrics against a baseline for those metrics. With an agent node selected in the agent-centric tree, the Heuristics node shows the metric values that are related to these indicators.
For a given metric, the Introscope baseline algorithm determines the next expected value, and the expected deviation from that value. When the actual deviation exceeds (2x) or significantly exceeds (4x) the expected deviation, the baseliner indicates a moderate or severe violation. The associated heuristic turns yellow or red.
Internally, the baseliner evaluates the slope of the time series, and determines the expected value of the slope. Recent data is given more weight than older data.
CA CEM calculates a defect specification baseline that is based on 28 days of historical data for behavioral defects. After enough data have been collected, you have the option of changing the defect specification value, or setting the baseline.
For example, the slow time defect specification has a default value of 5 seconds. If you gather actual transaction data and then set the baseline for the slow time defect, the value changes from the default of 5 seconds to the suggested defect specification value (say 7.2 seconds).
Baselines database
The Introscope
Baselines database
contains the most common, normal range of values for each metric in your system. The Introscope heuristic logic uses the values to determine whether there is an abnormal condition that requires administrator attention, or special event processing such as Transaction Tracer.
BizTrxHttpTracer
BizTrxHttpTracer
 is an agent extension that uses CA CEM business transaction definitions (the rule set) to identify and monitor transactions. BizTrxHttpTracer enables Introscope Transaction Tracer functionality so that metrics appear in the Investigator with CA CEM names. BizTrxHttpTracer requires the current transaction and tracing information to initiate transaction traces.
BizTrxHttpTracer replaces CEMTracer functionality.
Blame
Introscope 
Blame
 is the technology that is used to instrument an application. Introscope tracks component interactions and resource usage by marking application frontends and backends, and by providing metrics for problem investigations.
box-whisker graph
box-whisker graph
 represents a distribution of data points. The whiskers represent the maximum and minimum range. The box represents the 75th and 25th percentile. The white dash represents the 50th percentile, or median. Tick marks represent the 95th and 5th percentiles.
Connecting lines between the boxes show trends over time. The dashed (orange, connecting) line is the median trend line. The solid (magenta, connecting) line is the average trend line.
Horizontal lines show the upper and lower specification limits (USL and LSL). The data table below the graph shows count (number of transactions), span, average, and data points.
box whisker 2
box whisker 2
business application
business application
 is a software program that automates a business service. CA APM monitors web transactions, which are the product of web applications. A business application is part of the transaction hierarchy.
A CA CEM business application is the name of an object that holds application-specific configuration settings. The object can define the way that a web application:
  • Authenticates users (authentication type, login name parameters)
  • Maintains sessions (session ID parameters)
  • Identifies transactions (application type)
  • Handles case sensitivity of various HTTP parameters (URL paths and login names)
  • Processes user statistics (e-commerce or enterprise)
  • Handles character encoding (multibyte)
business impact
The 
business impact
 is the measure that a defect or an incident has on the business. The CA CEM product displays business impacts on the Impact Leaders and Incidents pages.
business impact
business process
In CA CEM product releases before CEM 5.0, a business service was named a business process.
See also: business service
business service
A CA CEM 
business service
 is a 
group
 of business transactions. Measurements are aggregated to this level in the transaction hierarchy.
In SOA Performance Management, a business service makes outgoing requests to backend systems for the enterprise service bus.
business transaction
A CA CEM 
business transaction
 is a 
set
 of one or more transactions. Measurements are gathered at this level in the transaction hierarchy. For each business transaction, there is one identifying transaction.
This set is used only with complex transactions (for example, Siebel or SAP).
business transaction component
In Introscope, a 
business transaction component 
represents one HTTP request/response pair that is instrumented and monitored to track the health of a business transaction. Business transaction components are the source of application triage map health metrics.
The business transaction component is the single identifying component of the transaction.
A business transaction component is similar to both of these components:
  • Transaction (as it is the one identifying transaction of the business transaction).
  • Transaction component (as it is the one identifying component in the one transaction).
business value add
The 
business value add
 is the sum of the per-transaction business values for all revenue-bearing transactions that are successfully completed for the reporting period. Revenue-bearing transactions can be identified and assigned a per-transaction value, in currency.
CA CEM Calculation: business value add = sum of business values for all revenue-bearing transactions
Used in CA CEM Calculation: total business value = net IT value add + business value add
CA Customer Experience Manager (CA CEM)
CA Customer Experience Manager (CA CEM)
 is a product that monitors customer transactions to isolate the causes of data center problems. CA CEM measures the performance and quality of customer transactions, identifies defects and variance, and quantifies the impact on customers and the business.
CEM transaction time
CEM transaction time
 is the total elapsed time of a transaction. The TIM monitors the time from the first request packet to the last response packet.
CEMDefinitionHandler
The
CEMDefinitionHandler
 is an Enterprise Manager extension that receives and parses CA CEM business transaction definitions and passes the parsed definitions to registered agents.
The
CEMDefinitionHandler
sends transaction-trace requests agent, receives transaction trace data from the agents, and passes that data back to CA CEM.
CEMTracer
CEMTracer
 is a Release 8.2 CA Introscope; agent extension. This extension was replaced in Release 9.0 with BizTrxHttpTracer.
character encoding
CA CEM supports 16-bit characters in transaction data and definition names. CEM provides out-of-the-box support for Chinese, Japanese, and Korean character sets. These
character encodings
are supported:
  • ISO-8859-1
     -- the default character encoding for CA CEM; the standard that the ISO defines, an 8-bit single-byte coded graphic character set - Latin alphabet No. 1 (sometimes named Latin-1); generally intended for Western European languages; the HTTP and MIME text default.
  • UTF-8
     -- the Unicode Transformation Format 8-bit character set is a variable-length character encoding for Unicode. It can represent any character in the Unicode standard, and is backward compatible with ASCII; the standard for encoding Unicode on UNIX / Linux; the preferred standard for multilingual web sites.
  • UTF-16
    -- the Unicode Transformation Format 16-bit character set that is capable of encoding all 1,112,064 possible characters in Unicode. The encoding is variable-length.
  • EUC-JP
     -- a variable-width encoding that is used to represent the elements of three Japanese character set standards: JIS X 0208, JIS X 0212, and JIS X 0201; based on Extended UNIX Code (EUC), which is a multibyte character encoding system; Japanese character encoding for UNIX / Linux.
  • Shift-JIS
     -- a character encoding for the Japanese language that is originally developed by a Japanese company named ASCII Corporation with Microsoft and standardized as JIS X 0208 (also named SJIS, or by its MIME name Shift_JIS); Japanese character encoding for Microsoft Windows.
  • ISO-2022-JP
     -- a widely used character encoding for the Japanese language that is based on the ISO-2022 standard (also named JIS); employs a technique for including multiple character sets in a single character encoding; includes ASCII, uses escape sequences to switch to: JIS X 0201-1976 (1 byte per character), JIS X 0208-1978 (2 bytes per character), JIS X 0208-1983 (2 bytes per character); double-byte coded Kanji (Chinese characters that are used in Japanese writing).
  • Windows-31J
     -- a Microsoft Windows extension to Shift-JIS to accommodate NEC special characters and IBM extensions.
  • GB2312
     -- the registered name for an official character encoding of the People's Republic of China, used for simplified Chinese characters. GB abbreviates Guojia Biaozhun, which means national standard in Chinese (also GB 2312); Chinese, simplified.
  • Big5
     -- a character encoding method that is used in Taiwan, Hong Kong, and Macau for traditional Chinese characters (also Big-5); Chinese, traditional.
  • EUC-KR
     -- a variable-width encoding to represent Korean text using two coded character sets: KS X 1001 and KS X 1003; based on Extended UNIX Code (EUC), which is a multibyte character encoding system; Korean.
clamp
clamp
 is a configurable limit of the number of metrics that are returned for a specific function. Used in transaction trace clamping and metric clamping for various CA APM components such as agents and the Enterprise Manager.
Collector
An Enterprise Manager 
Collector
 is one that a Manager of Managers (MOM) manages in a clustered environment.
Common Language Runtime (CLR)
Common Language Runtime
 (
CLR
) is the Microsoft implementation of the Common Language Infrastructure (CLI). The purpose of the CLI is to provide a language-independent platform for application development and execution.
The .NET CLR is roughly equivalent to the Java platform JVM.
Console, Workstation
The 
Console
 is the default view when you start the Introscope Workstation; it contains dashboards that show performance data in graphical views.
container
container
 refers to a Java run-time environment for enterprise beans. A container that runs on an EJB (Enterprise JavaBeans) server manages the life cycles of enterprise bean objects, coordinates distributed transactions, and implements object security.
See also: transaction
Cross-cluster Data Viewer (CDV)
The
Cross-cluster Data Viewer (CDV)
is a specialized Enterprise Manager that gathers agent and customer experience metrics data from multiple Collectors across multiple clusters. Using the CDV Workstation, CA APM administrators and triagers can create and view dashboards. CDV dashboards show a consolidated view of agent and customer experience metrics that are provided by the Collectors. Each Collector can connect to multiple CDVs, allowing flexibility in monitoring and viewing applications that are reporting to different CA APM clusters.
dashboard
An Introscope 
dashboard
 combines and presents application metrics in views to monitor the overall application environment. Dashboards deliver the in-depth performance information that is needed for rapid problem triage, diagnosis, and resolution for production applications.
dead metric
dead metric
 has no new data reported within a given length of time. The amount of time is configurable in Introscope.
deep visibility component
deep visibility component
 is a method or component that Introscope discovers and displays automatically without the use of ProbeBuilder Directives (PBDs). When smart instrumentation is enabled, Introscope analyzes methods for their complexity to determine the calls and components to instrument and display as deep visibility components.
defect
defect
 is the failure of a transaction to conform to customer expectations and transaction specifications. Defects are categorized as 
behavioral
 and 
response
 defects.
A defect is a single transaction opportunity that failed. If a transaction does not meet multiple specifications, then multiple defects are generated (for example, slow time 
and
 missing components).
Defects can be tracked using the defect Pareto and other graphs.
This concept is not the same as defective transaction.
defect business impact
The 
defect business impact
 is calculated based on the impact level of the user who is affected, impact level of the transaction, and the impact level of the defect type.
CA CEM Calculation: defect business impact = business transaction impact level * defect type impact level * user impact level
defect Pareto graph
The 
defect Pareto graph
 shows the most frequently occurring defects. This graph was named after the Pareto principle, also known as the 80/20 rule, where 20 percent of problems cause 80 percent of the defects.
The left scale corresponds to the number of defects in each business service, as represented in the vertical red bars. The right scale and the blue line correspond to the cumulative percentage of defects in all the red bars (which represent for example, business services, business transactions, and defect types).
See also: defect
defect type
CA CEM 
defect types
 include: slow/fast time, low/high throughput, small/large size, HTTP status code, missing transaction/component, content error, missing response, partial response.
The CA CEM administrator can configure the transaction defects and their specification limits. For example, a transaction time greater than 5 seconds might be considered to be too slow.
See also: defect
defective transaction
defective transaction
 is a transaction with one or more defects.
This concept is different from a defect.
See also: good transaction
Defects Per Million Opportunities (DPMO)
Defects Per Million Opportunities
, or 
DPMO
, is used to compare one service to another. DPMO allows a fair comparison of services with widely varied opportunity costs.
CA CEM Calculation: DPMO = (total defects / total opportunities) * 1,000,000
domain
An Introscope 
domain
 is a way to partition agents and management logic, to define which users can see what information.
The CA CEM 
domain
 provides a way for the administrator to establish systemwide default values and settings for:
  • Expected transaction behavior
  • User and business impacts
  • Systemwide data retention
As you create user groups, business services, and transactions, you have the choice of inheriting CA CEM domain default values, or creating specific values (for example, SLA settings for users).
domain configuration information
The 
domain configuration
 information contains business service and transaction information, which have two purposes:
  • The internal CA CEM domain configuration (transactions and defect definitions), which is synchronized between CA CEM and the TIMs, and instructs TIM monitoring.
  • The domain configuration (transaction hierarchy), which is synchronized between CA CEM and Introscope, and is then passed to registered agents.
domainconfig.xml
In Release 8.2, the 
domainconfig.xml
 file is used as the method to integrate CA CEM and CA Introscope. Used in CA APM 9.0 only with older agents with CEMTracer installed.
dual-stack network
In a 
dual-stack network
, both IPv4 and IPv6 services and applications are supported. This requires hosts and routers to implement both IPv4 and IPv6 protocols.
The dual-stack approach is a common way to introduce IPv6 into an existing IPv4 architecture. This approach enables networks to support both IPv4 and IPv6 during the transition period, waiting for IPv6 services and applications to become more readily available.
dynamic instrumentation
Introscope 
dynamic instrumentation
 is used to implement new and changed PBDs without restarting instrumented applications for the Introscope agent.
dynamic property
A
 dynamic property
 in the Introscope configuration files (for example, the IntroscopeAgent.profile file) is deployed as soon as the configuration file is saved. You do not need to restart the application or application servers for the change to take effect.
EM extension
An Introscope 
EM extension 
is program code (JAR file) that extends the basic functionality of the Enterprise Manager. CEMDefinitionHandler is the EM extension for the integration between CA CEM and CA Introscope.
Embedded Entitlements Manager (CA EEM)
CA Embedded Entitlements Manager (CA EEM)
 is a CA Technologies application that allows other applications to share common access policy management, authentication, and authorization services.
Enterprise Manager (EM)
The 
Enterprise Manager
 (
EM
) stores and aggregates application performance metrics such as response time, bandwidth, and memory allocation. Multiple agents, spread throughout the enterprise, collect, and relay application and environmental metrics and report them to the Enterprise Manager.
entry point
When smart instrumentation and automatic entry point detection are enabled, Introscope automatically monitors threads that are involved in client socket call transactions. 
Entry points 
are the transaction beginning points. Entry points display in the agent-centric tree and transaction traces.
Environmental Performance Agent (EPAgent, EPA)
The 
Environmental Performance Agent (EPAgent, EPA)
 is a modified version of the agent that helps integrate metric data from generic and non-Java sources into Introscope. EPA uses simple scripts that allow Introscope to monitor virtually any type of application subsystem that has an impact on performance. For example, directory servers, operating systems, messaging middleware, and transaction servers).
error snapshot
CA APM ErrorDetector generates an 
error snapshot
, which displays detailed information about what was happening when an error occurred. Error snapshot data are stored in the Transaction Event database.
See also: ErrorDetector
ErrorDetector
CA APM 
ErrorDetector
 allows application support personnel to detect and diagnose the cause of serious errors, which can prevent users from completing web transactions.
Predefined "serious" errors that are based on information that is contained in the PHP, J2EE and .NET specifications include these errors:
  • HTTP errors (for example, 404 and 500)
  • SQL statement errors
  • Network connectivity errors (time out errors)
  • Backend errors (for example, cannot send a message through JMS, cannot write a message to the message queue).
See also: error snapshot
event
An Introscope 
event
 is any action for which agents capture metrics. Examples include transaction traces, errors, and stalls.
Event Manager
The CA CEM 
Event Manager
 captures and logs system events such as communication failures or database space warnings.
evidence collection
An 
evidence collection
process can be initiated when an incident is opened, and when the business impact thresholds are exceeded on an incident. The evidence collection process might include initiating system statistics gathering, data collection, script execution, and so on.
Evidence that is collected might include performance, availability, utilization, and configuration information useful in identifying and resolving the cause of an incident.
extension
Extensions
 are CA APM applications that extend the data monitoring capabilities of Introscope. Extensions easily integrate with the core Introscope components, allowing for ease of use and integration into an already established Introscope environment.
Federal Information Processing Standards (FIPS)
Federal Information Processing Standards (FIPS)
 are publicly announced standards. The U.S. Federal government developed these standards for use by all nonmilitary government agencies and by government contractors. Many FIPS standards are modified versions of standards that are used in the wider software industry.
The FIPS 140-2 publication, "Security Requirements for Cryptographic Modules," specifies the security standard for the cryptographic libraries. This publication specifies the algorithms that software products should use for encryption. Encryption affects the storage and verification of passwords, and the communication of all sensitive data between components of a product and between products.
CA CEM is FIPS 140-2 compatible. CA CEM uses FIPS-compliant cryptographic libraries and algorithms to encrypt and decrypt sensitive data, such as passwords, HTTP defect information, and user session IDs.
Flex parameters
CA CEM extracts 
Flex parameters
 from the AMF messages in an HTTP request or response transaction body. Flex parameters contain data that is used by an Adobe Flex application.
frontend
frontend
 is the component of an application that first handles an incoming transaction. In most typical J2EE applications, this component is a servlet or a JSP. In some Java instances, it can be an EJB or some other component. Introscope automatically identifies servlets and JSPs as frontends, but not any other component. To mark a component as a frontend explicitly, use the FrontendMarker tracer.
See also: backend
good transaction
good transaction
 is a transaction with zero defects.
group
group
, in CA CEM, is used to describe multiple users and multiple services. Measurements are 
aggregated
 in a group; measurements are 
calculated
 on a set.
GUID
The 
GUID
 (globally unique identifier) is a unique key that ServletHeaderDecorator produces. The key identifies a transaction in the monitored business application. The GUID is the key information that correlates transactions between CA CEM and Introscope.
GUIDs can be created in a number of ways. Usually GUIDs are a combination of unique settings that are based on a specific time. For example, a GUID can be a combination of an IP address, network MAC address, date, and time.
heartbeat
heartbeat
 is the time interval when metrics are checked, usually in seconds.
heuristic metrics
Introscope 
heuristic metrics
 are used to evaluate and report status. They are integers, but the integers are symbols of status and do not measure anything. The value of a heuristic metric is determined by evaluating current metrics against a baseline for those metrics.
By defining alerts in terms of the heuristic metrics rather than fixed thresholds, the work of determining normal values for Key Performance Indicators shifts from the Introscope administrator to Introscope.
hidden property
hidden property
is a property in a configuration file. The property is only available for use when you add the property to the configuration file. For example, a configuration files is the IntroscopeAgent.profile file, or the IntroscopeEnterpriseManager.properties file. 
HTTPHeaderDecorator
The Introscope 
HTTPHeaderDecorator
 augments HTTP response headers for .NET agents. This capability allows CA CEM:
  • To display application server details for defective transactions.
  • To present hyperlinks from defect and incident detail pages to transaction traces in the Workstation Investigator.
The GUID is used as the transaction identifier, matching transactions that are monitored in CA CEM with transactions that the Introscope Transaction Tracer has captured. HTTPHeaderDecorator is an Introscope agent extension.
identifying component
The 
identifying component
 is the first transaction component in the transaction component set. The identifying component uniquely identifies the start of a transaction. An identifying component must not be a component of any other transaction.
A redirect can appear as the first component in a transaction recording, yet it is not the identifying component.
identifying transaction
The 
identifying transaction
 is the first transaction in a business transaction set. The identifying transaction uniquely identifies the start of a business transaction. An identifying transaction must not be a transaction of any other business transaction.
impact level
The 
impact level, 
or cost to the business, can be set in CA CEM at several levels.
The business impact of a defect depends on the impact level of these factors:
  • Transaction that is associated with the defect.
  • Defect type.
  • User that executed the defective transaction.
Each impact level has a corresponding value, or weight, which is used in calculating business impacts. These numerals are the weights:
0 ignore
1 minimum
2 very low
3 low
4 medium (the default)
5 high
6 critical
7 trigger immediately (forces a moderate incident immediately)
The business impact weights appear on the Impact Leaders and Defects pages.
By default, the user impact level setting is inherited from the user-group setting for the user the executed the transaction. By default, the transaction impact level setting is inherited from the business service setting for the transaction, which in turn is inherited from the CA CEM domain setting.
impact threshold
The 
impact threshold
 is a trigger point for incidents and for evidence collection. Values, or weights, are set at the CA CEM domain level for three thresholds:
  • Moderate (default = 1000)
  • Severe (default = 2500)
  • Critical (default = 5000)
When an impact threshold is exceeded for an incident, then the severity state changes. Escalating impact thresholds can also initiate evidence collection, or automated actions such as the creation of a trouble ticket.
incident
A CA CEM 
incident
 represents a group of defects that are correlated based on transaction type and defect type. Incidents represent business-affecting problems that have affected enough end users that the business must act to correct the problem.
incident business impact
The 
incident business impact
 is calculated by adding all the business impacts of the defects that are included in the incident.
CA CEM Calculation: incident business impact = defect1 business impact + defect2 business impact ... + defectn business impact
incident cost
The CA CEM administrator sets an 
incident cost
 (in currency) that is applied to all open (active) incidents. For example, if an incident affects 10 users for 45 minutes and the incident cost is set to $1, the total cost of the incident is calculated as 10 * 45 * 1 or $450.
Incident cost is used to estimate the cost of poor quality on the business. Incident cost can include direct costs such as lost productivity and indirect costs such as loss of reputation and goodwill.
The incident cost does not include any user activity that has been assigned to the group of unspecified users. The incident cost can be used to calculate lost value (or revenue) for each incident.
CA CEM Calculation: incident cost = cost-per-user-per-minute * number of users * incident duration in minutes
Used in CA CEM Calculation: net IT value add = IT value - incident cost
incident severity
The 
incident severity 
reflects the seriousness of the incident and its related defects. The possible incident severity states are:
  • Low - the incident has been generated but no threshold has been exceeded
  • Moderate - the moderate threshold has been exceeded
  • Severe - the severe threshold has been exceeded
  • Critical - the critical threshold has been exceeded
incident state
The 
incident state 
reflects the status of the incident and its related defects. These incident states are possible:
  • Pending - has at least one defect; the moderate threshold is not yet exceeded, or incident generating rules have not yet been met.
  • Open - the moderate threshold has been exceeded and it is not closed.
  • Closed - the CA CEM operator has closed this incident.
  • Aged out - the incident age-out rules have been met.
Instance Type
Instance Type
 is a specification that defines the memory, CPU, storage capacity, and hourly cost for an instance in Amazon Web Services (AWS). Instance types can be designed for standard applications or CPU-intensive, memory-intensive applications.
instrumented
Application code is 
instrumented
 when ProbeBuilder inserts probes, within the byte code, to send metrics to the agent.
Introscope
Introscope
is an enterprise application performance management solution that enables you to:
  • Monitor complex applications in production environments 24 hours a day, 7 days a week.
  • Detect problems before they affect your customers.
  • Resolve these issues quickly and collaboratively.
Investigator, Workstation
The Workstation 
Investigator
 allows you to view the application and system status, to search, and to browse metric data using a tree structure. You can have more than one Investigator window open simultaneously.
IT value
The CA CEM administrator can set an 
IT value
 per business transaction in currency (for example, $.010 per transaction). The currency number is used to calculate the value that IT provides to the business by delivering the transaction.
The IT value quantifies the business value of successfully delivering transactions to customers on behalf of the business.
CA CEM Calculation: IT Value = IT-value-per-business-transaction * number of business transactions
Used in CA CEM Calculation: net IT value add = IT value - incident cost
Java agent
The 
Java agent
 collects metrics in Java environments.
LeakHunter
CA APM 
LeakHunter
 allows application support personnel to detect and diagnose the cause of memory leaks.
listener port
listener port
 is used to simplify administration of the association between a connection factory, destination, and deployed message-driven bean.
live metric
live metric
 has actively reporting data from a specific agent.
logic time
The 
logic tim
e is the measure of time that the suspected Blame component program code takes to complete. This time is based on Introscope reporting.
MAC address
The 
MAC address
 (Media Access Control address) is a hardware address that uniquely identifies each node of a network. CA CEM returns the MAC address in the response of the server for every defective transaction (when available).
The MAC address can be useful during the problem resolution process when web servers are located behind a loadbalancer that masks the true identity of the web server at the IP level. For example, in Resonate load balancing environments, all web servers appear to have the same IP address. However, the MAC address that is sent in the response can uniquely identify the servers.
managed application
When an instrumented application is running, it is named a 
managed application
.
See also: instrumented
Management Module
An Introscope 
Management Module
 contains a set of monitoring configuration information. Management Modules are listed for each domain, and contain elements. Elements are objects that contain and organize data with monitoring logic such as alerts, actions, and dashboards.
Manager of Managers (MOM)
The Introscope 
Manager of Managers
 (
MOM
) stores metrics as reported by multiple Enterprise Managers. Enterprise Manager clustering allows one Enterprise Manager -- the MOM -- to manage other Enterprise Managers. Each of the managed Enterprise Managers, named Collectors, collects agent metrics and, in turn, relays those metrics to the MOM.
median value
The 
median value
 is a single value representing a data distribution. The median value is preferred to the average value as a single-number representation of a distribution when the distribution is not a normal (bell curve) distribution.
CA CEM Calculation: The middle point of a data set, where 50 percent of values are below, and 50 percent above this point.
metric clamp
metric clamp
 is a limit, or clamp, on the number of metrics on the agent and the Enterprise Manager. A metric clamp helps to prevent spikes in the number of reported metrics (metric explosions) on the Enterprise Manager.
metric explosion
metric explosion
 occurs when new metrics appear in large numbers over a short time. Misconfigured metric definitions can cause metric metadata to change with metric value changes, and appear as new metrics. For example, variable strings in a SQL metric. Misconfigured agent connection properties for a set of new agents can cause thousands of new metrics to overload the Enterprise Manager. These situations can reduce performance.
metric grouping
Metric groupings
 are Management Module objects that save this information:
  • The 
    agent expression --
     A regular expression in Perl 5 that filters input to the metric by specifying the data up to and including the agent name.
  • The 
    metric expression
     -- A regular expression in Perl 5 that specifies the resource (the chain of folders leading to the metric) and the metric.
  • The Management Module to which the metric grouping belongs.
metric leak
metric leak
 occurs when an Introscope misconfiguration results in agents reporting metrics for a limited time. This problem results in a gradual build-up of metric metadata without associated metric data.
metric throttle
metric throttle
 stops an agent when its metric output becomes excessive.
metric, Introscope
An
 Introscope metric
 is a measurement of application performance. Introscope metric types are:
  • Bandwidth -- JVM and CLR-level file and socket activity
  • Concurrency -- number of method invocations that are started but not yet finished
  • Count -- number of method invocations to date
  • Exception -- captures exceptions
  • Memory -- memory that is allocated to the JVM or CLR in use, as related to garbage collection
  • Rate -- number of method executions per second or time interval
  • Response time -- average method execution time in milliseconds
  • Stalled methods -- number of methods that are started but whose invocation times have exceeded a threshold
  • System logs -- monitors system out and system error output
  • Threads -- number of instrumented threads
mirrored port
mirrored port
 is a software feature of network routers and switches.
See also: network tap
missing component
A
missing component
defect is generated when a non-cacheable component of a transaction is missing. A request for this component was not observed within the expected configurable time period (the default is 10 seconds).
missing response
missing response
 means that a request for a particular component was observed, but no response was observed within the configurable period. The default time period is 60 seconds.
See also: partial response
missing transaction
A
missing transaction
defect is generated when a non-cacheable transaction of a business transaction is missing. A request for this transaction was not observed within the expected configurable time period (the default is 10 seconds).
MOM failover
Introscope 
MOM failover
 occurs when the MOM Enterprise Manager gets disconnected or goes down due to a hardware or network failure. The failover occurs when you have configured a second MOM Enterprise Manager to take over the first MOM Enterprise Manager.
monitor
Agents 
monitor
 end-to-end web performance, Java components and their dependencies, CLR components and their dependencies, connections to backend systems, and resource levels (including third-party software) and application server resources.
A CA CEM 
monitor
 is a Transaction Impact Monitor (TIM). TIMs monitor transactions and report defects and statistics to CA CEM.
net IT value add
The 
net IT value add
 is the sum of the IT value for a time period minus the sum of the incident cost for the same time period. The net IT value add represents all the benefit IT delivered to the business by delivering good transactions minus all the cost to the business resulting from customer-affecting incidents.
For example, if 100,000 transactions with an IT value of $.010 were successfully delivered in a day and a single incident with an IT cost of $450 occurred during that day the net IT value add would be (100,000 * $.010) - $450 = $550.00.
CA CEM Calculation: net IT value add = IT value - incident cost
Used in CA CEM Calculation: total business value = net IT value add + business value add
Network and Systems Management (NSM)
CA 
Network and Systems Management
 (CA NSM) is a CA product.
network tap
network tap
 is a hardware device that taps directly into the infrastructure cabling. This device creates copies of packets and forwards them on to one or more destinations.
See also: mirrored port
node
node
 is where specific metric information is gathered and displayed in the tree view of the Introscope Investigator. For example, the Investigator shows the backends node or the CPU usage node. When the node is expanded, more detailed metric information can be viewed and searched.
non-cacheable
non-cacheable
 transaction or component is one that the browser client or proxy server cannot cache. The TIM must observe the transaction or component when it is marked as non-cacheable. When it is missing, a missing component or missing transaction defect is generated and the transaction is marked as defective.
Operating Level Agreement (OLA)
An 
Operating Level Agreement (OLA)
 is a contract between an IT organization and the internal support groups. The terms of the contract depend on the needs of the parties involved. OLAs are used to manage service commitments by IT groups for compliance.
opportunity
An 
opportunity
 is any area within a product, process, service, or other system where a defect might occur. In general, more complex products mean more opportunities for defects.
In CA CEM, an opportunity occurs every time a transaction or component must pass or fail a defect test. Depending on how many specifications are configured, this number could be up to six opportunities per component (slow time fast time, low throughput, high throughput, content error, server error). Transactions could have up to seven opportunities because they also can have a missing component.
See also: defectspecification
parameter name pattern
CA CEM includes several private parameters with the default configuration. The following 
parameter name patterns
 are examples: pin, *ssn, *password, *passcode. (The asterisk "*" is a wildcard character.)
partial response
partial response
 means that a complete response was not observed for a particular component within the expected configurable time period (the default is 60 seconds).
See also: missing response
pending incident
pending incident
 has at least one defect, where incident generating rules have not yet been met, nor has an impact threshold been met.
The CA CEM administrator provides systemwide settings and values that establish when an incident changes state from pending to open, or to aged-out. For example, an incident changes state when the number of defects within a period rises above a certain threshold, or if the combined business impact of its defects is above a certain threshold.
percentile value
The 
percentile value 
of a distribution is a number where a percentage of the distribution is less than or equal to that percentile value. For example, the 25th percentile (also referred to as the lower quartile) is where 25 percent of the data values fall below it.
In another example, for a response time graph, the number at the 95th percentile means 95 percent of the transactions in that time period had a response time at that level or less.
performance metrics
CA CEM 
performance metrics
 are measurements in terms of success rate, total, good, and defective.
Performance metrics are familiar to IT professionals and are calculated on transactions and business transactions. Performance metrics represent distributions as averages.
PHP agent
The 
PHP agent
 collects metrics in PHP applications.
private parameter
private parameter
 is a transaction parameter that the CA CEM administrator identifies as private for security or privacy reasons. The values for the identified parameters are masked with asterisks when observed in a transaction.
CA CEM includes several private parameters with the default configuration, for example: pin, *ssn, *password, *passcode. (The asterisk "*" is a wildcard character.) CA CEM administrators can add to the list of private parameters.
probe
A probe
 measures specific pieces of information about an application without changing the business logic of the application. An agent is installed on the same computer as the instrumented web application.
ProbeBuilder
Introscope 
ProbeBuilder
 performs the instrumenting process, in which tracers identify the metrics that an agent gathers from web applications and the virtual machines at runtime. The tracers are defined in ProbeBuilder Directives (PBD) files.
ProbeBuilder Directive (PBD)
ProbeBuilder Directive (PBD)
 files tell ProbeBuilder how to add probes, such as timers and counters, to PHP, .NET or Java components to instrument the application. ProbeBuilder Directive files govern the specific metrics that agents report to the Enterprise Manager.
Custom Directives can also be created to track classes and methods unique to specific applications.
ProbeBuilder Lists (PBL)
ProbeBuilder List (PBL) 
file contains a list of multiple ProbeBuilder Directive files. Multiple PBL files can refer to the same PBD files.
ProbeBuilding, dynamic
Dynamic ProbeBuilding
is useful for making corrections to PBDs, or to change data collection levels during triage without interrupting application service.
processing time
In App Synthetic Monitor, the 
processing time
 is the period after the HTTP request is sent and the monitor waits for the first bytes of the result.
quality metrics
CA CEM 
quality metrics
 are measurements in terms of defects, opportunities, yield, Sigma, and DPMO.
Quality metrics are familiar to Quality professionals, whether within IT or without, and are calculated principally on opportunities. Quality metrics represent distributions as medians.
RADV
RADV 
is an acronym for Router Advertisement. In IPv6, router discovery can be accomplished using routers sending router advertisement messages. Discovery can be both on a regular basis, and in response to prompting of hosts with router solicitation messages. RADV can be used to announce IPv6 to the LAN (local area network).
range
In a box-whisker graph, the 
range
 is the interval between the minimum and maximum values.
recorder
The 
recorder 
tracks all Web browser activity from a particular client computer (IP address). The recorder identifies examples of the transaction to be monitored. The resulting transaction recording is used in the transaction definition process. The recording simplifies the process of creating transaction recognition and demarcation rules.
report type
In the CA CEM graphical analyses, the 
report type 
shows either a comparison of values (for example, comparing defect types), or a time series, which compares transactions on a per-hour basis.
request-based transaction
request-based transaction
 is a business transaction that CA CEM identifies based on the HTTP request parameters. Response-based transactions extend from a request-based transaction.
response defect
response defect
 is a defect that can be identified by analyzing the responses of a transaction. Response defects are measured in terms of success rate, total, good, and defective.
Response defects are detected by analyzing the HTTP header for the occurrence of an HTTP response code that indicates a defect has occurred. Response defects are also detected by analyzing the full content of the response for the occurrence of error messages or other content patterns indicating that a defect has occurred.
See also: defect
response-based transaction
response-based transaction
 is a business transaction that CA CEM identifies based on the HTTP response parameters. A response-based transaction definition is extended from a request-based transaction definition. When you create a request-based transaction definition, it is independent of other definitions. However, the response-based transaction definition is dependent on and is built from the request-based transaction definition.
rule set
rule set 
is regular expression patterns for parameter names/values that identify CA CEM transactions. The rule set is used to enable Introscope transaction traces.
Each agent extension creates its own rule set based on parsed domain configuration information (CA CEM business transaction definitions), which it receives from the Enterprise Manager.
SARM
Siebel 
SARM
 (Siebel Application Response Measurement) allows for response-time measurement of Siebel applications within a Siebel environment.
CA CEM captures Siebel SARM correlation data, which can be used to query Siebel to gather evidence that is related to a specific user and transaction.
script recorder
The 
script recorder
 is used to convert packet capture (pcap) files or HP LoadRunner VuGen log files into transaction recordings.
security user group
A CA CEM 
security user group
 defines the security access and privileges available to a user of APM and the CEM console user interface.
The default CA CEM security user groups are:
  • Admin -- has both Introscope and CA CEM access, and is given both Introscope Admin and CEM System Administrator privileges.
  • CEM System Administrator -- manages all CA CEM system administration functions.
  • CEM Configuration Administrator -- manages the general CA CEM configuration settings.
  • CEM Analyst -- has access to CEM reports and views only.
  • CEM Incident Analyst -- has access to CA CEM reports and views, including HTTP information about defects.
See also: EEM
ServletHeaderDecorator
The Introscope 
ServletHeaderDecorator
 augments HTTP response headers from servlets for Java agents. This capability allows CA CEM to:
  • Display application server details for defective transactions.
  • Present hyperlinks from defect and incident detail pages to transaction traces in the Workstation Investigator.
The GUID is used as the transaction identifier, matching transactions that are monitored in CA CEM with transactions that the Introscope Transaction Tracer captures. ServletHeaderDecorator is an agent extension.
set
set
, in CA CEM, is a compound object (for example, a set of transactions). Measurements are 
calculated
 on a set; measurements are 
aggregated
 in a group.
Sigma
The 
Sigma
 score (also known as Z score) is a value that is used in the Six Sigma system as a measure of defects in a service.
The Sigma score ranges from 0 to infinity. In general, a higher Sigma score is better. Services with zero defects have an infinite Sigma score and are represented with an asterisk (*).
Do not confuse the Sigma score with the standard deviation, which the Greek symbol sigma (Σ) commonly represents. The Sigma score is inversely proportional to the standard deviation.
In CA CEM, the Sigma score includes a 1.5 Sigma process shift.
See also: SLA, Sigma
Sigma SLA
Sigma Service Level Agreement (SLA)
 is a number that indicates service quality level. The default is 4.00 (approximately 6,200 defects per million opportunities), where 6.00 is near perfection (approximately 3.4 defects per million opportunities).
SiteMinder
CA 
SiteMinder
 is an application that provides security features such as single sign-on and centralized control of user access to web applications.
smart instrumentation
Smart instrumentation
 is a method that Introscope uses to instrument applications. This method uses highly optimized low overhead tracers. The tracers allow agents to discover and automatically instrument more methods to provide deep visibility components without the use of ProbeBuilder Directives (PBDs). Smart instrumentation also provides automatic transaction tracing.
SmartStor database
The Introscope 
SmartStor database
 is a nonrelational database that records all application performance data (Introscope metrics) at all times. This database enables users to analyze historical data, to identify root causes of application downtime, or perform capacity analysis without the need for an external database.
SmartStor is enabled by default during Introscope installation. SmartStor data is set to age out over time, so the data store will not get excessively large. There are multiple data files and they grow in number as more data is generated.
span
In a box-whisker graph, the 
span
 is the difference between the values from the 5th to 95th percentile.
CA CEM Calculation: span = 95th percentile value - 5th percentile value
specification
specification
 is a requirement for a transaction or a component of a transaction. If a transaction or a component does not meet the requirement that is established in the related specification, it is defined as a defect. For example, a slow time defect can be defined as any transaction time greater than 5.00 seconds.
Using the baseline rather than fixed thresholds, determining defect specification normal values shifts from the CA CEM administrator to CA CEM itself.
stall
An Introscope 
stall
 usually refers to methods that have started but with invocation times that have exceeded a threshold.
start-up bubble
start-up bubble
 is the temporary timeframe when there is high resource demand that can affect more than Introscope metrics reporting. During the start-up bubble, your instrumented application might become unresponsive.
It is possible for other components, sharing resources with the instrumented application or in the same environment, to be affected. The start-up bubble can be observed with the .NET agent at start-up time.
See also: .NET agent
stateful plug-ins
Stateful plug-ins
are expected to be long running scripts (such as daemons). Stateful plug-ins start when the Environment Performance Agent (EPAgent) starts and run forever, feeding data back into Introscope through the standard output channel of the plug-in. When a stateful plug-in terminates, the EPA restarts it.
stateless plug-ins
Stateless plug-ins
 are designed to run on a recurring schedule and are configured with the frequency (specified as delay between runs) at which they should be run. Stateless plug-ins are expected to be short-running scripts that simply collect some data, send it to the Environment Performance Agent (EPA) through the standard output channel, and terminate. No special error-checking is done by the EPA to ensure only one instance of a stateless plug-in is running at one time, so plug-in developers are required to design their stateless plug-ins to run and complete in a reasonably short timeframe.
success rate
The 
success rate
 measures the percentage of transactions that are defect-free.
CA CEM Calculation: success rate = 1 - defective count / total count
SuperDomain
The 
SuperDomain
 node contains metrics for all agents that report to the Enterprise Manager to which the Workstation is connected, and includes all user-defined domains and agents. This node is only visible to users with SuperDomain access. Metrics are organized in a Host|Process|Agent hierarchy.
supportability metrics
Introscope 
supportability metrics
 help support the healthy functioning of the Enterprise Manager itself. The Enterprise Manager generates and collects metrics about itself that are useful in assessing its health and determining how well it is performing under its workload.
suspected Blame backend component
The 
suspected Blame backend component
 is the most specific portion of the backend time that is identified as being the suspected cause of delay in a slow transaction. In Introscope, the suspected Blame backend component appears as the widest, but not necessarily the lowest, backend component in the graph.
It is the
slowest lowest
backend component, not the
lowest slowest
backend component in the Introscope graphs.
The suspected Blame backend component is identified by taking the lowest backend component that takes longer than ¼ of the overall backend time to complete.
suspected Blame component
The 
suspected Blame component
 is the most specific portion of logic (or program code) that is identified as being the suspected cause of delay in a slow transaction. In Introscope, the suspected Blame component appears as the widest, but not necessarily the lowest, component in the graph.
It is the
slowest lowest
component, not the
lowest slowest
component in the Introscope graphs.
The suspected Blame component is identified by taking the lowest (non-backend) component that takes longer than ¼ of the overall transaction time to complete.
sustainability metric
sustainability metric
 provides information about the internal state of the agent rather than the application the agent is monitoring. This data can help you investigate agent behavior.
synchronize all monitors
The CA CEM administrator must 
synchronize all monitors
 to enable monitoring communications between CA CEM and the TIM monitors. Synchronizing all monitors pushes the transaction and defect definitions from CA CEM to the 
enabled
 TIMs. In other words, synchronizing monitors puts the configuration into production.
Synchronizing all monitors also causes CA CEM to send transaction and tracing information to the Introscope Enterprise Manager, which in turn sends to the agents.
time to first response
The 
time to first response
 is the elapsed time from the 
last
 packet of the request to the first packet of the response for the component.
The time to first response varies, based on the type of defect being tracked:
  • Component defect, the time to first response for that component
  • Transaction defect, the time to first response for the identifying component of the transaction
  • Business transaction defect, the time to first response for identifying component of the identifying transaction
This setting can be changed to the
first
packet of the request to the first packet of the response. If you need this setting to determine inbound network latency, contact CA Support.
Changing this setting affects only new data. (Existing data values are based on the time to first response setting that was in place at the time the data was collected).
total business transactions
CA CEM 
total business transactions 
is the count of all transactions of a process for a time period.
total business value
The CA CEM 
total business value
 is a combination of net IT value add and business value add.
CA CEM Calculation: total business value = net IT value add + business value add
transaction
An Introscope 
transaction
 is the invocation and processing of a service. It is a complete processing cycle, where the application context defines completion:
  • In the context of a web application, it is the invocation and processing of a URL sent from a Web browser.
  • In the context of a web service, it is the invocation and processing of a SOAP message from a web services client.
Introscope can capture transactions and can include detail about the request that is made to the service and the details that are related to processing the service, such as calls made to a SQL database.
A CA CEM 
transaction
 is a set of transaction components that generally represents one request to the application server.
A transaction typically consists of an HTML component, followed by zero or more subcomponents (for example, CSS style sheet, JS JavaScript files, GIFs and JPG images). For each transaction, there is one identifying transaction component.
A single user action can result in one or multiple transactions, which are encapsulated in a business transaction.
transaction component
A CA CEM 
transaction component
 represents one HTTP request/response pair that makes up an HTML component or subcomponent.
The first transaction component in a transaction is also known as the identifying component.
transaction definition
A
transaction definition
is information that the TIM uses to identify a transaction uniquely as it passes through the network. You can create a transaction definition using the CA CEM recorders or manually using the CEM console.
Transaction Events database
The Introscope 
Transaction Events database
 contains detailed transaction data. This data includes transaction traces, stalls, and data that is collected from triggered events, such as error snapshots.
The Transaction Events database typically resides in the traces directory, and spans multiple files. One file is created per day, and the data is kept for the number of days specified.
transaction hierarchy
CA APM information and metrics are organized into a 
transaction hierarchy.
 This hierarchy is a way of translating business services and transactions down to the technical HTTP elements that create the customer experience.
The CA APM transaction hierarchy is:
business application is a software program that automates a business service. Every transaction (using business service, business transaction, and finally transaction) is associated with a business application.
Example: Siebel
Example: Avitek
business service is an arbitrary group of business transactions. 
Example: Avitek Financial (includes buying, selling, querying)
Example: Siebel Call Center (includes login, plus other Siebel business transactions)
business transaction is a set of transactions that represents one user action. 
Example: Buy-related Set (might include several buy-related transactions)
Example: Sell-related Set (might include several sell-related transactions)
transaction is a set of transaction components that generally represents one request to the application server.
Example: Buy (the actual buying transaction)
Example: Buy Price Query (a buy-related query)
business transaction component is used in Introscope as an alternative to the full set of transactions and transaction components belonging to a business transaction. The business transaction component corresponds to the identifying transaction component of the identifying transaction, for which it is named.
Example: Submit Buy (the identifying element for the transaction, 
and
 the identifying transaction for the business transaction)
transaction component is a low-level element that represents one HTTP request/response pair. 
Example: Submit Buy (the identifying element of the transaction which might be JavaScript)
Example: main.css (a nonidentifying, but critical element of the transaction)
transaction parameter is the lowest level element in the hierarchy; an HTTP name/value pair.
Example: URL Path=/dir/file.html (the identifying element of the component)
Example: Cookie=JSESSIONID
Transaction Impact Monitor (TIM)
Transaction Impact Monitor (TIM)
 server is responsible for:
  • Recording and observing HTTP packets
  • Identifying user log ins and the related transactions
  • Monitoring and reporting defects and other statistics to CA CEM
One or more TIMs can exist in a CA CEM environment.
transaction parameter
transaction parameter
 is an HTTP name/value pair, which consists of a type, a name, and a pattern. Examples include URL, query, post, and cookie (for example: URL Host=www.company.com).
Using a combination of transaction parameters, a CA CEM administrator can identify and validate the presence of a required transaction component.
transaction recorder
The 
transaction recorder
 is used to record transaction details using a variety of methods. Two types of recorders exist: the recorder and script recorder.
transaction signature
The 
transaction signature
 is the output of a transaction recorder and contains information about an individual transaction.
After the signature is created, the CA CEM administrator can analyze, refine, and then promote the transaction signature into a generalized transaction definition.
transaction size
The 
transaction size
 is the size, in bytes, of the HTTP traffic observed for a transaction. The size includes the HTTP header, and both the HTTP requests and responses. The size does not include Ethernet, IP, and TCP headers.
transaction throughput
CA CEM 
transaction throughput
 is used as a measure of efficiency, especially for transactions that vary widely in terms of time and size. A higher throughput means a more efficient transaction.
CA CEM Calculation: transaction throughput = transaction size / transaction time
transaction time SLA
The
 transaction time Service Level Agreement (SLA) 
is the total elapsed time of a transaction, which is represented in seconds. The default is 8 seconds.
transaction trace
transaction trace
 is the output from the Introscope Transaction Tracer. The trace contains a list of components that are called during a transaction, and their associated duration times.
transaction trace duration
The 
transaction trace duration 
is the execution time for the 
transaction trace session
. The maximum transaction trace session duration is a time limit. The default value is 30 minutes.
transaction trace time threshold
The 
transaction trace time threshold 
is the execution-time limit for the 
transaction
. When a transaction trace is running, all transactions that do not complete within the threshold are traced.
The transaction trace time threshold is a percentage, which is based on the slow time defect specification. For example, the slow time defect specification is set to 8.00 seconds, and the transaction trace time threshold is set to 25 percent. All transactions with a suspected Blame component (logic time) greater than 2.00 seconds are traced.
Transaction Tracer
Introscope 
Transaction Tracer
 monitors the activity of individual transactions as they flow through these boundaries:
  • Of a single Java virtual machine (JVM)
  • The Common Language Runtime (CLR) virtual platform, in the case of .NET.
The Transaction Tracer reduces the time that is required to identify problem components in a transaction. The tracer lets you trace transaction activity at the component level. BizTrxHttpTracer initiates the Transaction Tracer on behalf of CA CEM, using transaction information that is contained in the agent rule set.
transfer time
In App Synthetic Monitor, the 
transfer time
 is the period taken to complete the HTTP response data.
transaction volume
The 
transaction volume
 is the sum of sizes of all transactions for a specified time period.
triage
Triage
 is the process of:
  1. Gathering information relevant to a problem.
  2. Deciding the problem severity.
  3. Assigning the problem to the person who can fix it most quickly. The person who handles this stage of problem analysis can be named a triager.
See also: WebViewWorkstation
upper specification limit (USL)
The 
upper specification limit
, or USL, is a numerical value defining the highest acceptable value for the characteristic. For example, a USL can be the highest acceptable transaction throughput.
user group
In CA CEM, a 
user group
 allows you to configure settings for a collection of (monitored) users instead of having to configure the settings for each individual user separately. User groups can be defined so you can easily identify (monitored) user populations that might be experiencing problems. A user belongs to only one user group.
You can create new (monitored) user groups manually, and you can move users manually into their user groups. CA CEM also provides ways to create user groups automatically.
Several types of (monitored) user groups exist:
  • Request attribute user groups -- users who are grouped by the content within the HTTP request they are making.
  • Subnet user groups -- groups that have automatic assignment of new users by user subnet.
  • Manually created user groups -- users must be manually moved from the New Users group (or another user group) into this type of user group.
  • New Users -- when no automatic user group generation method is selected, all new user logins are assigned to the new users group.
  • Unspecified Users -- all electronic commerce transactions are assigned to the unspecified users group. Also enterprise transactions that occur before a user logs in are assigned to the unspecified users group.
user processing type
The CA CEM 
user processing type 
determines the amount of user-based statistics that the TIMs gather and store in the database. Two user processing types exist: enterprise and electronic commerce.
For enterprise business applications, detailed per-user statistics are stored per hour and per transaction. This user processing type provides the most detail about individual users. A significant increase can occur in disk storage usage for business applications with high user counts.
For electronic commerce business applications, detailed per-transaction type statistics are stored per hour and per transaction. This setting provides maximum scalability for high volume electronic commerce business applications. You can achieve significant savings in disk storage usage with this user processing type.
Web Services API
CA CEM
 Web Services API 
lets you extract data from CA CEM for use in external reporting systems, or for integration with third-party products.
WebView
APM WebView
 presents the customizable dashboards and Investigator tree views in a browser interface. WebView allows critical information to be viewed without the aid of the Workstation.
Workstation
The Introscope 
Workstation
 allows you to control Introscope and access performance metrics. You can:
  • Set alerts for individual metrics or logical metric groups.
  • View performance metrics.
  • Customize views for your own unique environment.
Workstation Web Start
Introscope 
Workstation Web Start uses 
Java Web Start to start the Introscope Workstation.
yield
The 
yield
 is a measure of quality that is represented as a percentage. Yield represents the capability of the process to produce defect-free results.
CA CEM Calculation: yield = 1 - defects / opportunities
See also: defectopportunity