| || |
Reg: Unable to record the application
To access my application in the browser I need to start an SampleClient.exe, which sends the communication to the server. When I am trying to record the application using LR 11.52, it is throwing an error and that error is also seen manually when the SampleClient.exe is not launched and started.
When we had a discussion with the developer, he says that it is something related to the Activex controls and when launching the URL it directly displays the home page, which inturn is a client side activity.
I have tried to capture the traffic using Fiddler, even it didnot help as nothing was captured in the tool.
Architecturally you appear to be assuming that even though this is an executable, that it communicates via the HTTP protocol. What is the basis for this assumption? What is the next upstream architectural component which the client application communicates with? Fiddler is an HTTP proxy, so if your application communicates on some other communications mechanism from HTTP, which would be common for a compiled executable rather than running inside of a browser, it will not capture any communication.
If you record in Windows sockets your executable and then take a look at the first few buffers in the data.ws file, you should find an announcement set of strings which are readable for the type and version of server your client is most likely connecting with. Also, if you examine the functions related to opening a connection in the sockets user, you will find a port identified. This brings in he concept of a well known port for a well known service. For instance, we expect web servers to speak to one or two ports, databases to listen to a specific port by vendor and brand, other services such as telnet and SSH have their own well known ports. You can take a look at the port identified in the connection information to see if this matches to a well known port.
Taking both the well known port as well as the information from the Data.ws should allow you to accurately identify the next upstream architectural component even in the absence of data from developers
Other great sources of data on the next upstream architectural components? The installation and requirements guide for the client, which may mention specific supporting APIs which need to be in place, such as database drivers for ODBC, ORACLE client, etc... You can also use Wireshark/Ethereal as a wire level protocol analyzer, capturing the conversation going back and forth from client to server and decoding the stream by protocol family. This can further confirm your hypothesis established by examining the windows socket virtual user recording.
Replace ineffective offshore contracts, LoadRunnerByTheHour
. Starting @ $19.95/hr USD.
Put us to the test, skilled expertise is less expensive than you might imagine.
Twitter: @LoadRunnerBTH @PerfBytes