LoadRunner Protocol for ".Net Desktop application"

[SaiKiran Cheemakurthi]

All LoadRunner Experts,

  Which LoadRunner Protocol is used for ".Net Desktop application"?

Thanks,

 Sai

[James Pulley]

Architecturally, what is the next upstream component that your ,net developed thick client communicates with?

--
 
 

[SaiKiran Cheemakurthi]

Java web app with chrodiant framework, jsf

--
 
 

[James Pulley]

So, then to communicate with a web application the _________ communications protocol riding on top of TCP is used.    Additionally, if a SOAP header is present, then it is possible that one could take advantage of the __________ Virtual User Type.

 

For recording thick clients which communicate with web applications using the ________ communications protocol LoadRunner offers the _________ virtual user type and the __________ Virtual user type.    With the ___________ virtual user type it is sometimes easier to use the old recording engine as it includes an option for recording applications that the new recording engine does not.   This sets up a recording proxy on the host which uses port 7777.   The thick client application could then connect to the proxy for recording and then have the communications passed through to the web applications server.    

 

With the new recording engine setting up a man in the idle proxy with the ____________ virtual user type can be cumbersome because you have to use the port mapping feature to set up all of the tunnels where all of the tunnel definitions may not be known.

--
 
 

[SaiKiran Cheemakurthi]

James, What is your Point?

--
 
 

[James Pulley]

Fill in the blanks and you will have your answer.      There are some assumptions here on architectural knowledge of the application, knowledge of communications architectures in general for web and web services, knowledge of LoadRunner and various protocols involving web technologies.

 

Assuming your .Net applications is communicating with a Java Web Application Server as its next upstream component this should set off all sorts of architectural flags for the most likely communications methods which you can confirm with a protocol analyzer or an examination winsock virtual user send and receive buffers in the data.ws file. 

 

Filling in the blanks will give you the most likely candidate, several alternate virtual user types and a couple of recording methods.

 

But hey, it’s a free answer.  It’s worth exactly what you paid for it.

--
 
 

[SaiKiran Cheemakurthi]

Thank you so much, let me try figure it out. Once again thank you so much at least guiding me proper direction

Sai

--