There are situations where recording application using protocol Web (HTTP/HTML) encounters problem such as (1) not recording events, (2) not launching or (3) crashing. The context may deviate however the below list aims to provide a quick-and-dirty resolution to the problems. Obviously, the quick-and-dirty may work/not work in different environment and situations, however it will help you scope down the problem in a sequential and logical manner.

1. Use another machine to record
2. Use web_custom_request
3. Configure Port Mappings using “WinInetlevel data” or “Socket level and WinInet level data”. And if necessary, define the port and certs.
4. Use Older Recording Engine
5. Use LoadRunner as Proxy Server on port 7777 for Recording (For Older Recording Engine)
6. Determine OS Support Status and application type
7. Determine the actual protocol and port number using Winsock protocol or network sniffing tools (WireShark Network Analyzer)

I’m leaving out the details at this juncture so that you can have an overview steps of what to do when Vugen is not recording any HTTP events emitting from your HTTP application. I will detailed the steps and reason in the subsequent post; so stay tuned!

Ok, let’s move to the details on the rationals and steps required to get your HTTP application recorded!

[1] Use another machine to record

Install VuGen on another machine and proceed with recording. What we are doing here, is to differ a problematic machine to a working one (at a machine-level troubleshooting). The existing machine may have problems due to a clone image, restricted privileges or previous installation of programs (unless you are pretty sure that your machine is fully workable with Vugen).

[2] Use web_custom_request

Use the basic web request methods for communicating to the server. This is needed when Vugen (sometimes) is unable to recognise the HTTP traffic and compose into web_submit_data APIs. Therefore, by instructing VuGen to record using web_custom_request only, this will detect all unknown communications been used in a HTTP mode to be recorded but in a more unreadable or unfriendly web_custom_request script.

1.1 Create a new Multi-Protocol Web (HTTP/HTML) script; do not create a Single Protocol script.

1.2 In the recording options, select recording to be URL-based script (not HTML mode) and select “Use web_custom_request only”. Proceed with the recording.