Here in this post I am going to describe various things that are required or need to understand with respect to Load Runner 11.0
OS that support LR 11.0
OS that support LR 11.0
- Windows Vista SP2 32-bit
- Windows XP Professional SP3 32-bit
- Windows Server 2003 Standard Edition/Enterprise Edition SP2 32-bit
- Windows Server 2008 Standard Edition/Enterprise Edition SP2 32-bit and 64-bit
- Windows 7
Note: VuGen recording is not supported on 64-bit operating systems.
How to download and Extract LoadRunner version 11 (LR 11)?
Click on "Demos and Downloads"
Enter your HP Passport credentials when needed.
You will have visibility to LR 11 (and other) downloads, if you have support for LoadRunner 11 as part of your HP Support Agreement Identifier (SAID) — HP SAIDs can be configured in the HP Passport Profile.
Procedure to download:
How to download and Extract LoadRunner version 11 (LR 11)?
Navigate to the support portal: http://support.openview.hp.com/
Click on "Downloads" tabClick on "Demos and Downloads"
Enter your HP Passport credentials when needed.
You will have visibility to LR 11 (and other) downloads, if you have support for LoadRunner 11 as part of your HP Support Agreement Identifier (SAID) — HP SAIDs can be configured in the HP Passport Profile.
Procedure to download:
Is Internet Explorer 9 supported by LR or PC 11.x ?
The base version of LR / PC 11.x doesn't support IE 9 by default; you need to contact customer support to get a patch on top of your base installation. It is known as Patch 3, once installed it will support IE9.
LoadRunner 11 applications (controller, VuGen GUIs) are slow to come up
After installing LoadRunner 11 the application UIs are very slow to be presented at sometimes.
It may take a minute or more for VuGen to be presented after it’s launched.
To resolve this slowness try the following
1. Install the latest LoadRunner 11 patches.
2. Add a proxy setting in IE / Internet Settings, if your environment uses a proxy for web/Internet access.
3. If the above does not work, open the following file in notepad :
C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config
Replace empty element:
<runtime/>
with this:
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
The reason why the correlation rules are not working is because the value to be correlated in the generation log in response body is in Plain text format, but when it is used in the script it is in URL format.
for instance in the generation log value is
"3,10 Feb 2011 18:50:13 -0000"
in the script the value is
"3%2C10 Feb 2011 18%3A50%3A13 -0000"
The same value "3%2C10 Feb 2011 18%3A50%3A13 -0000" is also a part of the request body, hence is not being captured.
The automatic correlation rule only handles 2 conversions for formatting as follows:
1. From HTML to URL
2. From URL to HTML
it does not handle Plain text to URL
When you do manual correlation, we are capturing the value and then using the function web_convert_param () to convert the plain text format to URL format, and hence it can be handled on the script. The correlation rules does not have the same level of flexibility as manual functions.
To fix this issue manually correlate the value.
LoadRunner 11 applications (controller, VuGen GUIs) are slow to come up
After installing LoadRunner 11 the application UIs are very slow to be presented at sometimes.
It may take a minute or more for VuGen to be presented after it’s launched.
To resolve this slowness try the following
1. Install the latest LoadRunner 11 patches.
2. Add a proxy setting in IE / Internet Settings, if your environment uses a proxy for web/Internet access.
3. If the above does not work, open the following file in notepad :
C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config
Replace empty element:
<runtime/>
with this:
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
Correlation rules are not working in LoadRunner 11
Correlation rules are not working in LoadRunner 11The reason why the correlation rules are not working is because the value to be correlated in the generation log in response body is in Plain text format, but when it is used in the script it is in URL format.
for instance in the generation log value is
"3,10 Feb 2011 18:50:13 -0000"
in the script the value is
"3%2C10 Feb 2011 18%3A50%3A13 -0000"
The same value "3%2C10 Feb 2011 18%3A50%3A13 -0000" is also a part of the request body, hence is not being captured.
The automatic correlation rule only handles 2 conversions for formatting as follows:
1. From HTML to URL
2. From URL to HTML
it does not handle Plain text to URL
When you do manual correlation, we are capturing the value and then using the function web_convert_param () to convert the plain text format to URL format, and hence it can be handled on the script. The correlation rules does not have the same level of flexibility as manual functions.
To fix this issue manually correlate the value.
No comments:
Post a Comment