IBM Tivoli Composite Application Manager for Transactions, Version 7.4.0.0

Filter properties

Every company has their own way of reporting on transactions and applications, so the mapping of filter properties is configurable by using customizable reporting rules.

Available filter properties

The properties available for filtering and reporting can vary, depending on the application issuing the ARM calls (ARM-based monitoring) or the agent type (Web Response Time) monitoring the transactions. Transaction Tracking contains both ARM and non-ARM type transactions. The following categorization of properties reflects this grouping.

Sample values for properties in italic are variable; those values in bold must be entered exactly as shown. Property Names are case-sensitive. For example, do not use QUERYSTRING for QueryString.

Table 1. Web Response Time properties
Property Name Value to enter
ApplicationProtocol protocol and version number

Example: HTTP/1.1 or HTTP/1.0
BrowserDescription description of the browser being used

The Browser Description field is obtained directly from the User-Agent header field in the HTTP request without any additional processing.
DestinationPort server destination port number

This is typically80 for HTTP servers, or 443 for HTTPS servers.
Hostname short form of host name
HTTP.GET:XXX The GET form entry field name you want to use in the filter. Example: To filter on the values in a field named zipcode, enter:HTTP.GET:zipcode.
HTTP.POST:XXX The POST form entry field name you want to use in the filter. Example: To filter on the values in a field named zipcode, enter:HTTP.POST:zipcode.
IP client IP address
IPDestinationAddress server IP address

This is typically the host name of the system where the Web Response Time agent is installed.
IPSourceAddress client IP address
IPV6 version 6 IP address
Method
The following string values are available for the HTTP method:
  • GET
  • POST
  • HEAD
  • PUT
  • OPTIONS
  • DELETE
  • TRACE
  • CONNECT
PageTitle title specified in the HTML code for the page
QueryString query string of the URL

The query segment is the portion of the dynamic URI that contains the search parameters of the request, not including the ? character. For example in http://www.ibm.com/support?p1=a &p2=b the query string is p1a&ps=b.
ReferrerURL referrer URL
ServerDescription description of the web server
SourcePort client source port number
Sysplex  
URL URL excluding the query string

The query segment is the portion of the dynamic URI that contains the search parameters of the request, not including the ? character. For example, in http://www.ibm.com/support?p1=a &p2=b , the query string is p1a&ps=b.
URLFile file name portion of the URL

Example: the index.html portion of http://www.ibm.com/hr/index.html
URLHostName host name portion of the URL

Example: http://www.ibm.com/hr/index.html
URLPath path portion of the URL

Example: the /hr/ portion of http://www.ibm.com/hr/index.html
XML.POST:XXX the child text of the specified XML tag XXX
This filter is used to reference data within posted XML content. XXX refers to an XML tag within the data. The value specified for this filter represents either of the following:
  • The child text of this tag
  • The name of the first nested child tag if no child text exists for XXX. In this case, if a namespace is present in XXX (Example: ns:tag), the value returned for the filter includes the namespace of the child tag, if one is present. If no namespace is provided for XXX, then the returned value is stripped of any namespace.

Example: a filter of type XML.POST:name and a value of s* would match an XML-based transaction that contains the tag: sstites.

To use the XML.POST:XXX variable, you must also set the Content-Type of the HTTP message.
Table 2. Generic ARM Applications properties
Property Name Value to enter
AgentType TU (Transaction Tracking). This value is static.
ApplicationGroup Specified by the application making the ARM calls.
ApplicationInstance Specified by the application making the ARM calls.
ApplicationName Specified by the application making the ARM calls.
Hostname short form of host name
IP IP version 4 address
IPV4ClassCSubNet subnet Class C address Example: 9.*
IPV4ClassBSubNet subnet Class B address Example: 9.53.*
IPV4ClassASubNet subnet Class A address Example: 9.53.24.*
ProcessID number corresponding to the process ID of the client application
ThreadID number corresponding to the thread ID of the client application
TransactionName Specified by the application making the ARM calls.
URI Specified by the application making the ARM calls.

ARM-based transactions also have the following properties based upon the application being monitored.

Table 3. ARM Applications: WebSphere Application Server — URI transactions properties
Property Name Value to enter
ApplicationName WebSphere®:<server_type>
for <server_type> use one the following responses:

APPLICATION_SERVER
ONDEMAND_ROUTER
PROXY_SERVER
ApplicationGroup server name
ApplicationInstance node.server name
TransactionName URL
Version WebSphere version Example: 6.1.0.15
Cell Name WebSphere cell name
URI URL without the http:// or the https:// prefix Example: The bold portion is the URI: http://www.ibm.com/myjsp.jsp?id=1&id2=2
Port port number
QueryString query string The query segment is the portion of the dynamic URI that contains the search parameters of the request, not including the ? character. For example in http://www.ibm.com/support?p1=a &p2=b the query string is p1a&ps=b.
Table 4. ARM Applications: WebSphere Application Server — EJB transactions properties
Property Name Value to enter
ApplicationName WebSphere:<server_type>
for <server_type> use one the following responses:

