Exceed onDemand A Technical Whitepaper
Exceed onDemand A Technical Whitepaper
Exceed onDemand A Technical Whitepaper
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Exceed</strong> <strong>onDemand</strong> 5 — A <strong>Technical</strong> <strong>Whitepaper</strong><br />
> Manage Activation Keys<br />
> Restart Cluster Manager<br />
> View Cluster Manager Log<br />
All tasks, except Setting Cluster Manager Password, apply to both Standalone and Cluster configured<br />
<strong>Exceed</strong> <strong>onDemand</strong> Server. The explanation and usage of most of the tasks are well documented in the<br />
Help file and manual. However, there are a couple of points that administrators should take note of.<br />
There are two ways to authenticate a user, Native and PAM. The Native authentication type allows<br />
<strong>Exceed</strong> <strong>onDemand</strong> Server to authenticate the users; more specifically, the host on which the Cluster<br />
Manager Node resides will handle the authentication requests. Alternatively, administrators can<br />
select PAM (Pluggable Authentication Modules) as the authentication type. The PAM option is only<br />
available if the Cluster Manager Node resides on Sun Solaris or Linux, as PAM has been widely<br />
adopted on those platforms. In this case, <strong>Exceed</strong> <strong>onDemand</strong> Client credentials will be passed to the<br />
PAM module for verification, but administrators are required to configure PAM to include <strong>Exceed</strong><br />
<strong>onDemand</strong> services and specify an associated PAM module. If configured properly, <strong>Exceed</strong> <strong>onDemand</strong><br />
Client credentials can be authenticated by LDAP Server, RSA Authentication Manager, or any other<br />
authentication/directory services that support PAM.<br />
Figure 21 — Manage the Cluster in the Cluster Settings dialog<br />
42
Change language