Rajeshavanthi 2700022MCX Visits (518)
Often times when you perform user load executions in IBM Rational Performance Tester (RPT), you come across various connection errors depending on the schedule design, network issues and so on. Its also interesting to see that sometimes the connection time-out error takes place only for a few of the virtual users as compared to the rest where the execution succeeds without any failure notice.
RPT is a load generation performance testing tool and mimics most of the recorded behavior during playback of the scripts. So overall whatever the connection times, response times, think times and so on are captured during recording is being utilized during playback action.
Considering this fact, the reason for time out behaviors could be many, but mostly related to how the application is responding to the requests during playback as compared to recorded mode. On the other hand RPT does allow you to modify Time-Out behavior of a recorded test. To access this setting:
Timeout: Specifies the time threshold for initiating the action that is selected for Timeout action. The test will wait up to this amount of time for a response. If the response comes back before the timeout limit, the test will proceed to the next action immediately when the response is received. The Timeout action and Timeout value settings apply to every page in the test.
That being said, there could be several application behaviors which can also impact the time-out properties of requests/response data. Sometimes, the host application server locks out your IP address, because the server notes that your IP address sends several virtual users.
Let's take another such frequently occurring error. For example:
Error occurred during connection to server 'ser
So what does this indicate? In its literal sense RPT tried to open a connection while trying to execute a request to the server for a secondary request (i.e. not the primary but something like a gif) and RPT was unable to open the connection to the server.
It's probably worth looking at all the previous requests and responses. Use the Protocol viewer where you can see the browser view or the actual response from the server. If there are no errors then the symptoms indicate a problem with the application or server under test.
In addition to this, if the network connectivity and bandwidth between the host controller and its agents are not uniform, then this might cause communication errors.
Rajeshavanthi 2700022MCX Visits (558)
IBM Rational Performance Tester (RPT) supports various error handling conditions which can help you narrow down the identification of performance bottlenecks of the given applications. You can specify how error conditions are handled when running a test or schedule. Error conditions include verification point failures, connection failures, server timeouts, custom code alerts, and problems with data correlation.
Say, for example, if you encounter an issue in the first transaction and based on this you want to exit from all the transactions and start from the first transaction all over again. It could also be a case where you cannot continue to next iteration as the loop is provided in the schedule. Let's discuss one simple scenario on similar lines.
Below are the Transactions available in the script:
Below are the HTTP pages available in the Transaction’s:
What happens if you select Exit Transaction and outermost in a request available in ‘Log
So, if you select Exit Transaction and outermost in a request available in ‘Log
RojaAyyagary 270005QDMN Visits (674)
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 v22.214.171.124. 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.
Discussion about RPT and schedule execution error "The workbench received notification that the execution process on Driver <<Agent Machine>> has terminated"
Rajeshavanthi 2700022MCX Visits (559)
IBM Rational Performance Tester (RPT) is a performance test tool which measures the performance of an IT system by generating load on it and measuring the response times of the system under load. RPT generates load by simulating the actions on the system of multiple simultaneous users. In order to achieve this, you might have to design the schedule with appropriate user load defined and configure the locations where these pre-defined user load needs to be executed.
Often times, when you perform such actions where the user loads are pushed on to the agent machine, you might / might not encounter various errors which could be related to insufficient memory defined for the execution, or network connection problems and so on....
This article specifically discusses one such error which is contributed by the way the RPT v126.96.36.199 agent component contributes to the schedule execution and the occurrence of this error holds good for any higher versions of RPT. However, the following solution is restricted for those who are working on the RPT v188.8.131.52 release.
Error: The workbench received notification that the execution process on Driver <<Agent Machine>> has terminated"
The above error might occur even when you try executing a schedule (irrespective of the virtual user load defined) locally on the RPT workbench or explicitly on external Agent machine. You might get involved in various troubleshooting methods such as :
6. Restart the workbench machine and agent machines
7. Configure the schedule with default settings by reducing the logging levels, set the user load = 1vu and execute the schedule
Despite attempting all these methods, the error persists, irrespective of the user load defined. Note that this is a known behavior in RPT 184.108.40.206 with deployment of cross-project assets. You can upgrade to RPT v8.6 where the problem is fixed.
RojaAyyagary 270005QDMN Visits (726)
Ever wondered how you could split a large test into small scripts? Also interested in playing back scripts from multiple protocols in a single schedule?
Compound tests help you to organize smaller tests into scenarios that can then be run end-to-end. Each of the smaller tests in a compound test can run on a different domain if required, such as a mobile device, or a web browser, and so on.
If you need to combine various tests into a single workflow or end-to-end scenario, you can organize the tests into a compound test. Each test may perform a part of the scenario. Each test may also run in a different domain, for example, a web browser or a mobile device. A typical example of a compound test is an online buying workflow. You may have built smaller tests for each part of an online purchase transaction, such as "log on", "log out", "view item", "add to cart", and "check out". You can combine these tests into a single flow in a compound test. When the compound test is run, its individual tests are run in sequence.
The types of tests you can combine into a compound test depend on the testing capabilities you have purchased. If you have purchased only mobile testing capabilities, you can combine tests on mobile applications into a compound test. If you have purchased additional testing capabilities along with mobile testing, you can also combine tests built using Selenium, HTTP tests, Socket tests, Citrix tests or SAP tests into a compound test.
Compound tests can have the following:
When you run a compound test, its test elements are run in the order defined in the compound test. This compound test consists of WebUI test and SAP test.
When a compound test run is completed, a Test Log is shown in the Test Execution perspective. You can work with the information in the test log and also generate test result reports.
You can create a compound test in a test workbench project. If you have an existing compound test, you can import the test to a test workbench project.
Importing a compound test into a Test Workbench project
You can import a compound test into a test workbench project.
To test the performance of multiple tests, you can add all the tests to a compound test and add the compound test to a user group. When you run a schedule, all the tests in the compound test are run in a sequential order.]
For additional information please refer to the Compound Tests topic in the IBM Knowledge Center.