Exceed onDemand A Technical Whitepaper
Exceed onDemand A Technical Whitepaper
Exceed onDemand A Technical Whitepaper
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Exceed</strong> <strong>onDemand</strong> 5 — A <strong>Technical</strong> <strong>Whitepaper</strong><br />
Connections<br />
As mentioned earlier, there can only be one <strong>Exceed</strong> <strong>onDemand</strong> Cluster Manager per Cluster.<br />
However, a physical copy of <strong>Exceed</strong> <strong>onDemand</strong> Cluster Manager comes with every installation of<br />
<strong>Exceed</strong> <strong>onDemand</strong> Server. Therefore, before an <strong>Exceed</strong> <strong>onDemand</strong> Server can join an existing Cluster<br />
to become a Node, the <strong>Exceed</strong> <strong>onDemand</strong> Cluster Manager residing on that Server has to be disabled<br />
using <strong>Exceed</strong> <strong>onDemand</strong> Server Manager. The only instance of <strong>Exceed</strong> <strong>onDemand</strong> Cluster Manager<br />
in a cluster will directly communicate with the X Proxy Manager on each node over the Cluster<br />
Manager port, which is 5500 by default.<br />
Users will interact with the Cluster Manager node to launch or configure a session. All connection<br />
requests are handled by Cluster Manager. The incoming requests are processed by <strong>Exceed</strong> <strong>onDemand</strong><br />
Cluster Manager, and the work load is distributed to the node which has the smallest load in order to<br />
promote load balancing.<br />
Data Storage<br />
Data Store is the location where configuration and connection profiles are stored. Several rules were<br />
implemented to protect data consistency and promote efficiency.<br />
The first and foremost rule is access restriction. Only the Cluster Manager has the privilege to<br />
communicate, access and write to the Data Store. Requests related to accessing or modifying<br />
configuration files, coming from either <strong>Exceed</strong> <strong>onDemand</strong> Client or X Proxy Managers, are<br />
routed to the Cluster Manager for processing.<br />
The second rule is one version of truth. There is one and only one Data Store in each <strong>Exceed</strong> <strong>onDemand</strong><br />
Server. When multiple <strong>Exceed</strong> <strong>onDemand</strong> Servers group together to form a Cluster, there is only one<br />
Cluster Manager survives. The result is that the Data Store that was originally attached to the surviving<br />
Cluster Manager is kept alive.<br />
License<br />
In many ways, License information can be treated as another form of configuration data that the<br />
Cluster Manager manages. Again, only Cluster Manager is allowed to deposit in, or withdraw from,<br />
the License pool.<br />
When an <strong>Exceed</strong> <strong>onDemand</strong> Server joins a Cluster, the administrators are required to manually<br />
transfer the license from the newly added node to the license pool by re-entering the Activation<br />
Key in the <strong>Exceed</strong> <strong>onDemand</strong> Server Manager.<br />
14
Change language