Exceed onDemand A Technical Whitepaper

Exceed onDemand Client
There are two ways to distribute Exceed onDemand Client to the user base:
> Exceed onDemand 5 — A Technical Whitepaper
1) distribute the wizard-driven, Windows-based installation program through the regular windows
deployment tools, or
2) distribute Exceed onDemand Client through web browsers with the help of Exceed onDemand
Deployment Wizard. Regardless of which deployment method is used, end users receive the same
Exceed onDemand Client.
For more information on deploying Exceed onDemand Client using Exceed onDemand Deployment
Tools, please refer to Section 8: “Web Deployment.”
Other Components
Exceed onDemand also comes with a collection of administrative and deployment tools that help
administrators manage the product:
> Exceed onDemand Deployment Wizard
> Exceed onDemand Server Manager
> Exceed onDemand Print Utilities
> Exceed onDemand Keyboard Editor
Most of these tools are Windows-based applications (with the exception of Exceed onDemand Print
Utilities which can also run on xNIX environments), and they are part of the Exceed onDemand Server
for Windows installation. Regardless of what platform Exceed onDemand Server is currently running
on, administrators would have to install Exceed onDemand Server for Windows on a Windows
platform should they wish to benefit from the additional tools. Exceed onDemand Server component
should be deselected during the installation. Thanks to Microsoft Windows Installer technology, it is
a simple and straightforward task to customize the installation.
Since Exceed onDemand Server can run on most common xNIX platforms, it is an added benefit
if the Server is installed on the same host where the X applications reside. By minimizing network
traffic and latency, this configuration can potentially improve overall performance.
In some other cases, administrators will favor the non-intrusive approach: Exceed onDemand Server
is installed on a separate machine, leaving the machines running the mission-critical applications
untouched. In this case, the host does not have to split resources, such as CPU cycles, bus bandwidth
and memory, between the mission-critical applications and Exceed onDemand Proxies. With more
resources available to the X applications on one machine and Exceed onDemand Proxies on another,
users may experience improvement in response time and performance.
25