Re: Which Protocol to use to Record HTTPS Applications using LoadRUnner 11.0

[James Pulley]

What is your testable hypothesis for which protocol to select based upon your expressed communication basis over http/s?

Have you tested it to see what happens?

On Nov 4, 2012, at 11:13 AM, satyam Reddy <meetv...@gmail.com> wrote:

HI,

we have an web based application Developed in Java and Oracle .Actually its a https application.

Could any one please suggest which protocol to use to record Https applicatioons in LoadRunner 11.0

Regards,

--
 
 

[James Pulley]

Oh, if we're going to use the protocol advisor then the answer is DCOM.

Why, because the answer is almost always DCOM with the protocol advisor.   The man issue with the PA is that you need to have a cultivated architectural eye in order to interpret the multiple options which are brought forth by the tool.    Here you have Satyam Reddy who is struggling to figure out which protocol to select for a web based application which is using a secure sockets layer (HTTP/S) connection.    This is about as straightforward a protocol selection as you can have based upon application architecture.

Give it to PA and you are going to get Winsock, Web, Click and Script, TruClient, DCOM and potentially event Citrix/RDP.    Given those options which would you pick if you don't have a feel for application architecture?   Furthermore, if you don't have a feel for application architecture how are you going to figure out what and where to monitor your application under test for bottlenecks.   This weakness in the architecture area will come back to bite you in your nether regions very rapidly on the subjects of design design, script construction, monitoring and the ability to determine success or failure for your test.

I would put forth a hypothesis that the protocol advisor the absolutely last item you should consider if you have any questions on which protocol to select, definitely not the first.    Look at your application architecture from the system design documents and the installation guides.  Consider the output of protocol analyzer traces and windows sockets recordings to identify well known ports which would point you toward one protocol selection or another.   Look to your mentor for guidance and listen to how they analyze the system.  Try a couple of different options based upon the analysis from the documents and the traces.   Finally when you have made your final decision take a look at the output of the protocol analyzer and see how confusing a path this would have lead you down.

James Pulley

@LoadRunnerBTH @PerfBytes

On Monday, November 5, 2012 1:03:44 AM UTC-5, TitledAroon wrote:

Best way is to use protocol advisor. It comes with vugen 11