Soumya Y Shanthimohan 270004GAQS Visits (1969)
A scenario where it looked like IBM Rational Performance Tester (RPT) was not capturing the 'Refresh' actions. While trying to record a SAP Business Objects session using RPT through Internet Explorer, there were many application triggered 'Refresh' that took place.
The 'Refresh' process would take sometime to end and it appeared like a progress window, as seen below -
RPT was capturing the actions when the 'Refresh' button was manually clicked by the user. However, it looked like RPT was not capturing the actions when the application triggered the 'Refresh' action.
The server replies for the above requests were as below -
There are several such exchanges until the refresh had ended.
Interestingly, it was noticed that the same request was sent again and again during the active session of the "Refresh" progress window. Looking at the server replies, one would think that RPT is not capturing the 'Refresh' actions triggered by the application.
It seemed to be a little confusing looking at the the Client requests with empty html pages and its corresponding server replies. However, after analyzing the requests and corresponding responses, it could be noticed that the RPT script was simulating the below request by looping on -
Until the server could send -
It was also noticed that the Client was sending empty.html requests every 20 seconds until the Server returned a response to the initial POST request.
There was nothing "missing" in the test!!
You can notice that there is a POST request for 'processPromps.jsp' and a GET request for 'report.jsp. The request "report.jsp" might have been sent too soon. RPT will in fact wait until the initial POST's response is received before sending the report.jsp request since the dynamic data (such as the sEntry value) in the report.jsp URL are being extracted from the POST's response. Thus, the playback will automatically have the correct sync
AcdntlPoet 2700019V2G Visits (1969)
Hot off the presses is the top content reused during September to help solve your Rational Team Concert (RTC) issues. Last month the following technotes were the most heavily reused when closing PMRs opened by you, our clients. We hope that highlighting them here will help others encountering the same or similar issues also find quick resolution:
Have you found a technote that helped you solve an issue without having to open a PMR? Let us know by rating and leaving feedback on that content using the "Rate this page" stars on the top right of the content or the box of the same name at the bottom of each technote! Your feedback is highly valuable to us as we work to improve the quality of solutions and help you solve issues more effectively and efficiently.
kellypuffs 06000168YK Visits (1969)
Jennba 270004K1Y7 Visits (1965)
Last night I attended the Super Women's Group panel discussion and reception and took a few notes to share. Before I get started, I am thrilled to say that it was standing room only. (The fire marshal had to turn people away.) It shows the growing number of women doing technology jobs and also the effectiveness of our marketing. Next year, we are getting a ballroom, ladies! Also, this advice can apply to any career and is relevant to all my followers.
kellypuffs 06000168YK Visits (1963)
Can't get enough news and information from Rational Client Support? Looking for another way to interact with us?
Be sure to follow RationalSupport on Twitter at http
I will admit to having mixed feelings about this, mainly because I'm such a Twitter purist. I value the genuine interactions and networking that Twitter provides, and do not appreciate it being used by companies and individuals as simply another media outlet. That being said, our employees, our clients and our business partners are already out on Twitter, sharing their experiences, problems, solutions, and ideas, so why NOT provide a Rational Support presence on Twitter.
It will be very interesting to see where this goes. I promise to do my utmost to make it another valuable tool in your Rational support toolbelt.