
14.2.4 Management Interface
These are performed via the Web Console and the Command Console. A description of managing a license using the Command
Console is given here.
Installed Licenses
An overall view of which licenses are currently installed in Rhino can be displayed by using the listLicenses command:
[Rhino@localhost (#7)] listLicenses
Installed licenses:
[LicenseInfo serial=107baa31c0e,validFrom=Wed Nov 23 14:00:50 NZDT 2005,
validUntil=Fri Dec 02 14:00:50 NZDT 2005,capacity=400,hardLimited=false,
valid=false,functions=[Rhino],versions=[Development],supersedes=[]]
[LicenseInfo serial=10749de74b0,validFrom=Tue Nov 01 16:28:34 NZDT 2005,
validUntil=Mon Jan 30 16:28:34 NZDT 2006,capacity=450,hardLimited=false,
valid=true,functions=[Rhino,Rhino-IN-SIS],versions=[Development,Development],
supersedes=[]]
Total: 2
Here, there are two licenses installed:
107baa31c0e
and
10749de74b0
. The former enables one function: [Rhino], and the
second enables two functions: [Rhino,Rhino-IN-SIS]. Both of these licenses are development licenses.
The command
getLicensedCapacity
can be used to determine how much throughput the Rhino cluster has:
[Rhino@localhost (#9)] getlicensedcapacity Rhino Development
Licensed capacity for function ’Rhino’ and version ’Development’: 450
Installing Licenses
To install a license, use the
installLicense
command. This command takes a URL as an argument. License files must be on
the local filesystem of the host where the node is running:
[Rhino@localhost (#12)] installLicense file:/home/user/rhino/rhino.license
Installing license from file:/home/user/rhino/rhino.license
Uninstalling Licenses
In the same way, licenses can be removed by using the
uninstallLicense
command:
[Rhino@localhost (#15)] uninstalllicense 105563b8895
Uninstalling license with serial ID: 105563b8895
14.2.5 Audit Logs
Rhino SLEE generates two copies of the same audit log. One is unencrypted and can be used by the Rhino SLEE system
administrator to perform a self-audit. The encrypted log contains an exact duplicate of the information in the unencrypted log.
The encrypted log may be requested by Open Cloud in order to perform a license audit. Audit logs are subject to “rollover” just
like any other rolling log appender log. Therefore it may be necessary to concatenate a number of logs in order to get the full
audit log for a particular period. Older logs are named audit.log.0, audit.log.1, etc.
The audit log format can be found in Appendix E.
Open Cloud Rhino 1.4.3 Administration Manual v1.1 87
Comentários a estes Manuais