This document describes the setup process for MTS (Microsoft Terminal Server) LoadRunner virtual users and, since they are essentially identical, it should also be useful for setting up Citrix virtual users. However, it was written as part of an MTS solution and has not, at this writing, been tested for a Citrix solution. This document was originally written for internal use and has been modified to become more generic.
Mercury Interactive provides two files that are intended to assist in the setup of Citrix/MTS virtual users.
They are routinely updated at Mercury and an effort should be made to find the latest version on their
Customer Service web site (http://merc-int.com (there is no www)). These documents are:
Note that the first document is an avi.exe file, which will actually "play" as a video (double click the file) if
you are using WINNT. If you are using WindowsXP you will probably not be able to play this file unless
Mercury updates it. The second document is a Word document.
Taking LoadRunner and WinRunner out of the picture for a moment, it is useful to discuss MTS/Citrix
solutions to gain a basic understanding of this technology. MTS/Citrix technology is used to deploy an
application on a server, which must be especially configured for the purpose. The server is then accessed by
client users whose local c:\ drives do not contain any of the application or database files but do contain
MTS or Citrix software allowing them to connect to the MTS or Citrix server. This setup allows the
developers to deploy changes to the application software on the server with no need to change any files on
the client. (Note that there can be multiple servers but we will limit this discussion to one server.) The
MTS/Citrix solution also, if properly implemented, allows the client user to work faster because the only
"work" being performed on the local client machine is the rendering of an image of the application on the
screen. All of the typical client-side work is done on the server.
There are two basic types of information that Mercury's tools can provide for MTS/Citrix technology: 1)
performance as it would be perceived to an actual user and 2) database (or connectivity) load . The first is
essentially a WinRunner solution, because it includes the rendering of the GUI and that piece is critical to
the actual user's experience. WinRunner, used by itself, runs only one "user" on the script. It's primary
purpose is to functionally test the application, so one user is enough. But for performance testing, we need
multiple users. LoadRunner runs multiple users but it does so without rendering the GUI.
The trick for performance testing of an MTS/Citrix setup is to use WinRunner for it's ability to test the GUI
combined with LoadRunner for it's ability to run multiple virtual users. Even in an MTS/Citrix situation, if
the only requirement of the test is to stress the database's ability to handle load, the solution can be
implemented without the WinRunner piece by using LoadRunner to simulate sessions without the GUI
rendering. This document discusses each of these basic tests separately.
c o n n e c tio n s to th e M T S /C itr ix server. This is done m anually before the start of the test. (x = th e n u m b e r o f v irtu a l u s e rs from th is clien t)
In th is p ic tu r e , 2 c o n n e c tio n s are open. The app window is th e M T S C o n m a n .e x e
b o x . C o n fig u re e a c h v u s e r to it's own host connection, e.g. host= 10.10.60.160.1: (The IP a d d r e s s o f th e M T S /C itr ix S erver:1 (S ee detailed
S c h e m a tic o f M T S /C itrix P e rfo rm a n c e T e s t u s in g W in R u n n e r/L o a d ru n n e r
Now bringing you back...
Does that email address look wrong? Try again with a different email.