Application Management Configuration Editor terminology
This section defines some of the common terms you encounter when
using the Application Management Configuration Editor:
- Application
- A group of transactions that represents a business application.
A single application might have transactions monitored by different
monitoring agents. For example, both Robotic Response Time and Web Response Time might
monitor the same transaction on the Websphere Application Server to
collect performance data for assessing the health of e-business components
and configurations. Web Response Time monitors
how real users experience the application, while Robotic Response Time helps
you try robotic scenarios that simulate customer transactions. Together,
these agents help you measure how users experience websites and applications
under different conditions and at different times.
The application is the highest level reporting group in the Tivoli Enterprise Portal and the Application Management Console. All transaction data is aggregated into the application. You can create situations to alert you to problems at the application level, and view application trends in the Application Management Console.
- Client
- A flexible grouping of end users that can be defined by an IP address or by a set of host name patterns. You can group clients by location, branch office, IP subnet, or other ways that meet your business needs.
- Component
- A user defined name for monitored TCP traffic that is displayed in the Tivoli Enterprise Portal workspaces and views. It includes one or more protocols that define the IP addresses and ports to monitor. For example, you might create a component named Production HTTP(S) that includes monitored TCP traffic to servers 9.48.152.128 and 9.48.152.129 on ports 82 and 445.
- Managed system list
- An agent-specific list of managed systems of the same type. For example, you can create a list of Linux managed systems for a particular geographic region named LINUX_LONDON, so that you can distribute profiles that are specific to that location. The list must be restricted to a single type of Response Time Agent, such as Web Response Time, or Robotic Response Time. You cannot mix agent types in the same managed system list.
- Profile
- A common grouping of configuration and monitoring attributes that define which transactions to monitor, when you want to monitor them, and the location on which you want to monitor them.
- Protocol
- A combination of a specific IP address (such as 9.48.152.128) or IP address pattern (such as 9.48.152.*) and port number to monitor for TCP traffic. You can create one or more protocol definitions as part of your Component definitions in the Application Management Configuration Editor.
- Realm
- The security credentials for Rational Performance Tester robotic scripts. Use situations and attributes from RRT_Realms to define realms.
- Transaction
- The business exchange that you want to monitor from the perspective
of the end user. For example, a transaction can occur between a workstation
and a program, between two workstations, or between two programs.
You can create definitions of what to monitor and reuse those definitions
in multiple profiles. There are two types of transactions: real
end-user and robotic.Note: Use of the term transaction when referring to TCP connections refers to a sequence of TCP request packets followed by a sequence of TCP reply packets.
- Real end-user transaction
- A set of filters that match monitored requests. These filters support full wildcard pattern matching on any transaction property and both INCLUDE and EXCLUDE settings.
- Robotic transaction
- A robotic script or CLI command. It is automatically created when a new robotic script is uploaded. This does not apply to CLI scripts because you must type the CLI command into the CLI transaction to run the CLI script.
- User group
- An IBM Tivoli Monitoring security access control list of users who have access to read or modify a profile, application, or client.