LoadRunner – The parameter file is stored in the script directory as .dat file extension.  It can be opened with a simple text editor like Notepad as it is stored in pure text format.  Therefore, you can manipulate the files via the Notepad.  You can also use office applications such as Microsoft Excel or OpenOffice.org Calc to work on the file.  This greatly the amount of work required for maintaining a long list of data.

Quick Test Professional – The parameter file is also stored in the script directory as an excel file, which will be an .xls file extension.  Being an excel file, it can be opened by office applications like Microsoft Excel.  Again, if you do not have money to purchase a licensed Microsoft product, you can always use open source products like OpenOffice.org Calc as an alternative tool as it is still able to work with .xls files.

We hope that by providing you such tips, you will be able to work efficiently with large list of data (that is especially prevalent in LoadRunner)!

Now, if you are proficient in LoadRunner, you may miss out on the details of how to go creating the start-stop transaction for the GUI Vuser script as the details are actually found in the QTP User Manual under the section, “Measuring Transaction” of HP Quick Test Professional User Guide – Volume 2 instead of LoadRunner manual.  In anyway, this is possible and only achievable via amending the scripts in QTP because Vugen will not be able open (read) QTP scripts.

Two ways you can insert a transaction.

• Via Keyword View – You can use Start Transaction icon > Insert Transaction at the step that you want the transaction to start measuring.   Subsequently, you will use Stop Transaction icon to stop the measurement.
• Via Expert View – You can use Services.StartTransaction “Transaction Name” and Services.EndTransaction “Transaction Name” to encapsulate where the start and end measurement.  “Transaction Name” is the name you give to defined for the transaction and this will appear when you run the GUI Vuser script in LoadRunner.

With the above information, you should be slightly more familiar with Quick Test Professional (QTP) integrating with LoadRunner.  However, again there may be more things that need to be considered and I may have left out.  Do feel free to feedback and experiences and anything that I missed out when using QTP in load testing!

In order to circumvent that, we use web_get_int_property API to retrieve the file size.  This file size will then be used to make comparison with the actual known file size on the server.  For usage of web_get_int_property, you can refer to the Function Reference available in Vugen.

On a brief overview, place the web_get_int_property APT after the request (web_url, web_custom_request, etc.) made for the file (PDF/excel).  I’ve extracted examples from LoadRunner Yahoo Groups and list them below for your convenience.

Example 1:

lr_message(“%ld”,web_get_int_property(HTTP_INFO_DOWNLOAD_SIZE));

web_get_int_property(HTTP_INFO_DOWNLOAD_SIZE);

web_get_int_property(HTTP_INFO_DOWNLOAD_TIME);

Note, HTTP_INFO_DOWNLOAD_SIZE does not give the actual size of PDF file.  This HTTP_INFO_DOWNLOAD_SIZE gets the body bytes, header bytes, and chunk bytes.  Therefore, you may need to fine tune the script to determine a range value of the PDF file size due to the header and chunk bytes.

Example 2:

float fFileDownloadSize, fFileDownloadTime, fFileDownloadRate;

funcFileDownload()
{
fFileDownloadSize = (web_get_int_property(HTTP_INFO_DOWNLOAD_SIZE)/1024.);
//in kilobytes
fFileDownloadTime = (web_get_int_property(HTTP_INFO_DOWNLOAD_TIME)/1000.);
//in seconds
fFileDownloadRate = fFileDownloadSize/fFileDownloadTime; //in KB/s

lr_output_message(“Size of download was %.0f kilobytes; Time of download was %.3f seconds”, FileDownloadSize, fFileDownloadTime);

lr_output_message(“Rate of download was %.2f KB/sec”, fFileDownloadRate);

return 0;
}

Example 3:

long DSize=0;

float DTime=0;

DSize = web_get_int_property(HTTP_INFO_DOWNLOAD_SIZE);

lr_output_message(“DSize is: %.2ld Bytes”, DSize);

lr_output_message(“File Download size is: %.2ld KB”, DSize /1024);

DTime = web_get_int_property(HTTP_INFO_DOWNLOAD_TIME);

lr_output_message(“File Download Time is:%.2f Seconds”, DTime / 1000);

90% percentile allows us to know that for a certain amount of transactions are performing at a certain amount of duration.  Of course it’s a really abstract description but anyway how is it useful?  Example, if the 90th Percentile is 10secs, what it literally means is that 90% of all transactions are performing at or under 10secs.  While the remaining 10% are performing more than 10secs.  If you have a SLA or performance requirements that is based on 90% of the transactions to perform under 8secs, you have pass this criteria.

