Recording Options - Load Runner - Chapter9

• Recording options can be opened via two different ways as below.
• Vugen --> Record--> Recording Options
• Vugen --> Recording icon -->Recording Options link
• Recording options has different settings that can be chosen before starting recording as below:
• General -->Recording: 
• HTML-based script: Is the generic mode of recording, which would capture requests, when your does any clicks. HTML would have less correlations compared to URL Mode.(Will explain this on upcoming posts). HTML mode captures all the non-html resources like(.css, .jpg, .png etc) in a combined requests of web_url.
• URL- based script: It is bit in-depth level of recording compared to HTML mode. URL mode captured all the requests going from browser to server and separate each and every components into separate requests under web_custom_request. i.e .css, .jpg, .png would also be called separately with separate web_custom_request. Mostly URL mode recording options are chosen for handling java-script calls, in-depth functional flows.
• When application is not getting recorded in HTML mode, we can try with URL mode recording, When application is not getting recorded in URL mode, we can try with HTML mode respectively.
• Script --> Script
• Additional settings that may help. You can check/Uncheck whatever is useful according to your need.
• Protocol --> Protocol
• Selected protocol name would be listed here.
• Code Generation --> Code Generation
• This is an important recording options, that needs attention. Both the check boxes should be selected. This helps in identifying dynamic values in our script, which is nothing but auto-correlation.(Will explain this in upcoming posts.)
• Correlation:
• Configuration --> Scan for correlations. Select all check boxes for enabling auto correlation.
• Rules --> Configuring auto correlation rules. (Will explain this in upcoming posts for better understanding)
• HTTP Properties:
• Preferences: 
• Enable checkbox "Generate web_reg_find functions for page titles". This helps for page validation. Which confirms other whether the expected web page is loaded or not.
• Check/Uncheck others based on your need.
• Proxy Recording Options:
• This has been explained in earlier post "How to handle recording issues.".
• Check/Uncheck the option "Use the LoadRunner Proxy to record a local application" to make the VUGEN record the events/requests. This helps in resolving recording issues.
• Network:
• Mapping and Filtering:
• Port Mapping --> Capture Level
• Socket Level data: This is the generic level of recording people use. If Socket level is selected before recording, it calls up SOCKET API which was built by HP Load Runner team to that provides access to internet.
• WinInet Level data: This is another level of recording, which calls up WININET(Windows Internet) API which was created by Microsoft team to provide access to internet.
• Socket and WinInet : It is the combination level of recording mode.
• The advisable way is, first we need to try with Socket Level, if the application were not recorded, then we need to select WinInet level and then finally we can try with both the application together.
• Advanced Port Mapping settings: This is an addition option can be configured if you aware of SSL details. (this is bit advanced which can be learnt later).
• Data Format Extension:
• Chain Configuration: Transforms GWT data to XML format(this is bit advanced which can be learnt later)
• Code Generation: This option can be enabled if the code generation is log is not readable. (this is bit advanced which can be learnt later)

How to Handle Recording Issues - Load Runner - Chapter8

• While trying to record any application, you may face many recording issues as below:
• Issue 1: Application will not launch while recording, the page will get loaded with some error messages like below 
• Error 1:"Page Not Found"
• Error 2: "Internet Explorer cannot display the webpage"
• Error 3: "Web page cannot be found"
• Error 4: "Forbidden" etc.
• Error 5: "Proxy Error"
• Issue 2: Application will be launched and you may be able to navigate while recording, but no recording events would be captured and at the end of recording, the script generated would not have any web requests captured it.
• Issue 3: While recording, browser will get closed abruptly or unexpectedly.
• Issue 4: Missing requests in the generated script.
• Resolution for Issue 1: 
• If you face Error 1 to Error 4: You need to try changing the recording options in recording dialog box. I will explain this in another post (Recording Options - Load Runner).
• If you face Error 5 : Once browser opens up during recording, go to IE Settings-->Internet options -->Connections Tap -->Lan Settings --> Check 1st two check box of proxy settings and provide proxy URL -->Click OK--> Click OK and Refresh. Then the events would start capturing.
• Resolution for Issue 2:
• For this issue, you need to change one recording options in recording settings as below. VUGEN-->Record menu --> Recording Options --> HTTP Properties --> Proxy Recording settings --> check first checkbox "Use the Load Runner Proxy to record a local application" and try recording once. If still issue persist, try un-checking it and try once again. The events will get captured.
• If the above doesn't helped, you need to change the browser in the beginning of the recording and try.
• If still issue persist, Try recording from different machine.
• Resolution for Issue 3: To overcome this issue, either you need to re-install IE or you need to record from different browser or different machine only.
• Resolution for Issue 4: If requests are missing in the newly generated script, then you need to record using FIDDLER tool instead of VUGEN.
• Stay Tuned for more learning. :-)