IBM Rational Performance Tester (RPT) is a user load performance testing application which can record traffic communicating over several protocols such as HTTP / HTTPS, Socket, TN3270 and so on. For all RPT supported protocols, refer to Types of applications for testing with Rational Performance Tester.
If you want to check what protocols are getting involved by the application during its course of communication, refer to How to find if the protocols used by the test application is supported by Rational Performance Tester.
In certain cases, when you invoke the application under test (AUT) via RPT's built-in HTTP recorder, the AUT might not display the page or rather the page elements. It’s quite obvious that if the AUT is trying to communicate over secured network (HTTPS), there might be various parameters like:
- What's the Cipher Strength used?
- What are the client and server certificates involved?
.................. and so on, which can contribute such behavior.
It could also be a case where you have to check which TLS versions are supported by the AUT. The TLS (Transport Layer Security) protocol is responsible for the authentication and key exchange necessary to establish or resume secure sessions. During a secured connection establishment, the following is managed.
- Cipher suite negotiation
- Authentication of the server and optionally, the client
- Session key information exchange.
You may access an application via a browser interface and notice that the application requires some certificate to be downloaded and tries to communicate via some TLS versions (Sample snapshot shown below).
Sometimes, it so happens that the traffic communicates over higher cipher strength as well. In such cases, you have to enable RPT to support this level of cipher strength as documented in Enabling Strong encryption greater than 128 bit key lengths in Rational Performance Tester.
But in some cases even though the traffic communicates over unsecured mode and smaller cipher strength (112 bit keys as shown in above snapshot), the AUT does show blank page when accessed via RPT's HTTP recorder. An ideal way to handle such situation is to disable the higher values of TLS specification within the RPT's recorder window during the recording course and check if the AUT shows up loading of all page contents.