Which Deployment Modes to Support?
The term ‘’deployment mode’ describes how licenses are delivered and activated—using the cloud-served mechanism or on-premises–based methods. This section describes the:
>The licensed application is deployed on-premises, on the end user's system.
> The license resides in the same system where the licensed application is installed.
>All licensing functionality is self-contained—the licensing library and license management functions are integrated into the licensed application. There is no dependency on an external RMS License Manager.
>License misuse is prevented by locking each license to a fingerprint (a unique system identification code) on the standalone system.
>Also known as floating or concurrent licensing. The licensed application (deployed on-premises, on the end user client machine) obtains a license from RMS License Manager. This model works similar to the client-server model.
>Multiple application instances share licenses from a central license pool managed by RMS License Manager.
> RMS License Manager keeps track of all licenses and handles requests from network users who want to run a licensed application. RMS License Manager grants licenses to client machines after verifying the relevant licensing terms and conditions, and denies requests when all licenses are in use.
>Usually, a limit is placed on the simultaneous number of allowed client sessions. This allows a limited number of license 'seats' to be shared across a large number of users within a local network.
>The client must be able to connect to the local network and to communicate with RMS License Manager.
>The license is typically locked to the fingerprint of RMS License Manager. Client locking can also be implemented, if required.
>Network licensing also supports extended capabilities, such as redundant servers (deploy multiple instances of a license server for fault tolerance), commuter licensing (temporarily check out licenses for remote use), group reservation (restrict a license for particular users, computers, or groups), and grace-period licensing (ensure continual access even during network outages).
>This type of licensing is applicable to both large and small enterprises that require centralized license management.
License leasing is an extension of the on-premises deployments (standalone and network, described above) with automatic license delivery and updates and usage collection.
In license leasing, a license that is valid up to a time in the future (such as a year) is not delivered completely in one go. Instead, license delivery is split into multiple, time-limited installments of equal durations (such as quarterly installments). These installments are then delivered and consumed sequentially. Successive installments let you update the license terms. For example, adding support for an additional number of users and providing access to new features. This behavior continues until the license validity elapses, as shown in the following example:
•The diagram on the left shows deployment of a non-leased license for the duration of a year.
•The diagram on the right shows deployment of a quarterly leased license. The successive installments allow you to include additional updates to the license terms.
>Since license distribution is managed from the cloud, you have more control over the licenses delivered in the field. You can reconfigure licenses near real time and perform remote entitlement activation, renewals, upgrades and downgrades without going through the manual and cumbersome processes involved in traditional methods, such as email.
>By providing software usage data, leased licenses provide the best of traditional on-premises licensing and contemporary usage data collection and reporting. Usage data can provide you with invaluable intelligence for informed business decision making, leading to better compliance and increased customer satisfaction. In parallel, your customers can also switch to consumption-based post-paid license models.
>Periodic cloud-connectivity is required to obtain license updates and synchronize usage data. For more details, see "Lease Mode" later in this section.