HP VuGen Certification
HP VuGen Certification
HP VuGen Certification
Chapter 1
During recording VuGen monitors the client end of the database and traces all the requests
sent by the user and received from the user, to the server.
During playback, Vuser scripts communicate directly with the server by executing calls to the
server API. When a Vuser communicates directly with a server, system resources are not
required for the client interface. This lets you run a large number of Vusers simultaneously on a
single workstation, and enables you to use only a few testing machines to emulate large server
loads.
Chapter 2
Running scripts from VuGen is useful for debugging.
VuGen records Vuser scripts on Windows platforms only. However, a recorded Vuser script can
be run on both Windows and UNIX platforms.
If you make changes to a Vuser script while in the Script view, VuGen makes the corresponding
changes in the Tree view of the Vuser script. If VuGen is unable to interpret the text-based
changes that were made, it will not convert the Script view into Tree or Thumbnail view.
When you run a Vuser script, it is processed by an interpreter and then executed. You
do not need to compile the script. Advanced users can compile a recorded script to create an
executable program.
By default, VuGen’s automatic script generator creates Vuser scripts in C for most protocols,
and in Java for Java type protocols. You can instruct VuGen to generate code in Visual Basic or
Javascript.
Note: The C Interpreter used for running Vuser scripts written in C, only supports the ANSI C
language. It does not support the Microsoft extensions to ANSI C.
Header File
All of the non-Java function prototypes are listed in the library header files. The header
files are located within the include directory of the product installation. They include detailed
syntax information and return values. They also include definitions of constants, availability,
and other advanced information that may not have been included in the Function Reference. In
most cases, the name of the header file corresponds to the prefix of the protocol. For example,
Database functions that begin with an lrd prefix, are listed in the lrd.h file.
The following table lists the header files associated with the most commonly used protocols:
Protocol File
AJAX (Click andScript) web_ajax.h
Citrix ctrxfuncs.h
COM/DCOM lrc.h
Database lrd.h
FTP mic_ftp.h
General C function lrun.h
IMAP mic_imap.h
LDAP mic_mldap.h
MAPI mic_mapi.h
Oracle NCA orafuncs.h
POP3 mic_pop3.h
RDP lrrdp.h
SAPGUI as_sapgui.h
SAP (Click and Script) sap_api.h
Siebel lrdsiebel.h
SMTP mic_smtp.h
Terminal Emulator lrrte.h
WAP as_wap.h
Web (HTML\HTTP) as_web.h
Web (Click and Script) web_api.h
Web Services wssoap.h
Windows Sockets lrs.h