LoadRunner/Performance Center support for Java Web Start (HTTP or JNLP)

Support for Java Web Start in VuGen / LoadRunner-Performance Center

Java Web Start is provided by Sun Microsystems. Java Web Start could have a HTTP or a Java Network Launching Protocol (JNLP) implementation. LoadRunner-Performance Center will capture HTTP communication.

JNLP Implementation:

Verify if you can run the application outside of Java Web Start. If so, please contact HP Software Support for the RMI/Corba qualifier to verify the support first before attempting to record.

Using Java Web Start technology, standalone Java software applications can be deployed with a single click over the network. Java Web Start ensures the most current version of the application is deployed including the correct version of the Java Runtime Environment. All the jar files are downloaded to the cache and the environment is setup on the fly by Java webstart — hence the environment for recording using VuGen is not set correctly by default.

Follow these steps to do the recording:

1. Create a folder "jars" in a temp folder to save all the application specific jar files.

2. Follow the procedure below to download all the jar files to the above folder:

a. Open the .jnlp file associated with the application launch.

b. Locate the tag in the file. Link to all the jar files will be within this tag.

c. Open a browser. Paste the .jar

d. Save the jar in the above location when asked.

e. Do the same for all the jar files.

SUMMARY OF ABOVE: Determine all of the jar files the app is using, and put them in a temporary folder (preferably in a path without spaces — like c:\temp\jars etc). If the jnlp file is not available, use any other means to determine which jar files are in use, and copy these application’s jar files to a temp directory.

3. Follow the System Configuration as mentioned below:

a. You will need the Sun JDK installed on your client machine (the same version used by the app) — it is preferable to install LoadRunner-Performance Center and Sun’s Java Development Kit (JDK) to a location using a path without spaces.

Example: C:\LoadRunner or C:\JDK but not C:\Program File\LoadRunner

b. Setup the System PATH as follows:

i. Right click on My Computer > Properties > System Properties > Advanced > Environment Variables

ii. Append LoadRunner and JDK to the path. The information should be entered in the following order ; note that the order is very important:



–<JDK>jre\bin\client (** For JDK 1.5, the Classic folder is replaced by the Client folder)

— The rest of the PATH for your machine

Example: PATH=C\:JDK\bin;C:\LoadRunner\bin;C:\JDK\jre\bin\client

iii. Click <OK> and close the System Properties Window.

c. Setup the System CLASSPATH as follows:

i. Right click on My Computer > Properties > System Properties > Advanced > Environment Variables

ii. Add LoadRunner and JDK to the CLASSPATH. The information must be entered in the following order:



–Any files needed for your Java application/JAR files stored in temp directory & collected in step (2) above.

–<JDK>\jre\lib\rt.jar (** JDK 1.2.2 and above only)

–<JDK>\lib\classes.zip (** Lower than JDK 1.2.2 only)

Example: CLASSPATH=C:\LoadRunner\classes;C:\LoadRunner\classes\srv;C:\JDK\jre\lib\rt.jar

iii. Click <OK> and close the System Properties Window.

d. How to verify your Environment setup in LoadRunner

i. After setting up the machine as specified in the System Configuration section above, run a "blank" Java Virtual User in Virtual User Generator (Vugen):

Create a new Java Record and Replay script, and when you start recording, immediately click "cancel" to the "Start Recording" dialog box. Replay this script — there should not be any errors during the run. Being able to run a blank script shows that the environment is configured, and that LoadRunner is able to make calls to the appropriate executables (PATH settings) as well as access the relevant class files (CLASSPATH settings).

e. To record the application, use a batch file.

Leave a Comment