HP LoadRunner Readme

The LoadRunner 11.00 Patch 02 release is a cumulative release and contains the content from the Patch 01 release.

Protocols

Ajax TruClient

Object Identification

Replay assistance. During replay, if TruClient cannot locate an object in the script, it provides you with a variety of options to locate the correct object in the application, and enables your script to continue to replay.

XPath. Object Identification now provides multiple XPath suggestions.

TruClient includes two new functions in the JavaScript area of a step:

evalXPath(XPath). Returns an array of the objects defined by the XPath in the argument.

random(array). Returns a random item from the array that is provided as its argument.

Steps

Else condition. You can now add an Else condition to an If section in a TruClient script.

Verify step. A new Verify step action was added for the browser object. Possible properties to verify are Title and Location.

Wait for Property step. A new Wait for Property step was added. Wait for Property waits the amount of time specified in the Step Timeout for the specified property to match the specified value. The list of properties you can verify depends on the role of the object.

Property verification. The list of properties you can verify for each object depends on the roles of the object and is no longer limited to visible text, all text, and inner html.

New properties and functions. TruClient now includes more functions and properties for use in your steps. For details, see the sections on TruClient Functions and TruClient Properties in the HP Virtual User Generator User Guide.

Replace with parameter. You can now right-click a value in a step and select Replace with parameter to automatically replace a value with a parameter.

Snapshots

Object icon. When you record a step on a button or similar object in TruClient, the description in the step may now include an image of the object.

Snapshots on errors. Snapshots on errors is now supported for TruClient scripts in Controller.

Compare snapshots. You can now compare recording, interactive replay, and load mode replay snapshots.

General

Web page graphs. You can now view Web page component breakdown graphs in Analysis for TruClient Vusers.

