
Chapter 14
Licensing
14.1 Introduction
This chapter explains how to use licenses and the effects licenses have on the running of the Rhino SLEE.
In order to activate services and resource adaptors, a valid license must be loaded into Rhino. At a minimum there should be
a valid license for the core functions (“default”) installed at all times. Further licenses that give access to additional resource
adaptors and services can also be installed.
Each license has the following properties;
• A unique serial identifier.
• A start date – the license is not valid until this date.
• An end date – the license is not valid after this date.
• A set of licenses that are superseded by this license.
• The licensed product functions.
• The licensed product versions.
• The licensed product capacities.
A license is considered valid if:
• The current date is after the license start date, but before the license end date.
• The list of license functions in that license contains the required function.
• The list of product versions contains the required version.
• The license is not superseded by another.
If multiple valid licenses for the same function are found then the largest licensed capacity is used.
When a service is activated, the Rhino SLEE checks the list of functions that this service requires against the list of installed
valid licenses. If all required functions are licensed then this service will activate. If one or more functions is unlicensed then
this service will not activate. The same behaviour occurs for resource adaptors.
85
Comentarios a estos manuales