apm_9.5 transaction definition guide
TRANSCRIPT
-
8/11/2019 APM_9.5 Transaction Definition Guide
1/211
Transaction Definition GuideRelease 9.5
CA Application PerformanceManagement
-
8/11/2019 APM_9.5 Transaction Definition Guide
2/211
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.
-
8/11/2019 APM_9.5 Transaction Definition Guide
3/211
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)
-
8/11/2019 APM_9.5 Transaction Definition Guide
4/211
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)
-
8/11/2019 APM_9.5 Transaction Definition Guide
5/211
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 -
8/11/2019 APM_9.5 Transaction Definition Guide
6/211
-
8/11/2019 APM_9.5 Transaction Definition Guide
7/211
Contents 7
Contents
Chapter 1: Introducing the transaction definition process 13
About this Guide ........................................................................................................................................................ 13
What you need to know ...................................................................................................................................... 14
About transaction identification ................................................................................................................................ 14
HTTP request parameter types ........................................................................................................................... 14
Response-based transactions ............................................................................................................................. 16
HTTP and HTML Response parameter types ....................................................................................................... 17
Monitoring Flex applications ............................................................................................................................... 18
Flex parameter types .......................................................................................................................................... 19
Transaction hierarchy ......................................................................................................................................... 19
About creating transaction definitions ............................................................................................................... 22
Identifying transactions based on the response ................................................................................................. 23
Transaction signature promotion process .......................................................................................................... 24
Process for creating transaction definitions .............................................................................................................. 24
Access the CEM Console ............................................................................................................................................ 25
Troubleshooting Login to CA CEM .............................................................................................................................. 26
Chapter 2: Defining business applications and services 27
Business application hierarchy ................................................................................................................................... 27
Defining a business application .................................................................................................................................. 28
Troubleshooting case sensitivity for login names ............................................................................................... 31
About defining business application identifiers ......................................................................................................... 31
Defining session identifiers ........................................................................................................................................ 32
Defining user identifiers ............................................................................................................................................. 34
Using the client IP address to identify users .............................................................................................................. 36
Identify users by client IP address and user group by IP subnet or by user group by IP subnet alone? .................... 38
Defining interim session identifiers ............................................................................................................................ 39
Example interim session identification using Location Query ............................................................................ 40
Defining user group identifiers................................................................................................................................... 41
Offset and Length examples ....................................................................................................................................... 42
Using XML to identify sessions, users, and user groups ............................................................................................. 42
Defining identifiers for NTLM authentication ............................................................................................................ 44
Using path parameters to identify sessions ............................................................................................................... 44
Setting the global delimiter for path parameters ...................................................................................................... 46
Defining business services .......................................................................................................................................... 47
-
8/11/2019 APM_9.5 Transaction Definition Guide
8/211
8 Transaction Definition Guide
Chapter 3: Recording transaction signatures 49
CA CEM recorder types .............................................................................................................................................. 50
Turning off web page caching .................................................................................................................................... 50
Setting up for recording with a proxy server ............................................................................................................. 51Monitoring traffic behind a proxy server ............................................................................................................ 52
Deactivate traffic monitoring on your client computer ...................................................................................... 53
Using the TIM recorder .............................................................................................................................................. 53
About content-types for recording sessions ....................................................................................................... 54
About unrecognized transaction components .................................................................................................... 54
Enabling transaction recording ........................................................................................................................... 55
Starting a Recording ............................................................................................................................................ 55
Stopping a TIM recorder session ......................................................................................................................... 60
Using the script recorder ............................................................................................................................................ 61
Installing the script recorder ............................................................................................................................... 61
Input script file types .......................................................................................................................................... 61
VuGen trace files ................................................................................................................................................. 61
Pcap files ............................................................................................................................................................. 62
Command line instructions ................................................................................................................................. 63
Viewing recording sessions ........................................................................................................................................ 63
Viewing the recording session transactions ........................................................................................................ 64
Viewing the recording session parameter map .................................................................................................. 65
Viewing the recording session transaction components .................................................................................... 67
Editing recording sessions .......................................................................................................................................... 67
Troubleshooting transaction recording ...................................................................................................................... 68
Chapter 4: Introscope agent recording 69
About recording with the Introscope agent ............................................................................................................... 69
About upgrading to CA APM 9.x ................................................................................................................................. 70
Process for recording transactions ............................................................................................................................. 70
Enable agent recording .............................................................................................................................................. 71
Enabling agent recording in the agent profile..................................................................................................... 72
Turning off web page caching ............................................................................................................................. 72
Accessing the CEM console ................................................................................................................................. 73
Setting up a business application ............................................................................................................................... 73
Setting up a business service...................................................................................................................................... 74
Setting up an agent filter ............................................................................................................................................ 75
Recording a business transaction ............................................................................................................................... 76
Known limitations ............................................................................................................................................... 77
Starting an agent recording session ........................................................................................................................... 79
Agent recording and proxy servers ............................................................................................................................ 82
Recording with an agent (no proxy server) ......................................................................................................... 83
-
8/11/2019 APM_9.5 Transaction Definition Guide
9/211
Contents 9
Recording with an agent through a proxy server ................................................................................................ 83
Viewing recording sessions ........................................................................................................................................ 85
Viewing the recording session transactions ........................................................................................................ 85
Viewing the recording session parameter map .................................................................................................. 86
Editing recording sessions .......................................................................................................................................... 87
Promoting transactions to definitions ........................................................................................................................ 88
Chapter 5: Automatically discovering transactions 91
About automatic transaction discovery ..................................................................................................................... 92
Creating a template and parameters ......................................................................................................................... 93
URL Path Filter examples .................................................................................................................................... 95
Any type example................................................................................................................................................ 95
Multiple transactions discovered from one template ........................................................................................ 96
Transaction naming example .............................................................................................................................. 96
Path parameter example .................................................................................................................................... 97
A catchall example .............................................................................................................................................. 97
The order in which templates are created .......................................................................................................... 98
Enabling templates ..................................................................................................................................................... 98
Editing templates ....................................................................................................................................................... 98
Selecting the TIMs for automatic transaction discovery ............................................................................................ 99
Starting automatic transaction discovery ................................................................................................................ 100
Stopping automatic transaction discovery ............................................................................................................... 101
Stopping the Transaction Discovery Collection Service .................................................................................... 101
Stopping automatic transaction discovery, but not stopping the service ........................................................ 101
Viewing discovered transactions .............................................................................................................................. 102
Monitoring discovered transactions ........................................................................................................................ 103
Automatically discovering components ................................................................................................................... 103
Troubleshooting automatic transaction discovery .................................................................................................. 105
Chapter 6: Defining transactions 109
About transaction definitions and identifiers .......................................................................................................... 109
About edits to request and response identifiers...................................................................................................... 110
Promoting transaction signatures to definitions...................................................................................................... 110
Creating Business Transactions ................................................................................................................................ 111
Editing transactions .................................................................................................................................................. 113
Editing transaction components .............................................................................................................................. 116
Wildcarding parameter names ................................................................................................................................. 119
Using XML to identify transactions .......................................................................................................................... 120
Adding and deleting parameters .............................................................................................................................. 122
About defining defects ............................................................................................................................................. 124
Defining business transaction defects...................................................................................................................... 125
-
8/11/2019 APM_9.5 Transaction Definition Guide
10/211
10 Transaction Definition Guide
Locate business transaction defect conditions ................................................................................................. 125
Modify a Defect Type Condition ....................................................................................................................... 125
Lock or Unlock a Defect Type Condition ........................................................................................................... 126
Set the baseline for a defect condition ............................................................................................................. 126
Defining transaction defects .................................................................................................................................... 127
Defining component defects .................................................................................................................................... 128
Viewing access policies for business services .......................................................................................................... 130
Adding access policies for business services ............................................................................................................ 131
Monitoring transactions ........................................................................................................................................... 134
Enabling transaction definitions ....................................................................................................................... 134
Enabling transaction monitoring ....................................................................................................................... 135
Synchronizing to TIMs, agents, WebView, and Workstation ............................................................................ 135
Chapter 7: Managing your transactions 137
About reviewing your transactions .......................................................................................................................... 137
Verifying transactions with CA CEM performance reports ...................................................................................... 138
Troubleshooting tips for transactions ...................................................................................................................... 139
Transactions were being recognized but suddenly stopped ............................................................................. 140
Observe the transactions being monitored by the TIM .................................................................................... 140
Too many missing response defects ................................................................................................................. 142
Problems with transactions that contain path parameters .............................................................................. 143
Troubleshooting response-based transactions ................................................................................................. 143
Troubleshooting Flex transactions .................................................................................................................... 143
Managing transaction settings with CA CEM ........................................................................................................... 144
Modifying business service and transaction settings ........................................................................................ 144
Modifying behavioral defect settings ............................................................................................................... 146
Modifying SLA success settings ......................................................................................................................... 148
Managing transaction settings with bulk editing ..................................................................................................... 148
Modifying business transaction settings ........................................................................................................... 149
Modifying defect conditions ............................................................................................................................. 150
Modifying user settings ..................................................................................................................................... 150
Exporting and importing business transaction definitions....................................................................................... 151
Additional information about exporting and importing business transaction definitions ............................... 152
Moving business transactions between business services ...................................................................................... 152
Managing transaction definitions ............................................................................................................................ 153
Usage example: TIM performance .................................................................................................................... 155Usage example: Troubleshooting...................................................................................................................... 155
Usage example: Transaction statistics .............................................................................................................. 155
Replacing existing business transaction definitions ................................................................................................. 156
-
8/11/2019 APM_9.5 Transaction Definition Guide
11/211
Contents 11
Chapter 8: Identifying transactions using the HTTP analyzer plug-in 157
About the HTTP analyzer plug-in .............................................................................................................................. 158
HTTP analyzer plug-in overview ............................................................................................................................... 158
About using the HTTP analyzer plug-in .................................................................................................................... 160Important cautions when deploying the HTTP analyzer plug-in ....................................................................... 161
Best practices when deploying the HTTP analyzer plug-in ............................................................................... 161
Deploying multiple HTTP analyzer plug-ins ....................................................................................................... 162
Handling XML data using the HTTP analyzer plug-in......................................................................................... 162
Process for deploying the HTTP analyzer plug-in ..................................................................................................... 163
Downloading the HTTP analyzer plug-in SDK ........................................................................................................... 164
Using the SDK to create an HTTP analyzer plug-in ................................................................................................... 165
Configuring an HTTP analyzer plug-in ...................................................................................................................... 166
Modifying an HTTP analyzer plug-in ......................................................................................................................... 168
Enabling an HTTP analyzer plug-in ........................................................................................................................... 170
Enabling and disabling TIM monitors ....................................................................................................................... 170
Testing an HTTP analyzer plug-in ............................................................................................................................. 170
Verifying an HTTP analyzer plug-in in the CEM console ........................................................................................... 173
Verifying an HTTP analyzer plug-in on the TIM ........................................................................................................ 174
Disabling an HTTP analyzer plug-in .......................................................................................................................... 177
Troubleshooting the HTTP analyzer plug-in SDK ...................................................................................................... 177
Events and logs ................................................................................................................................................. 177
TIM status ......................................................................................................................................................... 179
Transaction identification ................................................................................................................................. 181
User interface .................................................................................................................................................... 182
Code and compiler ............................................................................................................................................ 182
Chapter 9: Monitoring multibyte transactions 185
Process for using multibyte with CA CEM ................................................................................................................ 185
About using multibyte character sets with CA CEM ................................................................................................. 186
Before using multibyte with CA CEM ....................................................................................................................... 187
Configuring applications for multibyte characters ................................................................................................... 187
Recording multibyte transactions ............................................................................................................................ 189
Promoting multibyte transactions ........................................................................................................................... 190
Moving multibyte business transactions.................................................................................................................. 191
Special considerations for multibyte transaction monitoring .................................................................................. 192
CA CEM limitations for multibyte support ........................................................................................................ 192
Using export with multibyte business transactions .......................................................................................... 192
Using Save to CSV with multibyte business transactions .................................................................................. 193
Using regular expressions with multibyte transactions .................................................................................... 193
Using offsets with multibyte business transactions .......................................................................................... 193
Using automatic transaction discovery with multibyte applications ................................................................ 193
-
8/11/2019 APM_9.5 Transaction Definition Guide
12/211
12 Transaction Definition Guide
Using the HTTP analyzer plug-in with multibyte applications........................................................................... 194
Troubleshooting multibyte with CA CEM ................................................................................................................. 194
Appendix A: HTTP status codes 197100 series: informational status codes .................................................................................................................... 197
200 series: success status codes .............................................................................................................................. 197
300 series: redirection status codes ......................................................................................................................... 198
400 series: client error status codes ........................................................................................................................ 198
500 series: server error status codes ....................................................................................................................... 199
Appendix B: Regular expressions in CA CEM 201
BizTrxHttpTracer ...................................................................................................................................................... 201
CEMTracer ................................................................................................................................................................ 201
CA CEM TIM .............................................................................................................................................................. 202CA CEM ..................................................................................................................................................................... 202
CA CEM NSM bridge ................................................................................................................................................. 202
Regular expressions resources ................................................................................................................................. 202
Jakarta-ORO ...................................................................................................................................................... 203
PCRE Perl-compatible regular expressions ................................................................................................... 203
Java .................................................................................................................................................................... 203
Appendix C: Transaction Definition Troubleshooting 205
Index 207
-
8/11/2019 APM_9.5 Transaction Definition Guide
13/211
Chapter 1: Introducing the transaction definition process 13
Chapter 1: Introducing the transactiondefinition process
CA CEM provides real-time visibility into your users (internal and external) transactions,
and monitors your users transactions to isolate the causes of problems in the data
center. CA CEM measures the performance and quality of transactions, identifies
defects and variance, and quantifies the impact on users and the business. By
proactively detecting trends in degraded transaction response times and providing
various actionable reports, CA CEM enables you to act before a problem occurs or
Service Level Agreements (SLAs) are out of compliance.
This chapter provides an overview of how IT organizations can use CA CEM to define
user transactions in IT production environments.
This section contains the following topics:
About this Guide(see page 13)
About transaction identification(see page 14)
Process for creating transaction definitions(see page 24)
Access the CEM Console(see page 25)
Troubleshooting Login to CA CEM(see page 26)
About this Guide
This guide is intended for the person who is responsible for creating transactiondefinitions.
The final chapter is an exception: the audience for Identifying transactions using the
HTTP analyzer plug-in is primarily Java developers who are designing and testing their
own Java code for the HTTP analyzer plug-in.
The purpose of this guide is to help administrators establish and maintain business
applications, business services, and transaction definitions.
This guide assumes that:
CA APM has been installed according to the information in the CA APM Installation
and Upgrade Guide.
You have a basic understanding of CA APM and CA CEM as described in the CA APM
Overview Guide.
-
8/11/2019 APM_9.5 Transaction Definition Guide
14/211
About transaction identification
14 Transaction Definition Guide
What you need to know
To use this guide, you need a working knowledge of CA CEM administration and the user
transactions that you record, define, verify, and maintain for CA CEM.
We assume that you already have a working understanding of HTTP and Flex
transactions.
For information about configuring and administering CA CEM, see theCA APM
Configuration and Administration Guide.
About transaction identification
Transaction identification is the process of defining unique transactions that can be
distinguished from other transactions.
The transaction definition process provides a way to refine unique transaction
signatures. For example, a user logs on to your site and submits a form to the HR
department. Correctly specified transaction definitions enable CA APM to identify the
user login transaction and the HR form submission transaction as two distinct
transactions.
HTTP request parameter types
CA CEM identifies transactions based on HTTP name/value pairs observed in traffic
between the client browser and the web server. These HTTP name/value pairs are
named HTTP parameters. HTTP parameters consist of a type, a name, and a value. Theseparameters appear in the header and body of an HTTP request.
An HTTP Request contains a method, a URL, request headers, and optionally a request
body.
To identify a transaction based on the HTTP request parameters, you can specify any of
the following:
HTTP parameters in the HTTP Request
Flex properties in the HTTP Request body
-
8/11/2019 APM_9.5 Transaction Definition Guide
15/211
About transaction identification
Chapter 1: Introducing the transaction definition process 15
For example, following are some of the common HTTP parameters to identify
transactions based on the request:
Cookie
Cookie parameters are name/value pairs that appear in the Cookie: request-header.
Post
Post parameters are name/value pairs that appear in the HTTP Post request-body
when a POST method is used.
Query
Query parameters are name/value pairs that appear in the URL after the first ?
character.
URL
URL parameters are the host name, path, and port number values that appear in
the URL before the first ? character.
HTTP Request
HTTP Request parameters can be used to match fields in the HTTP header that the
client sends to the server.
HTTP Request Header
HTTP Header parameters are name/value pairs that appear in the HTTP Header.
Following is a simple example of an HTTP Request header, and the corresponding
parameters you would use to identify the transaction.
Example HTTP request:
POST /dir/file.html?P1=V1&P2=V2 HTTP/1.1
Host: www.company.com
Cookie: P3=V3; P4=V4
Content-Type: application/www-form-urlencoded
P5=V5&P6=V6
Accept-Language: en-us
Corresponding HTTP parameters:
URL Host=www.company.com
URL Path=/dir/file.html
Query P1=V1
Query P2=V2
Cookie P3=V3Cookie P4=V4
POST P5=V5
POST P6=V6
name=Accept-Language value=en-us
-
8/11/2019 APM_9.5 Transaction Definition Guide
16/211
About transaction identification
16 Transaction Definition Guide
Note:CA CEM can also identify transactions that are not based directly on HTTP. For
example, CA CEM can identify transactions based on XML strings and on values returned
by a custom-coded plug-in (the HTTP analyzer plug-in).
Response-based transactions
You can now record, define, and monitor transactions and also capture response
parameters in addition to the request.
For example, some web applications display different page elements according to the
end user's access authorization or what tasks the user has already performed. In this
case, a single request can generate multiple responses.
You can identify response-based transactions according to any of the following:
HTTP Response header
HTTP Response status
HTML response tag in the HTTP response body
Adobe Flex request and response parameters
If you use the HTTP Analyzer plug-in, be aware that now CA CEM passes both request
and response data to the plug-in. Previously, CA CEM passed only the request data. If
you do not want the plug-in to process the extra overhead, use version 1 of the plug-in
API.
More information
HTTP and HTML Response parameter types(see page 17)Best practices when deploying the HTTP analyzer plug-in(see page 161)
Troubleshooting response-based transactions(see page 143)
About content-types for recording sessions(see page 54)
Flex parameter types(see page 19)
-
8/11/2019 APM_9.5 Transaction Definition Guide
17/211
About transaction identification
Chapter 1: Introducing the transaction definition process 17
HTTP and HTML Response parameter types
An HTTP Response contains a status code, response headers, and typically a response
body. The only way to create a response-based transaction definition is to do so from a
request-based transaction.
To identify transactions based on the response, you can specify any of the following:
HTTP response status code
HTTP parameters that appear in the HTTP Response
HTML tags that appear in the HTTP Response body.
Flex response properties that appear in the HTTP Response body.
HTTP Response
The first line of an HTTP response contains the HTTP Response status code (in
addition to the HTTP version and HTTP Response status description).HTTP Response Header
The HTTP Response header information can include information such as server
version, date last modified, content type, or data your applications need.
HTML Response Tag
You can also identify transactions based on a unique value for an HTML tag in the
response body. For example, you can identify transactions that have a specific value
for the tag. Although technically you can specify any HTML tag, be sure to
use a tag that uniquely identifies the transaction.
Following are examples of how to use each of these parameter types.
Example HTTP Response status lines:
HTTP/1.1 - 404 Not Found
HTTP/1.1 - 200 OK
Example HTTP response parameters:
Status Matches "200"
Status Matches "4*"
Example HTTP Response Header:
HTTP/1.1 200 OK
Date: Tue, 12 Apr 2011 23:09:08 GMT
Server: Apache/2.2.16Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Type: text/html
Content-Length: 159796
Proxy-Connection: Keep-Alive
Connection: Keep-Alive
-
8/11/2019 APM_9.5 Transaction Definition Guide
18/211
About transaction identification
18 Transaction Definition Guide
Corresponding HTTP Response parameters:
Status Matches "200"
Server Matches "Apache*"
Content-Type matches "text/*"
Additional notes about HTML tags
Following are some additional things to know about using HTML tags to define
transactions in CA CEM:
Do not use < or > when defining an HTML tag parameter.
TIM searches transactions for response tag based on the MaxResponseBodySize
setting on the TIM. The default is 2000 and the maximum is 10000.
If an HTML tag in a transaction is either not well formed or the end tag is
undetermined, TIM matches 200 characters from the start of the tag.
Empty tags can be matched for non-existence so that you can make sure
transactions do not have empty HTML tags.
If there are multiple instances of the same HTML tag in an HTML response body,
TIM matches on the first instance in the transaction.
To specify HTML comment tags, specify !-- in the transaction definition. HTML
comment tags begin with .
Monitoring Flex applications
You can now record, identify, and monitor transactions in Adobe Flex applications that
use AMF 3. These applications communicate between the web browser Adobe Flash
plug-in and the web server.
-
8/11/2019 APM_9.5 Transaction Definition Guide
19/211
About transaction identification
Chapter 1: Introducing the transaction definition process 19
Flex parameter types
If your web applications use Adobe Flex objects or Adobe Flash, you can monitor
parameters that are unique to these types of applications. Adobe Flash or Flex
applications use binary or XML objects to pass data between the client and server. CACEM can parse the data in the Flex-specific properties that accompany the Flex
application data.
You can specify Flex properties to identify transactions based on the request or
response. Flex information is in the body of the HTTP request or response.
You can specify any of the following to identify transactions:
Flex HTTP Request Header to identify transactions based on the request
Flex Request Properties to identify transactions based on the request
Flex Response Properties to identify transactions based on the response
Flex HTTP Request Headers
The Flex HTTP Request Header is the header information for the Flex data and
appears in the HTTP body. Flex HTTP Request Headers are similar to HTTP Headers,
but are within the Flex data.
Flex Request Properties
messagetype, destination, source, operation, contenttype, method, url
Flex Response Properties
messageType, destination
Transaction hierarchy
Each CA CEM system has one domain, and business services and transactions are
associated with that domain. (Business applications are associated with business
services.)
Business Service group of business transactions within CA CEM.
Business Transaction set of transactions
Transaction set of transaction components
Transaction component URL retrieval
- Transaction parameter a name/value pair
Note:In Introscope, transactions are sometimes called Business Transaction
Components. For example, in the application triage map display in Workstation,
transactions are displayed as Business Transaction Components.
-
8/11/2019 APM_9.5 Transaction Definition Guide
20/211
About transaction identification
20 Transaction Definition Guide
Hierarchy example:
Local Domain Domain
Siebel Call Center Business Service:
ExecuteLogin Business Transaction
Execute Login (SWE) Transaction
rtcEditor.js Transaction Component
jctrls.css Transaction Component
wait.html Transaction
GCF_swe Transaction
GCF_sweapp Transaction
GCF_swecdawksp Transaction
GCF_sweattachment Transaction
GotoPostedAction Transaction
-
8/11/2019 APM_9.5 Transaction Definition Guide
21/211
About transaction identification
Chapter 1: Introducing the transaction definition process 21
Avitek Financial Business Service:
Buy Business Transaction
Buy Transaction (identifying)
Submit Buy Transaction Component (identifying)
main.css Transaction Component
portal_header.gif Transaction Component
customize.gif Transaction Component
setpassword.gif Transaction Component
logout.gif Transaction Component
transparent.gif Transaction Component
v_home.gif Transaction Component
web.gif Transaction Component
quote.gif Transaction Component
portlet_unedit.gif Transaction Component
up.gif Transaction Component
down.gif Transaction Component
buy.gif Transaction Component
sell.gif Transaction Component
portal_footer.gif Transaction Component
Other non-identifying transactions Transaction
-
8/11/2019 APM_9.5 Transaction Definition Guide
22/211
About transaction identification
22 Transaction Definition Guide
Corresponding response-based transaction:
Buy_Response Business Transaction
Buy_Response Transaction (Identifying)
Buy_Response Transaction Component (Identifying)
main.css Transaction Component
portal_header.gif Transaction Component
customize.gif Transaction Component
setpassword.gif Transaction Component
logout.gif Transaction Component
transparent.gif Transaction Component
v_home.gif Transaction Component
web.gif Transaction Component
quote.gif Transaction Component
portlet_unedit.gif Transaction Component
up.gif Transaction Component
down.gif Transaction Component
buy.gif Transaction Component
sell.gif Transaction Component
portal_footer.gif Transaction Component
About creating transaction definitions
You identify transactions based on the request transaction, or based on the request and
the associated response. The CA CEM recorders analyze the transaction and extracts
HTTP/HTTPS identification parameters from the request and response headers and
content.
When you have uniquely identified a transaction, you can create transaction definitions
to analyze your traffic. You can create a transaction definition by:
Using the agent recorder to record transaction signatures, identifying transaction
information only, as monitored by the agents you specify.
Using CA APM TG scripts, which are built in CA APM TG, to generate CA CEM
business transaction definitions.
-
8/11/2019 APM_9.5 Transaction Definition Guide
23/211
About transaction identification
Chapter 1: Introducing the transaction definition process 23
Using automatic transaction discovery to have CA CEM discover transactions for
you, based on bounding parameters that you configure.
Using the TIM recorder to record transaction signatures, and then promoting
transaction signatures to transaction definitions.
Using the script recorder, importing transaction definitions from other products.
Using business transaction export and import to copy a business transaction
definition from one CA CEM system to another.
Creating your own transaction definition manually, without recording.
Creating a response-based business transaction based on a request transaction.
For more information about CA APM TG scripts, see the CA APM Transaction Generator
Implementation Guide.
Identifying transactions based on the response
When identifying transactions to monitor, you first identify the request transaction.
Then you select the request transaction definition and create a response transaction
that extends from that request.
Often people customize applications so that the response page is slightly different,
depending on the requesting user. Following are some examples of cases when
response-based transaction identification is useful:
Some users qualify for a special promotion. Response pages for this subset of users
include an additional section of promotional content. In this case, you have multiple
response transactions based on a single request transaction.
Some users have restricted access and some content does not display for these
users. For example, the response page for these users does not display an
additional page frame.
Based on the user and the session, the application displays different content. For
example, different users of a portal may have configured it to display different
widgets.
Identify transactions based on the response status codes so that defects are
generated when the HTTP defect status codes occur (these defect codes are the 4xx
and 5xx HTTP status codes).
Note: You do not record or discover response-based transactions directly. You need to
discover or record a request-based transaction and then extend the request-based
transaction to create a response-based transaction.
-
8/11/2019 APM_9.5 Transaction Definition Guide
24/211
Process for creating transaction definitions
24 Transaction Definition Guide
Transaction signature promotion process
Transaction definitions can be created easily from user activity that CA CEM observes.
Recordings of user activity can be used as a means to discover generalized transaction
signatures.
After you have collected transaction signatures through a CA CEM recording session,
you can promote the signatures to transaction definitions, which you can use in your
transaction analysis. For example, when a user submits an HR form, the transaction
recorded by CA CEM is saved as a transaction signature.
Signature promotion makes creating transaction definitions easy.
After you promote the signatures to definitions, you can edit the definition components
to specify further which types of transactions to capture. For example, you can
generalize from the transaction signature so that transactions of all users submitting HR
forms are captured rather than just the one from the transaction recording.
Process for creating transaction definitions
Following is an overview of the tasks you perform when creating transaction definitions.
Follow these steps:
1. Define the domain. See the CA APM Configuration and Administration Guide.
2.
Define a business application and user identifiers within the business application.
(see page 28)
3.
Define a business service associated with the business application.(see page 47)
4.
Create transaction definitions. Useautomatic transaction discovery(see page 91) to
find transactions performed by your web application users and then create
transaction definitions based on these actual transactions.
Alternatives for step 4:
You can perform step 4 in a less automated way:
Record transactions(see page 49) from a particular browser.
Take a transaction signature you recorded andpromote it as a transaction
definition(see page 110) in the business service you created.
Edit the specific transaction definition(see page 113) to a generalizedtransaction definition using pattern matching, defect specifications, and
component specifications.
If you have Introscope without CA APM, then you can only doagent recording
(see page 69).
-
8/11/2019 APM_9.5 Transaction Definition Guide
25/211
Access the CEM Console
Chapter 1: Introducing the transaction definition process 25
5. If desired,create(see page 111) a response-based transaction definition that
extends from a request-based transaction definition.
6. Specify what transactions are considered defective at each level.(see page 124)
Business transaction defects
Transaction defects
Component defects
7.
Enable the transaction definition for monitoring.(see page 134)
8. Verify that the transactions are being monitored correctly.(see page 137)
Access the CEM Console
You can set up and administer business applications, business services, and transaction
definitions from any computer that has a web browser.
The CEM console is the main user interface of CA CEM. Administrators use it to set up
and configure CA CEM, including transaction recording and creating transaction
definitions. Analysts use it to produce and view reports.
If you are an administrator, the CEM console will have additional menu options.
Additionally, if no TIMs are enabled, certain CA CEM links do not appear.
(If no TIMs are enabled, the Tools and CA CEM links do not appear.)
Unless otherwise indicated, this guide assumes that you are using the CEM console as
an administrator.
-
8/11/2019 APM_9.5 Transaction Definition Guide
26/211
Troubleshooting Login to CA CEM
26 Transaction Definition Guide
In a clustered environment, the CEM console is on the Manager of Managers (MOM).
Follow these steps:
1.
Open a web browser and type the address:
http://:8081/wily
where is the IP address or DNS name for the MOM or a standalone
Enterprise Manager. For example:
http://192.168.1.54:8081/wily
http://cem.company.com:8081/wily
To use a DNS name, your DNS administrator must have configured it.
Note:The default port is 8081. It is defined in the
IntroscopeEnterpriseManager.properties file as
introscope.enterprisemanager.webserver.port=8081
and can be changed.
2.
Enter the user name and password.The default user name for the CA CEM administrator is cemadmin.
The CEM console appears.
For information about security and logins, see the CA APM Security Guide.
Troubleshooting Login to CA CEM
Symptom:
If you are unable to log in to CA CEM, verify that Active Scripting is enabled on your
browser.
If Active Scripting is disabled, when you click Log In on the CA CEM login page, you are
redirected to a CEM Console / Back page. This happens even when your User Name and
Password have been entered correctly.
Solution:
To enable Active Scripting, see the user documentation for your browser. For example,
in Internet Explorer 8, the setting is under Internet Options > Security > Custom level >
Scripting > Active scripting.
-
8/11/2019 APM_9.5 Transaction Definition Guide
27/211
Chapter 2: Defining business applications and services 27
Chapter 2: Defining business applicationsand services
Business applications are used to store application-specific information such as session
identification and user identification. Business services include transaction definitions.
Before you define transactions, you must first create a business application and a
business service associated with the business application to store the transactions.
This process describes the order in which you should define the CA CEM domain,
business applications, and business services.
Follow these steps:
1.
Define the CA CEM domain. This is usually done as a part of CA CEM setup. (See theCA APM Configuration and Administration Guide.)
2. Define a business application(see page 28).
3. Defineuser(see page 34),session(see page 32), andinterim session(see page 39)
identifiers for the business application;identify user groups(see page 41).
4. Define the business service associated with the business application(see page 47).
Business application hierarchy
Each organization has one domain, and business services and business applications are
associated with it.
Business application is an attribute of a business service. Each business service is
associated with one business application. The business application might be a
financial or product ordering application (for example, Siebel).
Business Service consists of groups of business transactions.
-
8/11/2019 APM_9.5 Transaction Definition Guide
28/211
Defining a business application
28 Transaction Definition Guide
About the default application
CA CEM comes with a default business application. You cannot delete or rename the
default application. When you select Ignore Applications in User Recognition (Setup >
Domain), then the case sensitivity for login names is determined by the DefaultApplication and the value set for this check box in other business applications is ignored.
Note:If you renamed the default application in a previous version of CA CEM and want
to change it back to "Default Application," contact CA Support.
Defining a business application
To gain the highest value from CA CEM, describe fundamental characteristics of the
application. These parameters affect the way CA CEM identifies users and monitors
business application statistics.
Follow these steps:
1.
Select Administration, Business Applications.
2. Click New to create a business application.
3. Complete the required information and click Save.
Name
Give a meaningful name to the business application. The business application name
is not case-sensitive.
Description
Add a comment about the business application.
-
8/11/2019 APM_9.5 Transaction Definition Guide
29/211
Defining a business application
Chapter 2: Defining business applications and services 29
Type
Select Generic or Siebel.
Authentication Type
Select the appropriate type for your business application.
Application Specific
If your business application provides its own authentication mechanism (For
example, through a cookie, post, query, or URL parameter).
Basic Authentication
If your organization or your business application does not provide authentication,
then CA CEM uses a standard HTTP protocol for prompting the user for a user name
and password.
SiteMinder
Select SiteMinder if your organization is using CA SiteMinder to manage sessions.
NTLM Authentication
Select if your organization is using the Windows NT LAN Manager
challenge-response mechanism for authentication. (SeeDefining identifiers for
NTLM authentication(see page 44) for more information.)
Case-Sensitive URL Path
Select this check box if you want the URL to be treated as case-sensitive. For web
servers running on Windows, clear this check box. For web servers running on other
operating systems, select this check box.
Case-Sensitive Login Names
Select this check box if you want User Names to be treated as case-sensitive. For
web servers running on Windows, clear this check box. For web servers running on
other operating systems, select this check box.
Note:If you select case-sensitive login names, you cannot change later to case
insensitive login names if it will result in a user name conflict. For example, if the
business application has users named CA_user and ca_User and you clear the Case
Sensitive Login Names check box, an internal application error "duplicate key
violates unique constraint" appears. For information about deleting users, see the
CA APM Configuration and Administration Guide.
Note:If you selected Ignore Applications in User Recognition when you set up your
domain (Setup > Domain), then case sensitivity is determined by the default
applications Case Sensitive Login Names option.
-
8/11/2019 APM_9.5 Transaction Definition Guide
30/211
Defining a business application
30 Transaction Definition Guide
Session Timeout
Enter the business applications timeout length. Once the timeout has been
reached, CA CEM discards the session ID information. If this value is not set
correctly, per-user defects and statistics might not be accurate.
If the session timeout is shorter than the business application's session timeout, the
defects and statistics will be associated with the unspecified user.
If the session timeout is longer than the business applications session timeout, the
defects and statistics for multiple users might be attributed to one user. (Session
IDs can be reused.)
User Processing Type
E-Commerce or Enterprise:
For e-Commerce business applications, detailed per-transaction type statistics are
stored per hour and per transaction definition. This setting provides maximum
scalability for high volume e-Commerce business applications. Significant savings in
the disk storage usage are possible with this setting.
For enterprise business applications, detailed per-user statistics are stored per
hour, per transaction definition, and per user. Because the setting provides the
most detailed statistics about individual users, there is a significant increase in the
disk storage usage for business applications with high user counts. Select Enterprise
only if you have a compelling need for per-user statistics.
Character Encoding
Select the appropriate character encoding for your business application:
ISO-8859-1
The default character encoding for CA CEM; the HTTP and MIME text
default.
UTF-8
The standard for encoding Unicode on UNIX / Linux; the preferred
standard for multilingual web sites.
EUC-JP
Japanese character encoding for UNIX / Linux.
Shift-JIS
Japanese character encoding for Microsoft Windows.
ISO-2022-JPDouble-byte coded Kanji (Chinese characters used in Japanese writing).
Windows-31J
Microsoft Windows extension to Shift-JIS to accommodate NEC special
characters and IBM extensions.
-
8/11/2019 APM_9.5 Transaction Definition Guide
31/211
About defining business application identifiers
Chapter 2: Defining business applications and services 31
GB2312
Character encoding for Chinese, simplified.
Big5
Character encoding for Chinese, traditional.
EUC-KR
Character encoding for Korean.
SeeMonitoring multibyte transactions(see page 185) for more information.
Now you are ready to create business application identifiers.
Troubleshooting case sensitivity for login names
Symptom:
The case sensitivity setting for recognizing login names does not work for the business
application.
For example, users are not appearing in their assigned groups. Or, case sensitivity is
being ignored when users are assigned to groups.
Solution:
Ensure one of the following:
That Ignore Applications in User Recognition (Setup > Domain) is not selected and that
Case Sensitive Login Names (Administration > Business Applications > business
application) is set correctly for the behavior you want.
Or
If Ignore Applications in User Recognition (Setup > Domain) is selected, then Case
Sensitive Login Names (Administration > Business Applications > Default Application) is
set correctly for the behavior you want for all your business applications.
For more information, seeAbout the default application(see page 27).
About defining business application identifiers
Web applications have various ways of differentiating one interactive user session from
another. For example, session ID is often used to keep track of a specific userperforming one transaction, or set of transactionsfrom start to finish.
You need to define business application identifiers so CA CEM can determine which
particular user is executing a particular transaction. These identifiers are defined at the
business application level, which means that multiple business services can use the
same identifiers.
-
8/11/2019 APM_9.5 Transaction Definition Guide
32/211
Defining session identifiers
32 Transaction Definition Guide
You might also want to define business application identifiers to track users within
groups, based on the content of their transactions.
You can identify sessions, users, and user groups for a business application via:
Session identification defines the session identifiers used to define where a
session starts and stops.
User identification if you do not specify user identifiers, transactions are assigned
to the generic unspecified user. You must specify user identifiers to bind the user
identity (for example, login ID) to a particular session (for example, session ID).
Interim session identification in some cases, such as a two-phase login
authentication process, the user identification and session identification cannot be
found in the same HTTP component. Interim session identification parameters can
be defined to link the two HTTP components.
User group identification identifies and groups users (and their associated
statistics) by the content within the request they are making.
Defining session identifiers
Web applications usually include a session ID for differentiating between interactive
user sessions. You configure CA CEM to specify which transaction parameter contains
the application session ID. CA CEM uses session identifiers for these functions:
Binding, or associating, transaction components into transactions
Binding transactions into business transactions
Identifying the user that executes a transaction or a business transaction
Session identifiers are defined at the business application level, which means that
multiple business services can use the same session identifiers.
The TIM recorder simplifies the definition process by automatically extracting
transaction signatures from live transactions passing through your network. You can
analyze these signatures to determine the transaction parameter that contains the
application session ID.
If you do not yet know the session identifier, you can come back to this step after you
define the transaction.
-
8/11/2019 APM_9.5 Transaction Definition Guide
33/211
Defining session identifiers
Chapter 2: Defining business applications and services 33
For information about determining transaction identification parameters, seeViewing
the recording session parameter map(see page 65).
To specify a business application session identifier:
1.
Select Administration > Business Applications. Select the name of your business
application (for example, Siebel Call Center).
2. Select Session Identification. Click New Parameter Group.
The Session Identification Parameter page appears.
3. Define the session identifier by choosing a parameter Type.
4. Enter a parameter Name that contains the session ID.
5. To specify a wildcard in the parameter Name, seeWildcarding parameter names
(see page 119).
6. To specify a substring within a parameter, click the Advanced button.
Offset is the number of characters to skip before examining the substring. Usea value of 0 to specify the entire string.
Length is the number of characters to include in the identifier. Use the value of
-1 to specify the entire string.
SeeOffset and Length examples(see page 42).
7. Click Save to save the session identification parameter. To define more parameters,
see the procedure below.
To specify additional session identification parameters:
1. Verify that you have created at least one session identification parameter (as
described in the procedure above).2. Decide if you want the new parameter to be ANDed or ORed with the existing
parameters.
ANDed means that all identifiers must be present to identify the session.
ORed means that if any of the identifiers in the parameter group are present,
the session is identified.
-
8/11/2019 APM_9.5 Transaction Definition Guide
34/211
Defining user identifiers
34 Transaction Definition Guide
3. To create an ANDed parameter, click New and complete the fields.
4. To create an ORed parameter, click New Parameter Group and complete the fields.
Example session identifiers
Application Parameter Type Parameter Name
Siebel Cookie _sn
J2EE Cookie JSESSIONID
Avitek Financial (WebLogic
application)
Cookie JSESSIONID_
SAMPLEPORTAL
various Cookie ASPSESSIONID*
CA SiteMinder see note SiteMinder SessionId
Note:Consult the CA SiteMinder documentation before enabling the CA SiteMinder
plug-in. SessionId is accessible through a SiteMinder cookie, usually named SMSESSION.
To enable CA SiteMinder or to change the cookie name, go to Setup > Plug-ins and
select CA SiteMinder. See the CA APM Configuration and Administration Guidefor more
information.
Defining user identifiers
A combination of user identification parameters and session identification parameters
enables CA CEM to assign the correct user for each monitored transaction. Verify that
the session identifiers are clearly defined before specifying the user identifiers.
User identifiers are defined at the business application level, which means that multiple
business services can use the same user identifiers.
CA CEM identifies users of login transactions by their login name. Users of other
transactions are identified by session ID and the login name of the login transaction for
that session.
Important:If you do not specify user identifiers, transactions are assigned to the
unspecified user and you do not collect statistics on a per-user basis.
If you do not yet know the user identifier, you can come back to this step after you
define the transaction.
-
8/11/2019 APM_9.5 Transaction Definition Guide
35/211
Defining user identifiers
Chapter 2: Defining business applications and services 35
For information about determining transaction identification parameters, seeViewing
the recording session parameter map(see page 65).
Note:After you define the User Identification parameter, for defects to be associated to
a user (instead of an unspecified user), do the following:
Define the Session Identification parameter.
Define a Login business transaction definition that contains the parameter defined
in User Identification parameter.
When users start their sessions by logging in, the login transaction picks up the user
name. Thereafter, any other transactions during the same session and the defects
they may produce can be linked by the Session Identification parameter to the user
name.
To specify a business application user identifier:
1. Select Administration > Business Applications. Select the name of your business
application (for example, Siebel Call Center).
2.
Select User Identification. Click New Parameter Group.
The User Identification Parameter page appears.
3. Define the user identifier by choosing a parameter Type and entering the
parameter Name that contains the User Name. (Multiple parameters are allowed.)
4. If you want to examine a specific substring within a parameter, click the Advanced
button.
Offset is the number of characters to skip before examining the substring. Use
a value of 0 to specify the entire string.
Length is the number of characters to include in the user identifier. Use thevalue of -1 to specify the entire string.
SeeOffset and Length examples(see page 42).
5. Click Save to save the user identification parameter. To define more parameters,
see the procedure below.
To specify additional user identification parameters:
1.
Verify that you have created at least one user identification parameter (as
described in the procedure above).
2.
Decide if you want the new parameter to be ANDed or ORed with the existing
parameters.
ANDed means that all identifiers must be present to identify the user.
ORed means that if any of the identifiers in the parameter group are present,
the user is identified.
-
8/11/2019 APM_9.5 Transaction Definition Guide
36/211
Using the client IP address to identify users
36 Transaction Definition Guide
3. To create an ANDed parameter, click New and complete the fields.
4. To create an ORed parameter, click New Parameter Group and complete the fields.
Example user identification parameters
Application Parameter Type Parameter Name
Siebel Post SWEUserName
J2EE Post j_username
Avitek Financial
(WebLogic application)
Post j_username
CA SiteMinder see
note
SiteMinder UserName
DistinguishedName
Note:Consult the CA SiteMinder documentation before enabling the CA SiteMinder
plug-in. To enable CA SiteMinder, go to Setup > Plug-ins and select CA SiteMinder. See
the CA APM Configuration and Administration Guidefor more information.
Using the client IP address to identify users
Typically users are identified by login name, obtained by setting a user identification
parameter as described above inDefining user identifiers(see page 34).
However, the client IP address can be used instead ofa login name.
-
8/11/2019 APM_9.5 Transaction Definition Guide
37/211
Using the client IP address to identify users
Chapter 2: Defining business applications and services 37
If you choose to do this, the client IP address appears in the User and Login Name fields
throughout the business application; for example, in the User Groups > User Search
page and the Incident Management > Defect details page, as shown.
Using the client IP address to identify users is a good choice when:
You need to triage transaction performance based on network segments.
The identity of individual users is not important (although the users experience
from that client machine is important).
For example, the web application being monitored is a kiosk application. In most cases,
users do not log in. They perform some transactions but do not need to identify
themselves. If an incident occurs, you want to be able to identify the kiosk, not the user
who experienced the defect.
Using the client IP address to identify users lets you set correlational SLAs based on the
kiosk's IP address. For example, a 1-second transaction in the head-office lobby could be
flagged as unacceptable, but an 8-second transaction time in a kiosk at a shopping mall
on a different continent could be acceptable.
Important: If users are behind a proxy server, they are identified and grouped according
to IP address of their proxy servers and not of their client machines. If the request trafficincludes an HTTP header that contains the client IP address, you can configure CA CEM
so that the client IP address is reported. See the CA APM Configuration and
Administration Guidefor how to identify users behind proxy servers.
-
8/11/2019 APM_9.5 Transaction Definition Guide
38/211
Identify users by client IP address and user group by IP subnet or by user group by IP subnet alone?
38 Transaction Definition Guide
To identify and display client IP address as the login name:
Important:Do not use this procedure for e-commerce or very large enterprise sites. The
number of users and user groups created can become unmanageable.
1.
Follow the procedure described inDefining user identifiers(see page 34). When you
set the parameter, select Type URL and Name Client IP.
2.
When you set up user groups for this business application, make sure that you
create the groups based on IP subnet (Setup > Domain). See the CA APMConfiguration and Administration Guidefor information on automatically assigning
new users to subnet user groups.
Important:Do not set user group identification parameters because doing this can
cause the same user to appear in different groups.
Identify users by client IP address and user group by IP subnetor by user group by IP subnet alone?
Even if you choose to create user groups based on IP subnet, there is a significant
difference between identifying users by user attributes or by client IP address.
If you identify users by parameters such as userid, the first time that users log in, they
are assigned to the group based on the IP subnet at that first log in. If users
subsequently log in from a different subnet, they are still associated with the user group
for the original subnet. If your users always log in from the same subnet, this is not an
issue. However, if your users are mobile, then their user groups do not reflect the
subnets that they actually log in from.
If you choose to identify users by client IP address and to create user groups based on IP
subnet, then data associated with a user group always originates from that IP subnet.
-
8/11/2019 APM_9.5 Transaction Definition Guide
39/211
Defining interim session identifiers
Chapter 2: Defining business applications and services 39
This table gives an example of the difference between identifying by client IP address
and by another user attribute (for example, userid). In both cases, user groups are based
on the IP subnet.
Login details If login name is set by the
userid
If login name is the client IP
address
First login:
userid = DrJones
IP_address =
172.16.1.1
Login Name = DrJones