Due to the use of third-party components (for example, Mozilla's Necko), Ajax TruClient measurements are less detailed, and may be less accurate than in other protocols.

Some graphs (for example, Time to First Buffer Breakdown) and some measurements (for example, SSL Handshake, Client/Error Time) are not available.

Browser settings. Browser settings are now accessible in the Ajax TruClient General Settings dialog box, in the Browser Settings tab.

Bookmarks. You can now save bookmarks in the Ajax TruClient General Settings dialog box.

Transactions. The Transaction Editor dialog box now contains indications if your transaction is missing a start or end step.

Citrix

Flex

AMF parsing. LoadRunner now includes improved AMF externalizable object parsing (Action Messaging Format). This makes the process of serializing using an external Java serializer simpler and more robust.

RTMP

Messaging support. RTMP now supports enhanced record and replay of messaging and has been verified for Adobe LiveCycle Data Services ES2 Version 3.1.

Streaming support. RTMP now supports enhanced record and replay of streaming.

When you record a Flex stream, by default, LoadRunner now generates a single flex_rtmp_receive_stream step in place of many flex_rtmp_receive and flex_rtmp_send steps. The flex_rtmp_receive_stream step makes your script more readable (eliminating tens or hundreds of lines) and makes the replay more reliable.

Note: The new flex_rtmp_receive_stream step is generated when the Generate flex_rtmp_receive_stream step option is selected in the Flex:RTMP pane of the Recording Options dialog box. Although this step makes the script more reliable, it does not replay certain actions you may perform while recording your script, such as pause and seek. It also does not replay the automatic requests that the client performs when Dynamic Stream is in use.

If it is important to replay these actions, you can clear the Generate flex_rtmp_receive_stream step option in the Flex:RTMP pane of the Recording Options dialog box, which causes LoadRunner to generate the steps for all of the raw streaming data.

However, to ensure proper replay, you must manually modify the generated script as described in Manually Adjusting Recorded Flex RTMP Steps.

The above functionality has been verified for Flash Media Server versions 3.5 and 4.0.

Externalizable objects. LoadRunner supports externalizable objects over RTMP.

User Data Points. LoadRunner now generates a number of new data points that provide more useful information for analysis. Note that some of the less commonly used Flex RTMP data points from previous versions were removed.

Web

General

What's New in LoadRunner 11.00 Patch 01

Protocols

Ajax TruClient. A new Ajax TruClient Tips and Tricks document provides additional guidelines on working with the Ajax TruClient Protocol. After installing the patch, the document is available in <LoadRunner installation folder>\help\HP LoadRunner v11 00 - Ajax TruClient Tips and Tricks.

Web (HTTP/HTML) protocol - Data Format Extension.

New Design. The Data Format Extension nodes in the Recording Options dialog box have been redesigned.

Create and use multiple chains. You can now create multiple chains and apply selected chains to different sections of the HTTP message. You can also specify a different chain for each Header and Cookie section in the message.

New Prefix/Postfix extension. A new Prefix/Postfix extension has been added, enabling you to truncate a specified section from the beginning or end of a message string, before the string is decoded.

Data Format Extension development. For details on developing LoadRunner Data Format Extensions, see the What's New section of the HP LoadRunner Data Format Extensions Developer Guide.

Citrix driver support. LoadRunner now supports the Citrix driver for Windows 2008.

Citrix client 10.0 and later support. LoadRunner requires the installation of a Citrix registry patch to record or replay on a Citrix client version 10.0 and later. LoadRunner now prompts you to automatically install the Citrix registry patch when working with these versions of the Citrix client. The message also allows you to select to install the patch manually.

Microsoft Remote Desktop Protocol (RDP).

RDP client support. LoadRunner can now record on the following versions of RDP client: 6.0, 6.1, and 7.0.

New supported operating systems. LoadRunner can now record and replay on a remote connection to a machine running the Windows 7 and Windows server 2008 operating systems.

Flex protocol. In the Recording Options > Flex > Configuration node, you can now define an external JVM if you do not want to work with the JRE version that is included with LoadRunner (1.5).

Features

What's New in LoadRunner 11.00

Protocols

Ajax TruClient - An advanced protocol for modern JavaScript based applications (including Ajax) emulating user activity within a web browser. Scripts are developed interactively in Mozilla Firefox.

Silverlight - A new protocol for Silverlight based applications emulating user activity at the transport level. Allows generating high level scripts by automatically importing and configuring WSDL files used by the application.

Java over HTTP - A new protocol designed to record java-based applications and applets. It produces a Java language script using web functions. This protocol is distinguished from other Java protocols in that it can record and replay Java remote calls over HTTP.

Citrix

The Citrix Protocol now supports Citrix Online Plugin versions 11.2 and 12.0.

Added support for Citrix XenApp Server 5.0

Oracle NCA - NCA Java object property support now provides automated creation and registration within a script of a query-answer table of communication between client-side Java objects and the Oracle NCA server.

SAPGUI - Added support for SAPGUI for Windows Client version 7.20.

Service Test - The LoadRunner Controller can run scripts created in HP Service Test 11.00, HP's solution for creating and running automated tests for SOA and headless technologies. Refer to the Service Test documentation for details of creating Service Test scripts for a load testing scenario.

Features

Installation and Configuration Information for LoadRunner 11.00

Prerequisite Software

Specific software needs to be installed before you can install LoadRunner. When you run the LoadRunner installation wizard, if the prerequisite software is not already installed on your computer, the wizard detects which software is missing and provides the option to install it.

System Requirements for VuGen, Controller, and Analysis

The following table describes the system requirements for installing VuGen, the Controller, or Analysis:

Load Generator for Windows System Requirements

The following table describes the system requirements for installing the Load Generator on a Windows machine.

Load Generator for UNIX System Requirements

This section describes the system requirements necessary for installing the HP Load Generator on a UNIX machine.

The following table describes the supported operating systems on which you can install a UNIX HP Load Generator.

Product Compatibility

Pre-Installation Notes and Limitations

Windows

UNIX

Virtual Environment Installation

Diagnostics for J2EE/.NET Requirements

ContentCheck in Multilingual Environments

This version supports ContentCheck rules in French, German, Spanish, and Italian. The correct language file should be installed according to the system locale.

Windows Firewall Considerations

In most Windows environments, Windows Firewall is turned on by default. The firewall does not allow certain LoadRunner components to communicate with each other. The Windows firewall therefore needs to be turned off.

Note: Turning off Windows Firewall increases the risk to your computer's security.

For each process that needs the firewall you can unblock the process by clicking the unblock button in the popup window that indicates that the program needs it, or by manually tuning the Windows firewall from the Exceptions tab.

WAN Emulation

HP Performance Validation SDK

HP Performance Validation SDK version 11.00 can be used only with LoadRunner version 11.00 and above.

Notes and Limitations

Note: This section includes notes and limitations for LoadRunner 11.00 Patch 02 as well as for the main LoadRunner 11.00 release, and all previous patches released over LoadRunner 11.00.

Notes and limitations listed for Patch 02 are new for Patch 02 and are in addition to the existing notes and limitations for the previous releases.

LoadRunner 11.00 Patch 02 Notes and Limitations

Processor	CPU Type: Intel Core, Pentium, Xeon, AMD or compatible Speed: 1 GHz minimum. 2 GHz or higher recommended
Operating System	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.
Memory (RAM)	Minimum: 2 GB Recommended: 4 GB or higher
Screen Resolution	Minimum: 1024 x 768
Browser	Microsoft Internet Explorer 6.0 SP1 or SP2 Microsoft Internet Explorer 7.0 Microsoft Internet Explorer 8.0
Available Hard Disk Space	Minimum: 2 GB

Processor	CPU Type: Intel Core, Pentium, Xeon, AMD or compatible Speed: 1 GHz minimum. 2 GHz or higher recommended Note for Pentium Processors: Intel Hyper-Threading technology is not supported. Hyper-Threading can be disabled in the BIOS. For more information, see: http://www.intel.com/support/processors/pentium4/sb/CS-017371.htm
Operating System	The following Windows operating systems are supported: 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
Memory (RAM)	Minimum: 1 GB Note: Memory depends on protocol type and system under test and can vary greatly.
Browser	Microsoft Internet Explorer 6.0 SP1 or SP2 Microsoft Internet Explorer 7.0 Microsoft Internet Explorer 8.0
Available Hard Disk Space	Minimum: 2 GB

Memory (RAM)	256 MB minimum Note: Memory depends on protocol type and system under test and can vary greatly.
Available Hard Disk Space	150 MB minimum

OS Type	OS Version	Platform
Sun Solaris	Solaris 9 (2.9) Solaris 10 (2.10)	Sun UltraSPARC-based systems
HP-UX	HP-UX 11iv2 (11.23)	HP PA-RISC
Red Hat Linux	Enterprise Linux 4.0 Enterprise Linux 5.0	CPU Type: Intel Core, Pentium, AMD or compatible Speed: 1 GHz minimum. 2 GHz or higher recommended

TruClient. Firefox Security Warning dialog boxes are not displayed in TruClient during script development.

Web (HTTP/HTML). Before recording or regenerating a Web (HTTP/HTML) script for the first time:

Click the Options button in the Start Recording or the Regenerate Script dialog box. The Recording Options or Regenerate Options dialog box opens. This enables the Rules file to be created.

Click OK to close the dialog box.

Citrix. To successfully record a multi protocol Citrix and Web script on XenApp5 only the SessionToken Citrix correlation rule should be enabled. The Session_Token Citrix correlation rule should be disabled.

Data Format Extensions. A script that includes a DFE can only run on a load generator hosted on a Windows platform.

Flex RTMP messaging support. All limitations that apply to AMF3 parsing apply to externalizable objects over RTMP.

flex_rtmp_receive_stream step. If the Generate flex_rtmp_receive_stream step option is enabled, all transactions, comments, and rendezvous points that you add from the Recording toolbar are added to the script after the flex_rtmp_receive_stream step in your script.

Correlations

When correlation rules detect a value greater than 256 bytes, you need to add the web_set_max_param_length function to your script with the necessary value, so that this correlation is handled during replay.

Correlation rules cannot use the web_convert_param function to automatically correlate data that appears in different formats. These correlations need to be handled manually.

Correlation Studio. After correlating you cannot undo the correlation of the script.

Multilingual Support

Manually Adjusting Recorded Flex RTMP Steps

When the Generate flex_rtmp_receive_stream step option is cleared in the Flex:RTMP pane of the Recording Options dialog box, LoadRunner generates flex_rtmp_receive and flex_rtmp_send steps for every communication with the server. This ensures that user actions such as pause and seek, as well as automatic requests that the client performs when Dynamic Stream is in use, are included in the script, but this method also captures less-necessary lines of code that are difficult to read and may not be reliable during replay.

If you choose to clear the Generate flex_rtmp_receive_stream step option in order to capture user data, follow the instructions below to remove the unnecessary steps from your script.

Search for the flex_rtmp_send step containing the initial play argument. For example:

flex_rtmp_send("send_step2",

"ConnectionID=10",

"Snapshot=tRTMP6.inf",

MESSAGE,

...

MESSAGE,

...

"Argument=<arguments><string>play</string><number>0</number><null/>"

...

LAST);

Delete or comment out the flex_rtmp_receive steps that occur during streaming. For example:

//this is the start of the stream:

// flex_rtmp_receive("recv_step2",

// "ConnectionID=10",

// "Snapshot=tRTMP7.inf",

// CHANNEL,

// "ChunkStreamID=2",

// CHANNEL,

// "ChunkStreamID=2",

// CHANNEL,

// "ChunkStreamID=4",

// CHANNEL,

// "ChunkStreamID=2",

// LAST);

// flex_rtmp_receive("recv_step3",

// "ConnectionID=10",

// "Snapshot=tRTMP8.inf",

// CHANNEL,

// "ChunkStreamID=5",

// CHANNEL,

// ...

You can also remove certain flex_rtmp_send steps that are not related to user actions, such as "user control message" types. For example:

// flex_rtmp_send("send_step3",

// "ConnectionID=10",

// "Snapshot=tRTMP9.inf",

// MESSAGE,

// "DataType=user control message",

// "EventType=set buffer length",

// "MessageStreamID=1",

// "BufferLength=100",

// LAST);

When you find a flex_rtmp_send step that represents a user action that you want to keep in your script, do the following:

Manually add a flex_rtmp_receive_stream step before the send step.

Make sure that the ConnectionID argument has the same value as the steps you removed above it.

The Snapshot argument is not relevant for the manually added step.

You can use the ContinueToNexStepAfter = <msec> argument to control the minimum play duration of the stream to download before continuing to the next step.

Determine the flex_rtmp_send steps that represent the user actions you want to keep. These will likely include arguments such as pauseRaw, pause, seek and play2 (for Dynamic Stream). For example:

flex_rtmp_send("send_step5",

"ConnectionID=10",

"Snapshot=tRTMP62.inf",

MESSAGE,

"DataType=command message amf3",

"ChunkStreamID=8",

"MessageStreamID=1",

"Argument=<arguments><string>pauseRaw</string><number>0</number><null/>"

"<boolean>true</boolean><number>12000</number></arguments>",

LAST);

Determine whether there are some extra flex_rtmp_send steps that you can remove. For example, if you dragged a button to seek in the stream, subtle jerks in the motion may be recorded as separate pause and seek actions. In these cases, may not need all of them. Keep only those that describe the desired operations.

Identify the flex_rtmp_receive step that indicates that the server has received the end of the user action. For example:

//this is the confirmation from the server on the "seek" command.

flex_rtmp_receive("recv_step55",

"ConnectionID=10",

"Snapshot=tRTMP68.inf",

CHANNEL,

"ChunkStreamID=2",

CHANNEL,

"ChunkStreamID=2",

LAST);

Repeat steps 2 - 4 for each set of unnecessary receive data and required user actions in your script.

For additional details on flex_rtmp_receive_stream including a complete example, see the LoadRunner Function Reference.

LoadRunner 11.00 Patch 01 Notes and Limitations

LoadRunner 11.00 Critical Update. You should not uninstall the LoadRunner 11.00 Critical Update from LoadRunner, VuGen Standalone, and Load Generator Standalone.

LoadRunner 11.00 Patch 02. You should not uninstall the LoadRunner 11.00 Patch 01 from Analysis Standalone.

Go to HP ALM > Help > Add-ins Page and click HP Quality Center Connectivity Add-in.

Click HP Quality Center Connectivity. The HP Quality Center Connectivity Add-in screen opens.

Click Download Add-in and run the downloaded file.

RDP Protocol. Recording on RDP client versions 6.0, 6.1, or 7.0 will fail if the remote machine is running Windows Server 2008 with terminal services.

Workaround:

When recording a script on a remote machine running Windows Server 2008 with terminal services, use RDP client versions 5.1 or 5.2.

When recording a script on a remote machine running Windows Server 2008 with RDP versions 6.0, 6.1, or 7.0, remove terminal services.

Citrix protocol. Citrix Agent text trapping does not work on the following environments:

Citrix servers installed on Windows Server 2008 R2.

64 bit applications running on Citrix servers installed on Windows Server 2008 64 bit.

Java protocol. When recording on Internet Explorer 8 using the Java protocol, you must first close all instances of Internet Explorer before LoadRunner opens an Explorer instance for the record session.

TruClient protocol versions. If you edit a TruClient script using a later version of LoadRunner than the one on which you recorded the script, it may fail to replay in some cases.

Before modifying the script, save a backup copy of the script.

Workaround: If the replay fails, re-record the script using the latest version of the TruClient protocol.

TruClient protocol Eval C step. The Eval C step in TruClient no longer supports the Filename argument. Scripts that used the Filename argument will fail when run in LoadRunner 11.00 Patch 01.

Workaround: Use the #include directive to include an external file in your script.

Correlations Studio.

Correlation Studio cannot add the web_set_max_html_param_len API automatically if the captured value is longer than 256 characters.

Correlation Studio does not support the Remove Correlation function.

LoadRunner 11.00 Notes and Limitations

General

To run LoadRunner on Windows 7 or Window Server 2008, you must have Administrator privileges and User Account Control (UAC) must be disabled.

Internet Explorer 8

For Click and Script based protocols, address bar operations and pop-up windows are not supported.

The Internet Explorer SmartScreen Filter must be disabled when recording with Citrix Web Access (formerly known as Citrix NFuse).

Internet Explorer Enhanced Security Configuration should be disabled when recording with Citrix Web Access (formerly known as Citrix NFuse) recording on Windows 2003/2008 Server.

WinInet recording is not supported.

Recording on 64 bit machines is not supported, however replaying scripts on 64 bit machines is supported.

FTP active mode with SSL is not supported in both explicit and implicit flavors.

The network speed simulation settings in the Network: Speed Simulation node in the Run Time Settings do not work with Windows 7. Virtual users will use the maximum bandwidth regardless of which option was selected.

It is not recommended to install and uninstall a Load Generator standalone installation on the same machine with a VuGen standalone installation.

The Load Generator cannot run Citrix scripts in service mode when the script was recording using Citrix Client version is 11.2 or higher.

The Agent icon does not appear in Windows 2008 and Vista when the LoadRunner Agent service is launched.

When LoadRunner Agent runs as service (magentservice.exe), files that are stored on remote network drives or referred to by UNC path cannot be accessed (script, parameter file, etc.). If you want to access files this way, run the LoadRunner Agent as process (magentproc.exe). If this is not possible, please contact Customer Support.

VuGen

SAP (Click and Script) recording. During recording, if you use a keyboard option instead of a UI element (for example, pressing Enter instead of clicking the log on button), the step may not be recorded. In general, when recording your script, it is recommended to use UI elements rather than keyboard options.

Citrix snapshots. Black snapshots may appear during record or replay when using Citrix Presentation Server 4.0 or 4.5 (before Rollup Pack 3).

Possible workaround: On the Citrix server select Start Menu > Settings > Control Panel > Administrative Tools > Terminal Services Configuration > Server Settings > Licensing and toggle the Per User/Per Device.

Recording Window Size and XenApp Plugin for Hosted Applications 11. The recording window size option does not work properly with the XenApp Plugin for Hosted Applications 11. The size of the client window is installed, but the server screen resolution is not. This is a Citrix Client limitation and will be fixed in future Citrix Client versions.

Workaround: When recording, set the window size equal to the local screen resolution. When replaying/load testing, set the VuGen or Load Generator screen resolution to equal the resolution used when the script was recorded. To verify the recorded resolution, view the Window property in the <Script Folder>\default.cfg file.

For the following protocols, replay is supported, but recording is no longer supported: Siebel DB2, Siebel MSSQL, Siebel Oracle, and Voice XML.

In Test Result reports, you can only use the Export to HTML file utility for scripts replayed in version 9.50 and later. To generate an HTML report for scripts created with earlier versions, run the script again in the 9.50 version (or later) of the product.

If you terminated the Protocol Advisor immediately after the detection process started, the Protocol Advisor may leave a hung process of the detected application, causing all recordings and detection sessions that follow to fail.

Workaround: Manually terminate the hung process.

The new Web snapshot model is backward compatible with previous versions of LoadRunner, however some snapshot data may be missing. If this occurs, regenerate the script.

The JSON Data Format Extension does not work in UNIX environments.

Recording a network based application on Windows 7. To record a network-based application (including Web), IPv6 communication must be disabled. Follow the instructions in http://www.addictivetips.com/windows-tips/how-to-disable-ipv6-in-windows-7/ to disable IPv6 on Windows 7.

For protocols using XML, replay fails to create a request when a parameterized input argument contains the ampersand (&) character.

Correlation Studio

VuGen Protocols

AJAX (Click and Script)

Ajax TruClient

Citrix

Click and Script (All)

Does not support VBScript

Does not support user actions on ActiveX objects and Macromedia Flash.

Scalability is lower than the Web HTML protocol, depending on the size and functionality of the business process.

Replay snapshots may differ from the actual Web page.

Support of right-to-left languages is limited (e.g., bi-directional or reversed text may not be processed as expected). This is defined by the default operating system translation table.

Recording an application in a specific language (e.g., French, Japanese) must be performed on a machine whose default locale (in Settings > Control Panel > Regional Options) is the same language.

The locale of the load-generator machine, including the default non-Unicode character set, must be configured to be the same as that of the recording machine. It cannot be assumed that the UNIX default character set is the same as in Windows, even for US-English machines, and this has to be explicitly verified. For example, the default character set on some UNIX machines, such as Linux, is UTF-8.

The Recording Options dialog box may take a long time to open.

Citrix Clients 11.2 and higher do not support the TCP/IP mode in the Citrix > Login node of the Recording Options dialog box.

When recording Citrix Web Access (formerly known as Citrix NFuse) applications, set the window size to "No preference" in the Citrix XenApp web portal preferences page.

Web (Click and Script) no longer supports replay of Applets and ActiveX objects. This functionality is now part of the AJAX (Click and Script) protocol.

Java (All)

Listing Directory Service (LDAP)

Media Player (MMS)

Media Player scripts fail with the error: Error -86801:Host access denied, <hostname> not available or missing.

Workaround: Call the mms_disable_host_check function in all Media Player scripts.

Microsoft .NET

Microsoft Remote Desktop Protocol (RDP)

SAP (Click and Script)

SAPGUI

Silverlight

WAP

Web Services

In VuGen Tree view, you may experience problems viewing/editing the following types of elements: any_object, CDATA, derived and recursive.

For large SOAP envelopes, Record and Replay snapshots are disabled.

The Import SOAP feature is not supported for envelopes containing a single element larger than 500KB.

Recording requests with attachments or security is not supported.

For Axis toolkit, Web service calls that include both attachments and security are not supported.

For .NET toolkit, SOAP version 1.2 is not supported for asynchronous calls.

You can enter text strings up to 10 KB to encode to base 64. If your string is larger, use the Get from file option.

For Axis toolkit, to use base64Binary encoding in scripts created before version 9.10, you must update your WSDL.

VuGen supports Web Service messages over JMS message Queue, but does not support JMS Topics.

JMS Bindings Extensions are not supported.

All services in your script should have the same security scenario. This can be configured via the Protocols and Security tab.

Asynchronous Web Service calls and custom user handlers are not supported for WCF.

The IsNonceIncluded and TimestampFormat properties of web_service_set_security are only supported in Script view and not in Tree view.

LoadRunner cannot replay scripts containing the soa_xml_validate function.

Note: For more detailed Web Services limitations, refer to the HP Service Test readme.

Controller

Secure Channels

GUI Vusers

SiteScope

Analysis

Analysis currently supports Microsoft SQL Server versions 2005 and above.

If you are using Microsoft SQL Server 2000, you need to either migrate Analysis data, or upgrade to Microsoft SQL Server 2005. The following tasks describe how to perform the migrating and upgrading procedures:

To migrate legacy Analysis data to a SQL 2005 server:

From the SQL Server Management Studio, using Object Explorer, connect to an instance of SQL Server Database Engine.

Expand Databases, right-click Analysis database, select Tasks\Copy Database.

Follow the instructions in the wizard.

To upgrade SQL 2000 to SQL 2005:

Backup Analysis database on the SQL 2000 (http://msdn.microsoft.com/en-us/library/cc966495.aspx)

Uninstall SQL 2000.

Install SQL 2005.

Restore Analysis data from backup. (http://msdn.microsoft.com/en-us/library/ms177429(SQL.90).aspx)

If you are using Microsoft SQL Server 2005 to store Analysis data and you apply a global filter on the Analysis graphs, errors may occur due to a Microsoft limitation. If an error occurs, try to apply the global filter again.

If you are using your own policy in an MS SQL server, you may need to add your own account to the Analysis database template (in the <LR Installation>\bin\dat folder).

When exporting Analysis reports to MS Word, take into account that the content load may affect the table format within the document. The RTF format is recommended.

The following Analysis default settings have been modified: Include Think Time is disabled and Generate complete data only is enabled.

There is a limitation with MS Access and SQL queries when filtering a large number of transactions (greater than 100).

Even after running the <Language> User Interface Pack, the Analysis UI data generated from the sample session (in the <LR Installation>\tutorial folder) will display in English. Filtering the graphs will fail. Workaround: Re-generate the graphs and then the corresponding language from the <Language> User Interface Pack will display and filtering will work.

LoadRunner Integration with HP Service Test

For more information about Service Test licenses, refer to the HP Service Test Installation Guide.

WAN Emulation

Windows Vista

To run LoadRunner on Windows Vista, User Account Control (UAC) must be enabled for users with User privileges. For users with Administrator privileges, UAC can be enabled or disabled.

Running the Windows Aero user interface on Vista machines, may slow down VuGen UI performance.

On Vista machines, icons may not appear correctly in some dialog boxes.

If LoadRunner is installed on a machine running Vista, LoadRunner cannot be integrated with WinRunner.

On Vista machines, replay for LDAP scripts recorded over SSL is not supported.

If you want to connect to HP Quality Center from a LoadRunner machine running Vista and the Quality Center client is not installed on your machine, you need to have Administrator privileges on the Vista machine.

Replaying a VB Vuser on a load generator machine with Windows Vista requires administrator privileges.

When running a LoadRunner Agent on a Load Generator machine running Vista, it is recommended that you restart your machine after installing LoadRunner, before running Vusers.

When running the LoadRunner Agent service on a Vista machine, the Agent Configuration will not restart the agent service if it is already running. To manually restart the Agent service, Choose Start > Administrative Tools > Services. Select the LoadRunner Agent service and choose Stop from the right-click menu. Restart it by selecting the LoadRunner Agent service and choosing Start from the right-click menu.

On Vista machines, when recording with MS Exchange (MAPI) protocol, the read_next_mail and mapi_read_next_mail_ex functions work only once per script, resulting in reading only the first message in the mail box.

On Vista machines with UAC enabled, FTP sessions cannot be recorded on Internet Explorer.

Workaround: Change the following Internet Explorer options:

Disable Protected Mode by clearing the Enable Protected Mode check box under Tools > Internet Options > Security.

Check the Every time I visit the webpage option under Tools > Internet Options > General > Browse history > Settings.

Multilingual Support

Language Packs

LoadRunner User Interface Pack. While installing the Language Pack a warning message may be displayed that the HP LoadRunner Launcher Process is in use.

Workaround: Click Continue to continue the installation.

Tutorial scripts. After the Language Pack installation, all sessions and scripts in \HP\LoadRunner\tutorial are still in English.

LoadRunner User Interface Pack. If you are working with a LoadRunner User Interface Pack, it is recommended that you install it before running LoadRunner for the first time.

Menus and toolbars. If you install a LoadRunner User Interface Pack after running LoadRunner for the first time, the menus and toolbars may not get translated.

Workaround:

Close LoadRunner and delete the following folder from the registry: HKEY_CURRENT_USER\Software\<Folder Name>, where <Folder Name> is the drive on which you installed LoadRunner.

For example, if LoadRunner is installed on the C drive, the registry folder name would be: HKEY_CURRENT_USER\Software\C:

Restart LoadRunner.

Report Templates in Analysis. If you install a LoadRunner User Interface Pack after running LoadRunner for the first time, the Report Templates in Analysis (Reports > Report Templates) may not get translated.

Workaround:

Close LoadRunner and copy the files from: <LoadRunner User Interface Pack CD root>\Reporting to folder <LoadRunner installation folder>\bin\dat\Reporting.

Restart LoadRunner.

Non-Localized LoadRunner on Foreign Language Operating Systems

Language support. LoadRunner only supports English and the native language of the machine's operating system. For example, if you are using Japanese Windows XP, you can work with LoadRunner in Japanese and in English.

Installation path. The path in which installation files for LoadRunner are located, and the path in which LoadRunner is installed, can contain only English characters.

Diagnostics add-in. To use the Diagnostics add-in with Controller on a computer with a non-English operating system the Diagnostics_9.0_8.0_LR_Addin_QCCR1I52206 hotfix should be installed. For further assistance, contact HP customer support.

.NET Framework 3.5 failure. Installing LoadRunner on a localized machine may result in a failure in the .NET Framework 3.5 installation process, and you will be asked to terminate the installation. This happens because the .NET 3.5 Framework installation attempts to download the Framework Language Pack but fails.

Workaround: Terminate the LoadRunner installation according to the Installation wizard's instructions and invoke the LoadRunner installation again.

Online Help. The search functionality may not function as expected for strings that contain Chinese/Japanese characters (except Japanese full-width Katakana).

Workaround: Add a half-width space after each character in the search string.

Online Help. For optimum performance of the online Help, you should install the latest JRE.

Japanese characters in Web (HTTP/HTML) scripts. If you set the advanced recording option to specify the encoding of an application, and the application uses different character encoding for different pages, then the recording log or script may display invalid Japanese characters. This does not cause any errors in the script replay.

Non-breaking spaces in Web protocols for Far Eastern languages. A non-breaking space (      `\xA0', etc.) cannot be represented in some Far Eastern locale character sets (in which it is considered a lead byte). Instead, non-breaking spaces are converted to regular spaces (` `, `\x20', etc.), both during script code generation and replay. This may cause replay problems, such as mismatches in length due to eliminating multiple regular spaces.

Workaround: To work around this issue, either:

Remove/add space(s) from/to the script so the comparison succeeds.

Specify regular expressions to avoid the issue.

Standalone installations. The installation interface of the VuGen and Analysis standalone are in English and not localized.

Flex AMF call properties. Multibyte symbols in Flex AMF call properties will be corrupted in the script text view.

ODBC protocol and Oracle-2T protocols. When recording a script in VuGen using the ODBC or Oracle-2t protocols, if you stop the recording while the AUT is still open, VuGen may crash.

Workaround:

Close LoadRunner.

Open the file <LoadRunner installation folder>\dat\protocols\options\script\general.opt in a text editor.

Comment out the following line by adding a semicolon at the beginning of the line:

Option=DumpProcesses

So it looks like this:

;Option=DumpProcesses

PDF report. In Analysis, a PDF report may be generated with unreadable characters if it contains non-English characters.

Workaround: Before you generate the PDF file, change the font in the Report Template that you are using.

Select Reports > Report Templates.

Select the template that you want to use.

In the Detailed Report section, select the Format tab.

For each UI element in the list, change the font to the desired font that supports the language in which the report is written.

Diagnostics add-in. Using the Diagnostics add-in with Controller on a computer with a non-English operating system is not supported.

Workaround: Install the Diagnostics add-in with Controller on a computer with an English operating system. The generated results can be viewed with a localized version of Analysis. For further assistance, contact HP customer support.

HP Software Support

This web site provides contact information and details about the products, services, and support that HP Software offers.

HP Software online software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support site to:

Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To find more information about access levels, go to:

Legal Notices

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Oracle® is a registered US trademark of Oracle Corporation, Redwood City, California.