Soumya Y Shanthimohan 270004GAQS Visits (1788)
IBM Rational Performance Tester (RPT) is a tool for automated performance testing of web and server based applications.
It allows users to create tests that mimic user transactions between an application client and server.
RPT captures data at the protocol level and supports applications based on the below protocols:
During test execution, these transactions are replicated in parallel to simulate a large transaction load on the server. Server response time measurements are collected to identify the presence and cause of any potential application bottlenecks.
RPT test playback does not invoke the client of the application you are testing. RPT does load testing only on the server (no testing is done against the client).
Attaullah_Syed 270003NDRK Visits (1283)
Author - Eric Solomon
Soumya Y Shanthimohan 270004GAQS Visits (1419)
A scenario where the contents of a PDF document was being datapooled (Eg. Name, address etc) using IBM Rational Performance Tester (RPT).
Soumya Y Shanthimohan 270004GAQS Visits (1411)
A scenario where, the IBM Rational Performance Tester (RPT) recording showed the message: 'This program cannot display the webpage'.
The script also had the required certificates in place.
Soumya Y Shanthimohan 270004GAQS Visits (1701)
What is an IP alias
IP aliasing is associating more than one IP address to a network interface.
IP aliasing in RPT
By default, when you run a schedule, each virtual user has the same IP address. However, you can make each virtual user appear as though it is running on its own host. To do this, you configure IP aliases on the host computer (RPT workbench), and enable IP aliasing in the schedule. When you run the schedule, the network traffic will appear to be generated by multiple hosts.
To avoid IP conflicts, the IPs have to be legitimate, available within the same subnet, and blocked for distribution.
Configuring IP aliases for a remote Windows location
To make it appear that a virtual user has its own IP address during a schedule run, configure IP aliases for each Windows remote location.
Now, when you run the schedule, it will give the impression that the network traffic is being generated from multiple hosts.
Note: To add multiple IP aliases, use the netsh command, as shown in the following example:
The ntcmds.chm file, typically located in C:\WINDOWS\Help, contains more details about the netsh command. When you are finished with the IP aliases, use the following command to remove them:
You can also use a batch file to add and delete the aliases.
Enabling virtual users to use IP aliases
After you have configured aliases at on remote computers, you set the schedule so that the virtual users can use the configured IP aliases.
To set the schedule so that the virtual users will use the IP aliases during a run:
Assignment of IP addresses for each virtual user in RPT
When IP aliases is enabled, it is expected that each virtual users have unique IP address available in order to emulate unique virtual users. However in some circumstances the number of IP address available may be less than the number of virtual users.
The answer to this is, when the location has IP aliasing enabled, RPT will ask the agent computer how many IP addresses it has available. It is up to you to have already configured the computer with these IP addresses. By default, RPT will use all IPv4 (but not IPv6) address available. You can also restrict the selection to IP addresses on particular interfaces.
If there are more virtual users on the location than there are IP addresses (which would normally be the case), RPT will distribute the virtual users evenly (more or less) across the available IP addresses. For example, if your location has IP addresses 192.22.22.02, 192.22.22.03, and 192.22.22.04 and you ran 10 users on the location, you would have a distribution similar to:
192.22.22.02: Users 1, 4, 7, 10
192.22.22.03: Users 2, 5, 8
192.22.22.04: Users 3, 6, 9
Identifying the originating IP address for each Virtual Tester
By default, when you run multiple Virtual Testers the originating IP address will be the IP address of the system hosting the individual Virtual Tester. However, RPT does have a feature (IP Aliasing) that allows you to assign a specific set of IP addresses per Virtual Tester (See the topic ‘Emulating network traffic from multiple hosts’ in RPT online help). If you have IP aliasing set up, there are two ways to verify the originating IP address.
You can see the IP address that a virtual Tester is using by setting the Test Log level of your schedule to ‘All’ and then checking the Extended Properties of a request in the Test Log after a playback. The originating address of the virtual user will appear as the "Local IP Address".
Alternatively, there is a custom code class outlined in the RPT online help (Extending Rational Performance Tester Functionality -> Custom Code Examples -> Retrieving the IP address of a Virtual user) that you can add to your test/schedule that will obtain the IP address