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.
What to do next
Now you can view response time
breakdown data in the report.