APPLICATION_SERVER
ONDEMAND_ROUTER
PROXY_SERVER
ApplicationGroup server name
ApplicationInstance node.server name
TransactionName EJB
Version WebSphere Version Example: 6.1.0.15
Cell Name WebSphere cell name
EJB name fully qualified EJB class name, followed by method name with a period (.) to connect them. Use the following format:com.mypackge.MyEJBClass.mymethod Example: 
com.ibm.defaultapplication.
IncrementBean.create
Table 5. ARM Applications: WebSphere Application Server — JMS transactions properties
Property Name Value to enter
ApplicationName WebSphere: <server_type>
for <server_type> use one the following responses:

APPLICATION_SERVER
ONDEMAND_ROUTER
PROXY_SERVER
ApplicationGroup server name
ApplicationInstance node.server name
TransactionName JMS
Version WebSphere version Example: 6.1.0.15
Cell Name WebSphere cell name
Bus name service integration bus name for the JMS
Destination Name destination queue name or topic name for the Java™ Message Service (JMS). Example: MyBusiness.Topic.Space
MdbDiscriminator MDB discriminator
MethodSelector method selector for JMS
Topic topic name
Table 6. ARM Applications: WebSphere Application Server — JNDI transactions properties
Property Name Value to enter
ApplicationName WebSphere:<server_type>
for <server_type> use one the following responses:

APPLICATION_SERVER
ONDEMAND_ROUTER
PROXY_SERVER
ApplicationGroup server name
ApplicationInstance node.server name
TransactionName JNDI
Version WebSphere version Example: 6.1.0.15
Cell Name WebSphere cell name
JNDI name JNDI name
Table 7. ARM Applications: WebSphere Application Server — JDBC transactions properties
Property Name Value to enter
ApplicationName WebSphere:<server_type>
for <server_type> use one the following responses:

APPLICATION_SERVER
ONDEMAND_ROUTER
PROXY_SERVER
ApplicationGroup server name
ApplicationInstance node.server name
TransactionName JDBC
Version WebSphere version Example: 6.1.0.15
Table 8. ARM Applications: WebSphere Application Server — JCA transactions properties
Property Name Value to enter
ApplicationName WebSphere:<server_type>
for <server_type> use one the following responses:

APPLICATION_SERVER
ONDEMAND_ROUTER
PROXY_SERVER
ApplicationGroup server name
ApplicationInstance node.server name
TransactionName JCA
Version WebSphere version Example: 6.1.0.15
ClassName class name
MethodName method name
Table 9. ARM Applications: WebSphere Application Server — WebSphere plug-ins (IHS/IIS) transactions properties
Property Name Value to enter
ApplicationName IBM® Webserving Plugin
ApplicationGroup

For Apache and IHS use IBM_HTTP_Server

For IIS use IIS
ApplicationInstance Hostname/PID=<process_name>
TransactionName WebRequest
PluginType Websphere
HostInfo host name
Port port
RemoteAddress IP address of the client
Protocol HTTP/1.0 or HTTP/1.1
Scheme http or https
QueryString URL query string The query segment is the portion of the dynamic URI that contains the search parameters of the request, not including the ? character. For example in http://www.ibm.com/support?p1=a &p2=b the query string is p1a&ps=b.
Table 10. ARM Applications: IBM DB2 Distributed Version transactions properties
Property Name Value to enter
ApplicationName IBM DB2 Universal Database™
ApplicationGroup

DB2®
ApplicationInstance Instance ID identifier
TransactionName SQL
DB2 Platform DB2 platform Example: For Windows, enter QDB2/NT.
Database Alias Database alias
Database Name Database name
Program Name db2jcc_application
Client Protocol 3
Application Hostname host name
Table 11. ARM Applications: Siebel Application Server transactions properties
Property Name Value to enter
ApplicationName Siebel Application Server
TransactionName The value of the SWECmd parameter ($HTTP.POST:SWECmd$ for Post transactions or $HTTP.GET:SWECmd$ for Get transactions).
Table 12. Transaction Tracking Applications (other than ARM): Transactions properties
Property Name Value to enter
ServerName server name
ComponentName component name
ApplicationName application name
TransactionName transaction name
Table 12 applies to the Transaction Tracking default filters for supported data collectors, including
  • ITCAM for Application Diagnostics
  • CICS®
  • CICS Transaction Gateway
  • Other
  • DB2 through CICS or IMS
  • Optim™ (DB2)
  • IMS™
  • IMS Connect
  • .NET
  • Tuxedo
  • WebSphere Message Broker
  • WebSphere MQ
See the Application Management Configuration Editor for details of the filters.
Parent topic: Using filters


Last updated: September 2014