HP LoadRunner Readme

for the Windows operating system

Software version: 11.00 Patch 03

Publication date: May 2011

This file provides information about LoadRunner version 11.00 Patch 03.

What's New in LoadRunner 11.00 Patch 03

Mobile Protocols

Two new solutions that expand LoadRunner's capability to include testing load on activity from both native and browser-based mobile applications:

To learn about the new Mobile Protocols, go to Help > Mobile Documentation from the VuGen main window.

Internet Explorer 9.0

As part of its Web protocols, LoadRunner now supports recording on Internet Explorer version 9.0. for Windows 7 Enterprise, 32 bit and Windows Server 2008, 32 bit. Internet Explorer 9.0 support contains the same functionality as previous versions of Internet Explorer for the Web protocols.

Granite DS (Data Services)

LoadRunner has added support for testing applications running on GraniteDS. GraniteDS is an open-source comprehensive development and integration solution for building Flex/JavaEE RIA applications. For details on how to create a script in GraniteDS, see LoadRunner 11.00 Patch 03 Notes and Limitations.

Upgrade to OpenSSL 1.0.

Web HTTP/HTML based protocols now support the new ciphers that are available in OpenSSL 1.0. All other protocols still use the previous version of OpenSSL.

What's New in LoadRunner 11.00 Patch 02

The LoadRunner 11.00 Patch 02 release is a cumulative release and contains the content from the Patch 01 release. You must have the Critical Update installed before installing Patch 02.

This section includes:

Protocols

This section includes:

Ajax TruClient
Citrix
Flex
Web

General

What's New in LoadRunner 11.00 Patch 01

You must have the Critical Update installed before installing Patch 01.

Protocols

Features

What's New in LoadRunner 11.00 Critical Update

The LoadRunner 11.00 Critical Update provides improved performance and stability to the LoadRunner 11.00 release. The LoadRunner 11.00 Critical Update is a required patch and must be installed over LoadRunner 11.00.

What's New in LoadRunner 11.00

Protocols

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.

The following prerequisite software needs to be installed:

System Requirements for VuGen, Controller, and Analysis

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

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 applications. You can record 32-bit applications 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


Load Generator for Windows System Requirements

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

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:
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


 

Load Generator for UNIX System Requirements

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

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


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

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


Product Compatibility

LoadRunner 11.00 is compatible with the following HP product versions:

Pre-Installation Notes and Limitations

This section includes:

Windows
UNIX
Virtual Environment Installation
Diagnostics for J2EE/.NET Requirements

A unique transaction name must be used for each scenario.

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.

The suitable language file can also be copied from the installation disk:

..\lrunner\MSI\setup\international\<lang>\dat\LrwiAedInstallation.xml

to the <LoadRunner>\dat directory.

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 03 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 03 are new for Patch 03 and are in addition to the existing notes and limitations for the previous releases.

This section includes:

LoadRunner 11.00 Patch 03 Notes and Limitations

LoadRunner 11.00 Patch 02 Notes and Limitations

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.

  1. Search for the flex_rtmp_send step containing the initial play argument. For example:
  2. flex_rtmp_send("send_step2",

            "ConnectionID=10",

            "Snapshot=tRTMP6.inf",

            MESSAGE,

            ...

            ...

            MESSAGE,

            ...

            ...

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

            ...

            LAST);

  3. Delete or comment out the flex_rtmp_receive steps that occur during streaming. For example:
  4. //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,

    //         ...

    //         ...

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

    //         "ConnectionID=10",

    //         "Snapshot=tRTMP9.inf",

    //         MESSAGE,

    //         "DataType=user control message",

    //         "EventType=set buffer length",

    //         "MessageStreamID=1",

    //         "BufferLength=100",

    //         LAST);

  7. When you find a flex_rtmp_send step that represents a user action that you want to keep in your script, do the following:
    1. 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.
    2. 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:
    3.     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);

    4. 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.
    5. Identify the flex_rtmp_receive step that indicates that the server has received the end of the user action. For example:
    6. //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);

  8. 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 Notes and Limitations

The LoadRunner 11.00 Critical Update provides improved performance and stability to the LoadRunner 11.00 release. The LoadRunner 11.00 Critical Update is a required patch and must be installed over LoadRunner 11.00.

LoadRunner 11.00 Notes and Limitations

General
VuGen
Correlation Studio
VuGen Protocols
AJAX (Click and Script)
Ajax TruClient
Citrix
Click and Script (All)
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
Controller
Secure Channels
GUI Vusers
SiteScope
Analysis
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
Multilingual Support

This section includes:

Language Packs
Non-Localized LoadRunner on Foreign Language Operating Systems

HP Software Support

You can visit the HP Software Support Web site at:

http://www.hp.com/go/hpsoftwaresupport

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:

http://h20230.www2.hp.com/new_access_levels.jsp

To register for an HP Passport ID, go to:

http://h20229.www2.hp.com/passport-registration.html

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.

The information contained herein is subject to change without notice.

Trademark Notices

Java is a registered trademark of Oracle and/or its affiliates.

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

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

UNIX® is a registered trademark of The Open Group.


© Copyright 2011 Hewlett-Packard Development Company, L.P.