The Percentile can also tell you how the system is performing, such that if there is a higher percentage of slow response time transaction and what is the percentage that is performing higher than the expected transaction response time.  In a typical average transaction response time graph, you can see how the (passed) transactions are performing during the entire load test period over time.  However, the Percentile graph illustrates the (passed) transactions and their percentage with respect to the overall transactions.

In the below example taken from the Analysis User Guide, at the 60th Percentile, tr_amazon_help is at about 4secs, which means 60% and less of tr_amazon_help is responding at 4secs less.  While at the 90th Percentile, 90% of all tr_cnn_weather transactions are responding at 20secs or less.

web_reg_save_param(“p_EmpID”,
“LB=Emp_ID=”,
“RB=\”",
“Ord=ALL”,
“RelFrameId=1″,
“Search=Body”,
“IgnoreRedirections=Yes”,
LAST);

This is familiar coding where p_EmpID will be captured with LB of EMP_ID= and RB of “.  However, another parameter to note in web_reg_save_param is the ORD, or Ordinal.  This specifies the locaiton of the value to capture if multiple occurrences of LB and RB exists.  By default, the value is ORD=ALL which meant that all occurrences will be captured.  When all occurances are captured, they are stored in an array.  The total number of values captured can be accessed by placing a _count suffix after the parameter name.  Example (note, Total_Employees have to be defined as an integer in the script):

