Dundas BI licensing
- Managing licensing
- See also
This article explains how licensing works in Dundas BI and shows you how to administer licensing from within the application.
2.1. What is a Dundas BI license?
A Dundas BI license grants your organization a number of license seats, which enables users to log on and use the application. In addition, optional features such as SaaS / Multi-Tenancy only appear in the Dundas BI application if enabled through a license.
2.2. Cumulative nature of Dundas BI licenses
Dundas BI licenses are cumulative. For example, if your organization needs 5 more license seats, you can obtain a license from Dundas that adds 5 more users on top of what you already have. In other cases, a license may replace or invalidate a prior license; adding a retail license on top of the evaluation license that is included with the Dundas BI installer will invalidate the evaluation license.
2.3. Dundas BI instance
Dundas BI supports multi-server deployment out-of-the-box for load balancing purposes. In this scenario, multiple servers have Dundas BI installed but they each point to (or share) the same Dundas BI Application Database (App DB).
For licensing purposes, the entire ecosystem of servers and software referencing a single Dundas BI Application Database is referred to as a Dundas BI Instance. Dundas BI licensing is tied to such an instance and there may be a limit on the number of servers permitted to connect to the instance.
2.4. License kinds
The following kinds of licenses are available:
2.5. License format
A Dundas BI license is a block of XML text; there is no license "file" involved per se. Installation of a license can be done remotely from the Dundas BI Administration interface and simply involves copying and pasting the license XML text obtained from Dundas.
2.6. Core count
A Dundas BI license may specify a set number of allowed CPU cores. The core counting method is indicated in the license:
- Per-server – the sum of CPU cores present on the server running the application.
- Per-instance – the sum of CPU cores used by each of the servers running the application (for a load-balancing environment).
If there are more CPU cores available than indicated in the license, Dundas BI will only use the allowed number of cores.
A license seat allows users to log on to Dundas BI. Two license seat modes are available to support your organization's specific needs:
Reserved Seats (also known as Named Seats)
- Allows users to log on regardless of who else may be using the application.
- Ideal for users who need use the application frequently or for long periods of time.
- Seat types: Reserved Standard User, Reserved Power User, Developer.
- Dundas BI Developers always use a reserved seat.
Floating Seats (also known as Concurrent Seats)
- Floating license seats make it possible to support a large number of Dundas BI users.
- The key is that the floating users cannot be using the application all at the same time.
- The number of floating users logged on simultaneously cannot exceed a certain limit as determined by Dundas BI licensing.
- Seat types: Floating Standard User, Floating Power User.
To better understand the concept of floating seats, think of chairs at a table. If all of the chairs are taken, people standing will have to wait until someone gets out of a chair before they can sit down.
(Accounts set as an API account do not consume a seat, but can only be used for making API calls without using the UI or making a data retrieval call.)
Elasticity is a built-in feature of the Dundas BI licensing system that allows a user to temporarily exceed the floating license limits. This feature allows a user to still log on and continue working while giving the Dundas BI system administrator notice and an opportunity to review the organization's need for more Dundas BI license seats.
A Dundas BI retail license typically includes a fixed number of elastic hours for standard users and power users. For example, a standard user may be permitted to exceed the license limits by logging on for up to 5 hours in total per calendar quarter. Note that unused elastic hours are not carried over from one quarter to the next.
Besides elastic hours, there is also the concept of elastic seats which represents the number of concurrent users that are permitted to log on and use up elastic hours when all floating seats are occupied. In a Dundas BI license, there are two license fields, Floating Power User Elastic Seats and Floating Standard User Elastic Seats, which represent the maximum number of concurrent users that can be logged on and using elastic seats for power users and standard users, respectively.
3. Managing licensing
To manage licensing in Dundas BI, go to the main menu and click the Admin button. Then expand the Licensing section to see the available options.
3.1. Adding a Dundas BI license
Adding a Dundas BI license is as simple as copying and pasting the license XML text obtained from Dundas. See the article on managing licenses for details.
You may need to add a new license if you are upgrading an instance between major versions of Dundas BI.
3.2. Seat usage
Click Seat Usage to see the number and distribution of seats that are currently in use for this Dundas BI instance.
The Seat Usage screen shows a number of horizontal bar charts. If reserved license seats are in-use, click on the in-use bar to see the corresponding list of user accounts that are logged on. If floating seats are in-use, click on the in-use bar to see the corresponding list of logon sessions.
The maximum number of floating (concurrent) logon sessions reached in a given calendar month for each floating seat type (e.g., standard or power user) is recorded in a database view (vSessionUsageHistory) in the Dundas BI Application Database. You can use this information to monitor how close your organization is to reaching your floating license limits.
For example, in the figure below, the maximum number of floating logon sessions (for standard users or SeatKind = 0) reached in October 2015 was 19.
The values for the SeatKind column are defined in the LicenseSeatKind enumeration.
3.4. Configuring elasticity
There are a few configuration settings related to license elasticity. To view or modify these settings, expand the Setup section in the Admin screen and then click Config. Change the Category to Licensing and also click the Show Advanced Settings checkbox.
The Elasticity Activation Warning Enabled setting determines whether an email will be sent to the Dundas BI system administrator the first time a user starts using an elastic seat in any given elasticity period. The email will be sent a maximum of one time per calendar quarter and the email settings in Dundas BI must be configured properly for this to work.
The Elastic Hour Warning Threshold settings are used to send an email to the Dundas BI system administrator when a specific number of elastic hours are remaining. By default, this is set to zero hours which means the email will be sent when the hours have been exhausted. No warning email is sent if the threshold is set to -1.
3.5. SaaS / multi-tenancy
Dundas BI provides built-in support for SaaS (software-as-a-service) and multi-tenant scenarios. This is a feature that allows a single Dundas BI instance to serve multiple independent tenants. But note that this feature is an option which must be enabled through appropriate licensing.
Dundas BI system administrators can create and set up multiple tenants that are completely isolated from each other. System administrators can also assign seats and elastic hours on a per-tenant basis.
Additionally, each tenant can have their own tenant administrators, which have the ability to add and manage users, groups, and projects without having to involve the system administrators.
3.5.1. View seat allocation
To view the seat allocation for each tenant, go to the main menu and click Admin. Then expand the SaaS/Multi-tenancy section and click Tenants.
You can view the seat allocation summary for each tenant in the Seat Allocation column.
- If there is a problem with the licenses in your instance (e.g., all licenses have expired), the built-in administrator user will still be able to log on (with Viewer privileges) in order to correct the issue.
5. See also
- Upgrade an instance
- Seat types
- Managing licenses
- Configuration settings
- Administration overview
- Off the Charts: How Does Licensing Work?