Types of VUsers

Types of VUsers

LoadRunner has various types of Vusers. Each type is designed to handle different aspects of today's client/server architectures.

You can use the Vuser types in any combination in a scenario in order to create a comprehensive client/server test. The following Vuser types are available: 

The Vuser types are divided into the following categories:

All Protocols: a list of all supported protocols in alphabetical order. 

1.  Application Deployment Solution: For the Citrix protocol. 
2. Client/Server: For DB2 CLI, DNS, MS SQL, ODBC, Oracle (2-tier), Sybase 
3. Ctlib, Sybase Dblib, and Windows Sockets protocols. 
4. Custom: For C templates, Visual Basic templates, Java templates, 
5. Javascript and VBscript type scripts. 
6.  Distributed Components: For COM/DCOM, Corba-Java, and Rmi -Java protocols. 
7. E-business: For FTP, LDAP, Palm, Web (HTTP/HTML), Web Services, and the dual Web/Winsocket protocols. 
8.  Enterprise Java Beans: For EJB Testing and Rmi-Java protocols. 
9. ERP/CRM: For Baan, Oracle NCA, Peoplesoft-Tuxedo, Peoplesoft 8, 
10. SAPGUI, SAP-Web, and Siebel (Siebel-DB2CLI, Siebel-MSSQL, Siebel-Web, and Siebel-Oracle) protocols. 
11.  Legacy: For Terminal Emulation (RTE). 
12.  Mailing Services: Internet Messaging (IMAP), MS Exchange (MAPI), POP3, and SMTP. 
13.  Middleware: Jacada and Tuxedo (6, 7) protocols. 
14.  Streaming: For MediaPlayer and RealPlayer protocols. 
15.  Wireless: For i-Mode, VoiceXML, and WAP protocols. 

Unlike a WinRunner workstation which emulates a single user's use of a client, LoadRunner can emulate thousands of Virtual Users.

Load generators are controlled by VuGen scripts which issue non-GUI API calls using the same protocols as the client under test. But WinRunner GUI Vusersemulate keystrokes, mouse clicks, and other User Interface actions on the client being tested Only one GUI user can run from a machine unless LoadRunner Terminal Services Manager manages remote machines with Terminal Server Agent enabled and logged into a Terminal Services Client session.

During run-time, threaded vusers share a common memory pool. So threading supports more Vusers per load generator.

The Status of Vusers on all load generators start from "Running", then go to "Ready" after going through the init section of the script. Vusers are "Finished" in passed or failed end status. Vusers are automatically "Stopped" when the Load Generator is overloaded.

No additional license is needed to monitor standard web (HTTP) servers (Apache, IIS, and Netscape).

To use Web Services Monitors for SOAP and XML, a separate license is needed, and vUsers require the Web Services add-in installed with Feature Pack (FP1)