Exceed onDemand A Technical Whitepaper

More documents

Recommendations

Info

Exceed onDemand 5 — A Technical Whitepaper Connections As mentioned earlier, there can only be one Exceed onDemand Cluster Manager per Cluster. However, a physical copy of Exceed onDemand Cluster Manager comes with every installation of Exceed onDemand Server. Therefore, before an Exceed onDemand Server can join an existing Cluster to become a Node, the Exceed onDemand Cluster Manager residing on that Server has to be disabled using Exceed onDemand Server Manager. The only instance of Exceed onDemand Cluster Manager in a cluster will directly communicate with the X Proxy Manager on each node over the Cluster Manager port, which is 5500 by default. Users will interact with the Cluster Manager node to launch or configure a session. All connection requests are handled by Cluster Manager. The incoming requests are processed by Exceed onDemand Cluster Manager, and the work load is distributed to the node which has the smallest load in order to promote load balancing. Data Storage Data Store is the location where configuration and connection profiles are stored. Several rules were implemented to protect data consistency and promote efficiency. The first and foremost rule is access restriction. Only the Cluster Manager has the privilege to communicate, access and write to the Data Store. Requests related to accessing or modifying configuration files, coming from either Exceed onDemand Client or X Proxy Managers, are routed to the Cluster Manager for processing. The second rule is one version of truth. There is one and only one Data Store in each Exceed onDemand Server. When multiple Exceed onDemand Servers group together to form a Cluster, there is only one Cluster Manager survives. The result is that the Data Store that was originally attached to the surviving Cluster Manager is kept alive. License In many ways, License information can be treated as another form of configuration data that the Cluster Manager manages. Again, only Cluster Manager is allowed to deposit in, or withdraw from, the License pool. When an Exceed onDemand Server joins a Cluster, the administrators are required to manually transfer the license from the newly added node to the license pool by re-entering the Activation Key in the Exceed onDemand Server Manager. 14
Types of Connectivity > Exceed onDemand 5 — A Technical Whitepaper Typically, X applications communicate with X Display Servers to display output and receive input. In the case of Exceed onDemand, X applications communicate with Exceed onDemand Proxy via the X protocol. In turn, Exceed onDemand Proxy communicates with Exceed onDemand Client via Thin X Protocol (TXP). Exceed onDemand offers a number of startup modes, which enable two types of connectivity: Direct Client-server Connectivity: Exceed onDemand Client connects directly to X applications that reside on the same physical machine as Exceed onDemand Server. Figure 3 — Connects directly to X applications on Exceed onDemand Server Gateway Server Connectivity: X Applications Exceed onDemand Server Thin X Protocol Traffic Thin X Protocol Traffic Exceed onDemand Client Exceed onDemand Client Exceed onDemand Client Exceed onDemand Server is not required to be installed on every machine on which X applications reside. Exceed onDemand Server can act as a gateway between Exceed onDemand Client and X applications running on different machines. 15
Page 1: Transforming Information into Intel
Page 4 and 5: Exceed onDemand 5 — A Technical W
Page 62: Server > Desktop Consolidation > X

Exceed onDemand A Technical Whitepaper

Create successful ePaper yourself

Delete template?

Save as template?