Escolar Documentos
Profissional Documentos
Cultura Documentos
0
Deepa – Citrix Community member of Orkut.
Basics - I
Citrix Presentation Server is the flagship product of Citrix Systems Inc. Citrix
Presentation Server 4.0 is a part of the Citrix Access Suite 4.0. The other products
of the Citrix Access Suite are:
Citrix Conference Manager is bundled free with the Citrix Presentation Server and is
the only product that is dependent on the presence of Citrix Presentation Server. The
other products can be installed, configured and managed independently. Briefly, the
component of the Citrix Access Suite has the following functions:
Citrix Access Gateway – SSL-VPN solution from Citrix which can be completely
integrated with Citrix Presentation Server.
The CCA training session will be focused on only one product of the Access Suite –
Citrix Presentation Server. The Presentation Server comes in three editions. They
are:
To provide any or all the above functionality of the Presentation Server, the following
components may or may not be required (the requirement of the component
depends upon the functionality that is to be provided):
1. Presentation Server
2. Presentation Server Clients (Program Neighborhood, Program Neighborhood
Agent, Web Client)
3. Web Interface Server
4. Data Store Server (may be on the same server as the Presentation Server
but not preferred)
5. License Server (may be on the same server as the Presentation Server but
not preferred)
The above components of the Presentation Server can be managed by the following
tools:
Data Store – Data Store is a static collection of data. All server farm configurations
are maintained in the data store which is only readable through the CMC. Data Store
can be created on Oracle, IBM DB2, SQL, MSDE and Access. Access is default
(mf20.mdb). Access database or the MSDE database the method of accessing the
database is indirect. For all other databases it is direct. The static information
includes – Server Farm Name, List of published application, policies, servers in the
farm, administrators of the farm and their rights, installable packages, load balancing
rules.
Local Host Cache – Local copy of a subset of info stored in the data store. It is
responsible for providing the services to the users when the connectivity to the data
store has been lost.
Zone – Logical division of the Farm. Each zone has it sown Data Collector. May or
may not follow the subnet boundaries.
Application Management - I
Here we will take a look at the core feature of Citrix Presentation Server –
Application Management.
2. Content Publishing – Publishing a particular data file for use. Data file can
be a .pdf, .xls, .doc, .html file. Content publishing is not limited to the file types
mentioned here.
All published applications that the user has access to is called an Application Set.
Application Folders can be created to lend organization to the applications that the
user has access to. An application set is made available to the user through the
Presentation Server client. An application set contains only those applications that
belong to a single server farm.
1. Start->Programs->Citrix->Management Consoles->CMC
2. Authenticate to the server farm using your credentials.
3. Expand the Server Farm Name to display the list of folders under it
4. Right click on the Applications Folder and choose Publish Application.
5. Follow the prompts to publish the application.
Application Management - II
Publishing applications and content becomes a much broader when the concept of
content redirection is considered. The following excerpt taken from a Citrix
publication explains the concept of content redirection very well:
With the capability to redirect application and content launching from server to client
or client to server, referred to as content redirection, access to information is
expanded even more. You decide whether users’ access information with remote
applications published on servers or with applications running locally on client
devices.
Note : For your users to access content published with a specified Universal Naming
Convention (UNC) path and through the Web Interface, you must publish the content
with content redirection and redirect to a correctly published application.
• Use content publishing to provide access to document files, media files, Web
pages, and any other type of file, regardless of storage location. Shortcuts to the
published content are presented to users the same way shortcuts to published
applications are presented. You can decide whether users open published files with
local applications or with remote applications published on servers.
http://www.brianmadden.com/content/article/Understanding-Application-Isolation-
Environments-AIE-in-Citrix-Presentation-Server-4
Apart from publishing applications there are a lot of things that one needs to consider
while working on a Presentation Server. One of the most important task is to provide
optimum performance of the application to all the users. Add to that the requirement
of 24 x 7 availability, then post installation server tuning tasks can be a very
impressive.
Taking into consideration the fact that the pre-requisite of installing the Presentation
server is the presence of Terminal Services, tweaking the performance of the
Terminal Services itself goes a long way in providing optimum performance of
applications to users.
The following link to a white paper is very complete in every sense w.r.t.
performance tuning:
http://www.brianmadden.com/content/article/Its-Here-My-Comprehensive-White-
Paper-about-Terminal-Server-and-Citrix-Performance-Tuning-is-Ready
There are certain application specific performance tuning parameters as well which
may be tuned to deliver better performance.
A related concept to performance is that of load balancing. As had been said before,
the feature of load balancing is available in the Advance and the Enterprise edition of
Presentation Server. Presentation Server load evaluators can be configured through
the Citrix Management Console. The default and the advanced load evaluator are
bundled with the Presentation Server. The administrator cannot delete the bundled
load evaluators. They cannot be modified. It also gives the option of defining a
customized load evaluators. Each load evaluator is a collection of rules/ criteria
which define how the load on a server is calculated.
The default load evaluator is based on single criteria - Server User Load with a
default value of 100. The advanced load evaluator is based on three criteria -
Memory Utilization, CPU Utilization and Page Swaps. These criteria are defined on
the basis of an upper and a lower threshold value. The server reports full load when
the higher threshold value is crossed.
The server reports no load when the value of criteria is lower than the lowest
threshold value.
Custom load evaluators can be created by making a copy of the bundled ones or
making a fresh one. Any of the following criteria can be used to define the load
evaluator:
Arriving at the threshold values can be a time consuming task since it would entail
monitoring the server performance under various user loads. Different applications
use different quantities of resources and the type of hardware also determines the
same. So there is no set standard for threshold values.
Once a load evaluator is defined, it can be attached to either the servers in the farm
or the published application. A server or an application can be attached to only one
load evaluator at a time. It is mandatory to have a load evaluator for a server but that
is not so for an application. An application that has a load evaluator attached to it is
hosted on a server which also has a load evaluator attached to it. The load of such a
server will be cumulative for both types of load evaluators. If any one of the criteria in
any one of the load evaluators crosses the higher threshold value, the server reports
a full load. The Load Manage Monitor option of the application and the server gives a
graphical representation of the values being reported by the individual criteria of the
load evaluator.
Note: The load that the server has is reported to the Data Collector. When a user
launches an application it goes to the data collector to get the information on the
least loaded server for that application and gets directed towards it.
This feature basically reduces the time taken to launch the applications. Each
application makes use of certain file which gets loaded in particular memory address
which is called base address. The base address of various .dll files can be the same
which leads to collisions and looking for an alternative memory address to place the
file in. This increases the time taken to launch an application.
VMO takes care of this latency that is experienced while launching applications.
What it basically does is that it stores the alternate memory address that the file uses
in a file called repair.sfo. CtxSfoSvc.exe is the file that is responsible writing onto the
repair.sfo. At a pre-configured time, CtxBace.exe reads the repair.sfo and changes
the files listed in the repair.sfo to always be loaded on the alternate memory address.
The results of running the ctxbace.sfo is found in bindxxx.sfo. CtxBace.sfo does not
destroy the original file. It attaches a hidden file with the same name but a different
time stamp and attaches it to the original file. CtxTestDll.exe tests the rebased file for
proper functionality after the file has been rebased. A driver called CtxAltstr.sys
intercepts each request that is made for a file. In case the file is rebased, then the
modified file is loaded into the memory otherwise the original file is loaded.
There are some applications that do not function well when they are rebased. Any
file which has a digital signature, any file which is protected by Windows Rights
Management are resistant to rebasing and should be included in the Exclusion list of
VMO.
VMO can be configured at the farm wide and server level. It is scheduled to run at a
specific time on a farm level.
http://www.dabcc.com/forumcontent.aspx?sectionid=20