About VUGEN

VUGEN is component of loadrunner used to develop scripts for performance testing your business critical scenarios. After business critical scenarios are identified VUGEN is used to record / Develop script for all you scenarios. Vugen is a protocol based record and playback tool. VUSER concept is one which you wil be hearing very often. Well what is a vuser? The answer is one VUser is equivalent to one human. VUSER is used to emulate the actions performed by human and VUGEN helps vuser to successfully perform this emulation. The actions Vusers Perform are described/develope in the Vuser Script.

How Loadrunner VUGEN works:

loadrunner records / playbacks scripts at protocol level and it doesn’t work at your GUI level (Unlike QTP), it doesn’t perform any gui operations when you play back the script.GUI is not at all important to loadrunner. Loadrunner doesn’t record any client activity. Vugen during recording automatically generates functions that emulate your manual actions instead of manually coding the application’s API function calls to the server. When you start your recording activity in VUGEN, VUGEN captures all interactions between the client and the server. Events like mouse movement, editing data, entering data on the web form or client side is not recorded because these events do not interact with the server. VUGEN pays special attention for all the requests sent by the user and received from the user to the server. When you playback the recorded script from vugen ,the script communicates directly with the server using the Server API calls. Client system resources are not much utilised for this operation.

Lets see how this works when we record on google:

• Internet explorer opens up and tries to establish connection with google
• After successfully connection google page is displayed
• Enter name in the search box and click search
• Clients again sends request to the server
• Server responds back to client by displaying the results

Same thing how VUGEN interprets:

• Add Cookies that google uses for each header
• Make http request on URL http://www.google.com/
• Make http request for each of the gifs on that page
• Above 2 requests may be embedded in one web_url ( Please refer on the modes of recording for the same)
• Web_submit form is inserted for pressing “Submit” of a get or put form.

Vuser Types:

VuGen enables you to record on different protocols. A variety of Vuser types, each suited to a particular load testing environment or topology is used for the same.

Below is the list of protocols used:

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