RojaAyyagary 270005QDMN Visits (305)
Run and Control Rational Performance Tester executions and Reports using a web browser - Part 1
Table of Contents
- Configure Web Reports
- Execution Control
- Display Report
- Export Data
- Customize Web Reports
Traditionally Rational Performance Tester execution is monitored, controlled and reports can be viewed in the workbench. Recently a new feature has been introduced that would allow the test execution be monitored, controlled, view reports, and export data if needed using a browser on another system. Reports can be customized as well.
This article explains how to configure, use web reports in Rational Performance Tester. This feature is being improved as new versions of RPT get released. This document refers to RPT v220.127.116.11. Customization of Reports would be discussed more in detail in Part 2 of this article.
Configure Web Reports
To enable web reports, go to RPT -> Window -> Preferences -> Test -> Performance Test Reports -> Web Reports -> select Allow remote access from a web browser check box.
For Non-secure web access, select No security is required to access reports check box. By default, the non-secure port number for web reports is 8080. If this port number is used by another service, you can provide another port number.
To provide security for web reports, select the Security is required to access reports check box.
To access reports remotely, on another computer, open a web browser and type http
To control the schedule execution remotely using a browser, select Allow control of schedule execution from the web browser check box as shown in the image below.
When accessed remotely during execution of schedule, it appears similar to the screen below. Using this, it is possible to Change Number of Users, Manage Synchronization Points, Stop Test Run, Change Stage Duration and Change Log Level
Rational Performance Tester Web Reports can display Custom Reports, Protocol Independent Reports, Display Service Report, HTTP Reports, Socket Reports, TN3270 Reports and Selenium Execution Report
Under HTTP Reports - Page Performance Report you will find the following tabs.
Page Performance Report
Response Vs Time Summary
Server Health Summary
You can export reports in HTML format for others to view; export an entire run or specific counters to a CSV file for further analysis; or export report metadata (templates) so that other users can generate any custom reports that you have created.
You can also export the web-based charts as image.
If the default reports do not address your needs, you can create a new customized report.
Customizing Web Reports will be discussed more in detail in Part 2 of this article.
Rajeshavanthi 2700022MCX Visits (492)
There are several questions which come up when you are performance testing your application using IBM Rational Performance Tester (RPT). Among all such questions, let's discussion on question like "How to measure the client side page rendering with RPT?" You might say, that you script measuring only the downloading of multiple request/ response for the specific click event and its not capturing the service level agreement statistics to display the downloaded request\response as per the browser level. It could also be a case where, when a script is recorded in RPT, the manual navigation from one page to another takes a lot of time. However, when the script is played back, the response times vary less when compared to what you see manually.
Now, lets look at this from RPT perspective.
IBM Rational Performance Tester is a server load testing tool, designed to measure effects of multiple users on a server. As such it does not make use of a client side browser instead simply interacting with the server
As you know, RPT is used to measure the response time between the fist byte sent in the page's first request and last byte received during the response from the server. The client side experience (how long for a page to be
So in short, there exists no straight forward way to get the measurement metrics pertaining to the client side browser rendering in RPT. However, The client side rendering may be captured as 'Client processing delay' in the recorded test. There may be counter(s) that measure the net server response time but there could be no counters for client rendering. That is understandable because there is no "client" and so no "rendering" that actually takes place when a load is being driven by RPT.
Here's a short note on the impa
dmmckinn 1200006SCS Visits (959)
In continuing on the topic of Performance testing, Vaughn Rokosz takes a look at some of the common reasons performance tests can fail, and suggests ways of tuning your servers to avoid the common issues.
Take a look at his latest article that includes the following:
For your convenience, here is the link to the previous article on the subject: Creating a perf
dmmckinn 1200006SCS Visits (769)
Looking for information about how to build performance simulations?
Building a good simulation of a user population requires expertise at many levels, including:
In the following article Vaughn Rokosz, a technical lead for the CLM performance team, shares some of his experiences with building performance simulations of the Jazz products. He walks through a simple example demonstrating how to build a simulation of a user population that is creating work items in Rational Team Concert. He also shares some of the things used to make the development of performance simulations simpler by attaching the Rational Performance Tester project that he used when working through the example.
Stay tuned for part 2...
Check out these newly published videos for IBM Rational Performance Tester.
vjagadeesh 2700063KJN Visits (999)
Correlation of cookies is not mandatory in RPT. During playback some values which are recorded during scripting are sent to the server to be processed, but these values most of the time are dynamic in nature, and they do not form the page content during response from the server. Cookies are usually cached to be reused by the page, but these do not give the correct response time for the page content. Hence, some times the test is run by disabling the cache. To summarize, no it is not necessary to correlate cookie in RPT, as they do not form the basic contents of the page.
AcdntlPoet 2700019V2G Visits (698)
Export and Import Project Files in Rational Performance Tester- IBM Rational Client Support Engineer Roja Ayyagary provides a demonstration of how to export and import project files in IBM Rational Performance Tester.
Soumya Y Shanthimohan 270004GAQS Visits (911)
While working on a specific scenario, I noticed three different playbacks had three different Page element status codes.
Below was my observation after analyzing the playback data
The Page Element Status code was 100% successful for the first run –
A bar chart that shows the following information to indicate the overall success of the run.
Here, the page element success means that the response code verification point passed for that request. If a request has no verification points, success means that the server received the request and returned a response with a status code in the 200 or 300 category or returned an expected response with a status code in the 400 or 500 category.
Here, if you notice the section ‘Server Health Summary’, the number of total page element attempts is equal to the total page element Status code success. Hence we see success rate for Page Element Status code is 100%
The Page Element Status code was 99.26% successful for the second run -
Notice the section ‘Server Health Summary’, the number of total page element attempts is NOT equal to the total page element Status code success. Hence we see success rate for Page Element Status code is 99.26%
The Page Element Status code was 84.44% successful for the third run -
Notice the section ‘Server Health Summary’, the number of total page element attempts is NOT equal to the total page element Status code success. Hence we see success rate for Page Element Status code is 84.44%
Soumya Y Shanthimohan 270004GAQS Visits (1113)
When establishing the stages of execution in a schedule, you may want to pull down the active virtual users at different intervals but may not find an option to do that in Rational Performance Tester (RPT).
You may also find the below Request for Enhancement (RFE) whose status may say the feature is delivered -
However, the RFE had been closed saying that the functionality was already available in the product.
The explanation is that "Change Rate" could mean "Ramp Up" rate or "Ramp Down" rate depending on the context.
If the current stage has more users than the previous one, "change rate" means "Ramp Up" and if it has lesser users it will mean "Ramp Down",
For example, the first stage may have 100 users and the second stage have just 1 user. The "Ramp Down" happens in the second stage.
vjagadeesh 2700063KJN Visits (732)
Socket recording script correlation in Rational Performance Tester (RPT):
In RPT, the script which is recorded using socket recording do not contain information in request and response format. The recorded script is in send and receive format. Information recorded in the send and receive format is basic in nature, meaning the information is either in binary, ASCII or Hex.
Correlation of these values manually is difficult. The binary data need to be converted to ASCII format before the correlation is performed. Dynamic values are dependent on both the application type and the encoding format used in the application. Hence the correlation in binary format is not done.
Correlation of ASCII format is handled like normal manual correlation.
. The value is searched in the reponse content of the receive message.
. A reference is created, for the ASCII value.
. This is replaced in the send requests in the script.
Sometimes, hex codes are also considered for correlation. Here the hex codes in the receive format are manually converted to ASCII format and the relevant values are considered for reference. Once the reference is created, this is replaced in the send request, as done in ASCII format.
This topic covers the basic of correlation of scripts recorded using socket protocol, using RPT.