|
<< Click to Display Table of Contents >> Servers for thin client solutions |
  
|
|
<< Click to Display Table of Contents >> Servers for thin client solutions |
|
In this topic, rules of thumb for dimensioning of the hardware in thin client solutions for cadett ELSA are discussed.
In a thin client solution, cadett ELSA is running on a server, not on a workstation. The client acts as a terminal towards a server. There are multiple advantages with such solutions, but also some disadvantages.
•Low bandwidth demand
•Relative high latency demand (meaning that a low latency is required)
•High server demands, especially when the number of clients exceeds 3 - 4.
Solutions from Citrix, Microsoft, and TSplus are supported (Citrix XenApp and similar, Microsoft Remote Desktop and similar, TSplus).
If the number of concurrent users is lower than 4, a so-called "small thin client solution" is sufficient. In that case, one single server can manage both the server and the clients of cadett ELSA. We refer to that case as a “small thin client solution”.
•Suitable for up to 3 - 5 simultaneous users (recommended max. 3 - 4)
•Shared cadett ELSA and client server
If the number of concurrent users exceed 3 - 4, a so-called "large thin client solution" is required. In that case, a separate cadett ELSA server is used, similar to a conventional cadett ELSA server. The clients are handled by a number of separate client servers, each one handling up to 3 - 4 concurrent users.
•Suitable for more than 3 - 5 simultaneous users
•Separate cadett ELSA server
•2 or more client servers for up to 3 - 5 concurrent users each
•Roaming profiles, load balancing, etc.
Please refer to the sub-topics listed below.