
The current functions that are used by the Rhino family of products are:
“Rhino” – The function used by the production Rhino build for its core functions.
“RhinoSDK” – The function used by the SDK Rhino build for its core functions.
“default” – This is synonymous with “Rhino” on the production build and “RhinoSDK” on the SDK build. This is intended
to be used for services that disable accounting on the core function where those services must work on both the SDK and
production builds without recompilation or repackaging.
14.2 Alarms
Licensing alarms will typically be raised in the following situations:
• A license has expired.
• A license is due to expire in the next 7 days.
• License units are being processed for a currently unlicensed function.
• A license function is currently processing more accounted units than it is licensed for.
Once an alarm has been raised it is up to the system administrator to verify that it is still pertinent and to cancel it. Particular
note should be paid to the time the alarm was generated and in the case of an over capacity alarm it may be necessary to view
the audit logs to determine exactly when and how long the system was over capacity. Alarms may be cancelled through the
management console. Please note that a cancelled capacity alarm will be re-generated if a licensed function continues to run
over capacity.
14.2.1 License Validity
Services and resource adaptors will fail to activate if they require unlicensed functions. This applies to explicit activation (i.e.
via a management client) and implicit activation (i.e. on SLEE restart). There is one exception: if a node joins an existing
cluster that has an active service for which there is no valid license, the service will become active on that node.
In the production version of Rhino, services and resource adaptors that are already active will continue to successfully process
events for functions that are no longer licensed, such as when a license has expired.
For the SDK version of Rhino, services and resource adaptors that are already active will stop processing events for the core
“RhinoSDK” function if it becomes unlicensed, typically after a license has expired.
14.2.2 Limit Enforcement
For the production version of Rhino, the “hard limit” on a license is never enforced by the SLEE. Alarms will be generated
if event processing rate goes above the licensed limit and an audit of the audit log will show the amount of time spent over
licensed limit for each over-limit function.
For the SDK version of Rhino, the “hard limit” on the core “RhinoSDK” function will be enforced. That is, events bound for a
service that uses this function over the licensed limit will be dropped. If more than one service is interested in the same event
and one of those services is over limit then none of the services will receive the event. Alarms will be generated when events
are dropped. An audit of the audit log will show that events equal to (or just less than) the licensed limit were processed.
14.2.3 Statistics
Statistics are available through the standard Rhino SLEE statistics interfaces. ‘License Accounting’ is the name of the root
statistic, and statistics are available per function, with each function showing an “accountedInitialEvents” and “unaccountedIni-
tialEvents” value. Only “accountedInitialEvents” count towards licensed limits, “unaccountedInitialEvents” are recorded for
services and resource adaptors where accounted=”false” is configured for a licensed function.
Open Cloud Rhino 1.4.3 Administration Manual v1.1 86
Kommentare zu diesen Handbüchern