New CLM Whitepaper: Use Rational Performance Tester to monitor Collaborative Lifecycle Management server resources
AcdntlPoet 2700019V2G Visits (2651)
Check out this new CLM whitepaper from Rational Client Support's AVP team member Dayal Sachdev!
Dayal knows that clients today face challenges scaling Jazz environments appropriately and maintaining them, and has written this whitepaper that describes one approach to monitoring a server layer and captures those results for analysis using Resource Monitoring with IBM Rational Performance Tester. The target audience is administrators whom are in charge of hosting and maintaining Jazz CLM tools today while having a moderate understanding of load testing concepts and Jazz tools.
Abstract: Using IBM Rational Performance Tester V8.5 to resource monitor an IBM Rational Collaborative Lifecycle Manager V4.0.3 server hosted on IBM WebSphere Application Server V8.5.5.
Released: September 25, 2013
Authors: Dayal Sachdev
Table of Contents:
vjagadeesh 2700063KJN Visits (565)
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 (477)
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 (701)
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 (898)
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.