Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Microsoft Terminal Server and Citrix in LoadRunner

Microsoft Terminal Server and Citrix in LoadRunner



|Views: 1,489 |Likes:
Published by api-26334688

More info:

Published by: api-26334688 on Oct 16, 2008
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





How to Set Up and Run Load or Performance Tests in a
Microsoft Terminal Server or Citrix Environment
Note: This is an expanded explanation of the Mercury document called Load Testing with LoadRunner in a
Citrix/Microsoft Terminal Server environment., dated March 11, 2002.
Questions, corrections: Whitney Wetherill, 908-626-6022

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:

1. citrix_setup_video.avi.exe
2. Load Testing with LoadRunner in a Citrix/Microsoft Terminal Server environment, March 11,

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.

Both of the above files are useful but elaboration should also help and that is the purpose of this document:
to add to the information provide by Mercury.
Understanding MTS/Citrix

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.

Performance and Load Tests of MTS/Citrix

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.

Performance Test, WinRunner Used With LoadRunner
Setting up the Test Machines
Figure 1 below provides a very basic description of an MTS setup. The drawing can be found at
\\at_lbtciadi01\int_testdocs\Citrix_MTS_Docs\DiagramMTS_Citrix_Solution.vsd for closer inspection.
Detailed explanations for each step are provided following the diagram.
Figure 1, Diagram of MTS/Citrix setup.
C lie n t M a c h in e ( s )
S tep 2.
U se M T S /C itrix to create x+1

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

w in d o w .
T h is is th e o n ly f u n c tio n o f th e
c lie n t m a c h in e . It d o e s n o t
even need to have W inR unner
o r L o a d ru n n e r in s ta lle d .
D e s k to p
S te p 1 .
U s e W in R u n n e r o n th e M T S /
C itrix server to generate a G U I
script. D ebug from this server
(run m anually).
M ake sure Loadrunner is also
in s ta lle d o n th is m a c h in e .
E d it th e file s e ttin g s a s
described in the M ercury
d o c u m e n ta tio n .
T h is b o x w ill b e th e lo a d
in je c to r m a c h in e ( e a c h c lie n t
vuser will launch W inrunner).
M T S /C itrix S e rv e r
A p p
G U I S c rip t
C o n tr o lle r
Step 3.
M a p a d riv e to th e M T S /C itrix

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= (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

in s tr u c tio n s .)
U se th e w izard to fin d th e
W in R u n n e r s c r ip t th a t is o n
th e M T S /C itrix s e rv e r (F ile
ty p e G U I V u s e r).
x + 1 = # of
connections per
c lie n t
M ap Drive
fo r S c rip t.
U se
c o n n e c -
tio n s fo r
lo a d .
x = # of
vusers per
c lie n t

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

Activity (17)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Anuj Mathur liked this
prmukundan liked this
rajusathya liked this
rajusathya liked this
manishkharedocs liked this
uweerasena liked this
mohmedarif liked this
vinovels liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->