Because you can collect response
time breakdown data in historical mode using IBM® Tivoli® Monitoring, you can import this data after you have run a schedule.
You can import response time breakdown data into a test report or
a schedule report.
Before you begin
The monitoring server can be IBM Tivoli Monitoring for Transaction Performance, IBM Tivoli Composite Application Manager for WebSphere®, IBM Tivoli Composite
Application Manager for Response Time Tracking, or IBM Tivoli Composite Application Manager for Application Diagnostics. When
importing response time breakdown data, ensure that the clocks on
all computers are synchronized. If you import response time breakdown
data from a computer for which the clock was not synchronized, you
can use the
Correct Time Offset feature in
the
Performance Test Runs view to adjust the
clock skew. Also, ensure that the management server does not truncate
the Uniform Resource Identifier (URI) in any transaction names. No
response time breakdown data is displayed if the management server
truncates URIs in transaction names. If the management server truncates
URIs in transaction names, increase the value of the TEXTSTRING_LENGTH
property on the management server.
About this task
Typically you import response time breakdown from a live
production environment, rather than a development environment. When
you analyze applications in a production environment, the data you
are working with is data from past activity that has been stored in
a database, which is queried, collected, and imported for analysis.
Procedure
- Right-click a set of execution results in the Performance Test Runs view, and click Import
Response Time Breakdown Data from the menu; alternatively,
right-click a report, and click Import Response Time Breakdown
Data from the menu.
- Specify the location of the IBM Tivoli Monitoring
server:
- Type the IP address or the fully qualified host name
of the IBM Tivoli Monitoring server in the Host field.
- Type the user ID and password for the monitoring server
in Authentication.
- Change the Connection information
if needed. Typically your Tivoli system administrator specifies this information.
- Select Save Password to save
your password locally. If you do not save your password, you might
be prompted for it (depending on the host system configuration) when
editing the configured location or when running test schedules that
use the location.
- Click Next.
- Specify the time period for which to import data.
When specifying the time in a specific number of units, note that
for consistency, "month" is defined as 30 days and "year" is defined
as 365 days. "Days" refer to 24 hour periods, not calendar days. If
you click Specify a time interval, the Start
time and End time will be automatically set to match the run into
which you are importing the response time breakdown data. The selected
units of time are subtracted from the time that you click Finish to import the data to give the start time. For
example, if you select 2 months, the time period will be the 60 days
(24-hour time periods) immediately prior to clicking Finish. Choose Import detailed instance-level data or Import aggregated statistics. You cannot
import aggregated statistics from an IBM Tivoli Composite
Application Manager for WebSphere server. Attempting to do so will result in an error message.
If you want to import response time breakdown data to correlate
with test results, import instance-level data. Instance-level data
correlates to an exact transaction URI (in other words, a specific
page element). Aggregated statistics do not. The Transactions page of the wizard shows a list of all available transactions. The Transaction Pattern column shows the exact transaction
that is recorded. Transactions that contain a regular expression cannot
be correlated with a page element. Contact your Tivoli system administrator to ensure that
instance-level data is collected for the exact URI used in tests.
- Click Next.
- Specify the policies, or traps, from which to import data.
If there are no policies or traps listed, click Back, and then adjust the time period to include an interval where policies
or traps are captured. Click Next.
- Select the hosts from which to import data. Here Host refers to a system that is running one or more IBM Tivoli Monitoring agents; then click Next.
- Select the transactions from which to import data, and
click Next.
- Select the Profiling project and Monitor group under which to store the imported data.
If you imported the data by clicking , then you must change
the default project and monitor. In this case specify your test project
as the profiling project and the report under which you want to store
the data as the monitor; if you do not, the data will not import correctly.
What to do next
Now you can view response time
breakdown data in the report.