Total_Employees=atoi(atoi(lr_eval_string(“{p_EmpID_count}”­));

While to access a specified value in the array, you will put an index after the parameter in _{index} format.  Example illustrates reading the 2nd Employee ID in the array:

Current_EmployeeID=atoi(lr_eval_string(“{p_Emp_ID_2}”­));

Of course, these are just methods to read the values extracted for your scripting work.  Hopefully, you will find it easier when you are performing scripting work.

NOTE (21 Oct 2008):  Corrections to the default value of the Ordinal parameter.  It should be ORD=1, meaning the first occurence, instead of ORD=ALL.

Let’s go through an overview for implementing the Oracle DB. Basically, we are doing in this sequence:

1. Get an account in Oracle and access to the V$ tables that contains the monitoring data.
2. Install 32-bit Oracle client on the Controller machine.
3. Ensuring that proper configuration is done to connect to the DB using TNSNAMES.ora and defining the Oracle path.
4. Login to the DB using SQL*PLUS and run a query to see if you can collect the statistics from the V$ tables.
5. Launch LoadRunner Controller, configure the monitor and start your load test!

Ok, let’s dive into the details!

1. Request for an account and password to be created in the database instance (unless you are the DBA). Example, loadtester, and grant them access to read the following table. These tables consist of the statistic of the database instance.

• V$SESSTAT
• V$SYSSTAT
• V$STATNAME
• V$INSTANCE
• V$SESSION

2. Ensure that Oracle client libraries are installed on the Controller. Remembered that in order to monitor, you need local installation of the client in order for LoadRunner to query the monitoring data. If you do not have the client libraries, download it from Oracle Downloads. Download only the 32-bit Oracle client.

3. If you have the client installed, ensure the 32-bit Oracle client is installed on the Controller, not the 16-bit client.

4. Verify that %OracleHome%\bin is included in the path environment. This can be done by going to START > My Computer > Properties > “Advanced Tab” > Enviromental Settings.

5. Configure the TNSNAMES.ora file on the Controller. TNSNAMES.ora file is a SQL*Net configuration file that defines databases addresses for establishing connections to them. This file normally resides in the ORACLE_HOME\NETWORK\ADMIN directory. (Source: OraFaq)

Attached is an example of the TNSNAMES.ora file. Click here to download.

6. Ensure login successful with the created account (e.g. loadtester) with SQL*Plus from the Controller machine.

7. Ensure the privileges are given properly by typing the following command. If they don’t return results or return access rights issues, most probably the steps for prior to this one has not been configured properly. Therefore, approach the Database Administrator for assistance or go back to the previous steps to ensure they are properly configured.

• SELECT * FROM V$SESSTAT
• SELECT * FROM V$SYSSTAT
• SELECT * FROM V$STATNAME
• SELECT * FROM V$INSTANCE
• SELECT * FROM V$SESSION

8. Launch LoadRunner Controller as per norm and add the Oracle Database Monitor. When prompt, enter the account name (e.g. loadtester), it’s corresponding password and the destination server name. Statistics should be drawn from the V$ table and displayed in Controller.

With the above, you should be able to successfully configure the monitoring environment and the Controller with minimal difficulty.

Note:
You can change the sampling interval for the monitor using the vmon.cfg file located in {loadrunner-installed-dir}\monitors\vmon.cfg

To configure Sybase database monitoring, we will require ASE Monitoring Server (not the ASE) to be installed on the Controller (refer to “How does the monitoring work in LoadRunner?” for monitoring concepts). Furthermore, we will require an additional DLL in Controller for it to work. From the Monitor Reference, the DLL is named, libct.dll. That is for version 12. While in version 15, it’s named libsybct.dll. ASE in short for Adaptive Server Enterprise is a database product from Sybase. To get the latest copy of the ASE server can be obtained from the Sybase website.

• Downloading the installation requires the registration with Sybase. Registration process is hassle-free without any approval needed and you will be able to proceed with download once the registration completes.
• Upon full installation, all components are installed which includes the ASE database and the ASE Monitoring Server. Sample databases are provided in this installation if you required them.
• Both servers are not started by default. Therefore, you will need to configure them and start them up manually.
• To start the server go to START > Programs > Sybase > Adaptive Server Enterprise > Server Config.
• To start the ASE Monitoring Server, go to Service of Windows and find Sybase MONServer_<ASE Monitoring Server Name>.
• Alternatively, the ASE Monitoring Server can be booted from configuring the ASE Monitoring Server. Details for booting the ASEMS can be found in the additional resources.

NOTES

• Controller uses ASE Monitoring Server to monitor and not ASE and therefore, there is a need to ensure the ASE Monitoring Server is started, properly configured and accessible by the Controller.
• Login information to configure the ASE and ASE Monitoring Server are; Login: sa, Password: <blank>
• There maybe a difference of the filenames for the DLLs being used by ASE Open Client Connectivity. The filenames in v15 is libsybct.dll as compared to libct.dll in v12.
• Replacing the file libct.dll with a renamed libsybct.dll (libsybct.dll renamed to libct.dll) in the Controller does not have any impact to the monitoring.
• When configuring the ASE Monitoring Server in the Controller, in the Monitored Server Machines, put the machine name on the network (not the Sybase ASE server itself). In the Resource Measurements on the server machine, put the ASE Monitoring Server name (not the Sybase ASE server itself)

TROUBLESHOOTING

• After installing the Sybase ASE. Ensure that monitoring can be performed by the ASE Monitoring Server on the local machine. Use the Sybase Central console to perform the previous mentioned, by adding the “Monitor” folder. If the monitoring failed, it maybe the case that the ASE Monitoring Server is not started or configured properly. From here, troubleshoot accordingly.
• If monitoring was successful from ASE Monitoring Server locally, use dsedit tool from Sybase client to ensure connectivity.
• If dsedit tool locates the ASE and ASE Monitoring Server successfully, but connectivity fails when connecting via Controller, there might be a configuration problem on the Controller-side.

ADDITIONAL RESOURCES

• http://www.sypron.nl/main.html -Webpage that contains Sybase ASE information.
• http://www.sypron.nl/get_ase_soft.html – Download information for Sybase ASE
• http://www.sybase.com/ase_1500devel – Downloading Adaptive Server Enterprise version 15.0 Developer’s Edition
• http://www.isug.com/Sybase_FAQ/ASE/section1.6.html#scview – Information on ASE Monitoring Server
• http://manuals.sybase.com/onlinebooks/group-as/asg1250e/monbook – Monitoring Server; Information on methods of booting the ASE Monitoring Server.

Most of the time we have to work with the administrator account on a Windows environment in a load test or setting up of monitors. A common problem that I encountered is that I’m unable to login as an administrator to have full privileges to the machine either if some settings have changed throughout the duration of its usage. In anyway, to login as administrator account, you will need to enable administrator login for the Windows XP.

And in order to do that, you will have to edit the registry.

• Click Start, Run and type Regedit.exe
• Navigate to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList
• Use the File, Export option to backup the key (recommended)
• Create a new DWORD Value named Administrator
• Double-click Administrator, and set 1 as its data
• Exit the Registry Editor.
• Log off the current user and return to the login page again. You should be able to see the administrator login.

NOTE: This can also be applied to non-administrator account login on the welcome menu.

You should begin with your loopback interface. Use either localhost or 127.0.0.1. Next, ping your interface by IP number. (Run ifconfig –a or ipconfig /all if in doubt.) If either of these fails, you know that you have a problem with the host.

IP Address (local machine)

Next, try a host on a local network that you know is operational. Use its IP address rather than its hostname. If this fails, there are several possibilities. If other hosts are able to communicate on the local network, then you likely have problems with your connection to the network. This could be your interface, the cable to your machine, or your connection to a hub or switch. Of course, you can’t rule out configuration errors such as media type on the adapter or a bad IP address or mask.

Hostname (local machine)

Next, try to reach the same host by name rather than number. This is to determine if the DNS and name resolution is the cause of the problem. If this fails, you almost certain to have problems with name resolution.

Router Connectivity

Try reaching the near and far interfaces of the router. This will turn up any basic routing problems you may have on your host or connectivity problems getting to your router.

Traceroute Remote Machines

If all goes well here, you are ready to ping remote computers. (You will need to know the IP address of the intermediate devices to do this test. If in doubt, use traceroute to determine the machines.) Realize, of course, that if you start having failures at this point, the problem will likely lie beyond your router. For example, your ICMP ECHO_REQUEST packets may reach the remote machine, but it may not have a route to your machine to use for the ICMP ECHO_REPLY packets.

When faced with failure at this point, your response will depend on who is responsible for the machines beyond your router. If this is still part of your network, you will want to shift your tests to machines on the other side of the router and try to work in both directions.

Before you seek help… If these machines are outside your responsibility or control, you will need to enlist the help of the appropriate person. Before you contact this person, you should collect as much as information as you can. There are three things you may want to do. First, go back to using IP numbers if you have been using names. As said before, if things start working, you have a name resolution problem.

Second, if you were trying to ping a device several hops beyond your router, go back to closer machines and try to zero in on exactly where you first encountered the problem.

Finally, be sure to probe form more than one machine. While you may have a great deal of confidence in your local machine at this point, your discussion with the remote administrator may go much more smoothly if you can definitely say that you are seeing this problem from multiple machines instead of just one.

(Source: Network Troubleshooting Tools” by Joseph D. Sloan)

• Document ID 31731: Troubleshooting guide for VuGen (not stable/crashes/freezes/GPF)
• Document ID 12532: Troubleshooting guide for Controller ( not stable/crashes/freezes/GPF )

There are a couple of solutions in both documents, but we would recommend trying out the following that usually resolves the problem.

• Login as administrator and perform the work with that account.
• Run the batch file.
• Reinitializing the .ini file or the document term it as “recreate the initialization file”.

Take note on the terminology of the administrator here, it is the default administrator account on the Windows operating system without any changes to it’s roles or privileges. If the environment you worked in have default images, or amended administrator account, you may need to use a machine that is “clean” to test out and run Vugen or Controller. On top of the given list from the official vendor, we’ve experiences that certain situations may cause the Vugen and Controller to behave abnormally as well.

Do you have another Mercury/HP product running on the same machine such as QTP or WinRunner? They may conflict with Vugen and Controller when placed together on the same machine. As such, it is advisable to install only LoadRunner components on the machine while other products are to be installed separately.

In addition, you can use Process Explorer (as recommended by the document) to find out if there are conflict with the processes. The link is broken in the document as Sysinternals have been acquired by Microsoft in July 2006. Click Process Explorer to be directed to the actual website.

Do you have DEP enabled in your machine? DEP (Data Execution Prevention) is part of the Windows XP SP2 feature and extends to Windows 2003 and the Vista versions. For more information of DEP, refer to the following resources:

• A detailed description of the Data Execution Prevention (DEP) feature in Windows XP Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows Server 2003
• Data Execution Prevention by Wikipedia
• Data Execution Prevention by Marc Liron

To resolve this problem, you have to disable DEP. This is as described in Document ID 41489: No events recorded in VuGen when trying to record an application on Windows 2003 SP1 or Windows XP SP2.

What are the technology/protocol used by the application? Specified to Vugen recording, the third possibility that causes the problem is the type of application that you are working with. Example, if the application runs on RCP (Rich Client Platform) or applets but communicates in HTTP. For this, you’ve to identify the actual protocol being transmitted and find workarounds to it. In the example of HTTP, you can refer to a previous article, “Quick-and-Dirty Recording Techniques for Web (HTTP/HTML)” for more information.

If all else fails, the best suggestion is to get a “clean” machine, login with the default local administrator and perform a re-installation of LoadRunner. Remember, the definition of “clean” means that the machine operating system is not based on a clone image. Well, we’ve to say that this is not the entire list that the community is experiencing and therefore, if you have a problem relating to the crashing or abnormal behavior, please share with us and we will append to this list accordingly.