Named User behavior from BI 4.2 SP04 based on different License
Index
- Introduction
- Definition of license types
- Possible license key combinations
The below link talks about Named and Concurrent users types:
https://blogs.sap.com/2013/01/30/bi-platform-licensing-basics-csbls-and-named-users/
- Named user can be created using Named User License (NUL) or Processor License.
- Concurrent user can be created using Concurrent License (CSBL) or Processor License
As per definition of Named user, it is meant for an individual user and hence credentials should not be shared across.
Problem:
But we did encounter some discrepancies wrt Named User usage.
Hence we introduced restriction on max number of logon sessions to 10 for each named user.
Concern:
Named User License was also used by organizations who were publishing content to general public. Ex, Government would want to publish a WebI document in their portals, which will be viewed by all the citizens.
In such a scenario, the restriction of 10 sessions would be a blocker and hence we need a way out.
Solution: Introduction of Public Document License type.
This license is an extension of Named User License (NUL), but having unlimited logon sessions for Named users.
Public Document License should be used only for Public systems.
Going forward, Named user can be created using one of the below license types
- Named User License (NUL)
- Processor License and
- Public Document License
Definition of different license types:
- Concurrent license – is restricted to number of sessions
- Processor license – is restricted to number of processors
- Named User license – is restricted to number of users created
Note: Number of logon session restricted to 10 for named user created using Named User License.
- Public license – is restricted to number of users created
Note: No restriction on number of sessions for named user created using Processor or Public license (behavior identical to legacy Named user)
Behavior of different license types combination in a cluster/standalone setup is detailed out below:
| Case | Currently in System | New License added | Result |
| 1 |
Named license So its limited to 10 sessions |
Named license | Allowed |
| 2 |
Named license So its limited to 10 sessions |
Public license | Not Allowed |
| 3 |
Named license So its limited to 10 sessions |
Concurrent license | Allowed |
| 4 |
Named license So its limited to 10 sessions |
Processor license | Not Allowed |
| 5 | Concurrent license | Concurrent license | Allowed |
| 6 | Concurrent license | Public license | Allowed |
| 7 | Concurrent license | Named license | Allowed |
| 8 | Concurrent license | Processor license | Allowed |
| 9 | Public license | Public license | Allowed |
| 10 | Public license | Named license | Not Allowed |
| 11 | Public license | Concurrent license | Allowed |
| 12 | Public license | Processor license | Allowed |
| 13 | Processor license | Processor license | Allowed |
| 14 | Processor license | Named license | Not Allowed |
| 15 | Processor license | Concurrent license | Allowed |
| 16 | Processor license | Public license | Allowed |
| 17 | Combination of Concurrent license + Named license | Public license | Not Allowed |
| 18 | Combination of Concurrent license + Public license | Named license | Not Allowed |
| 19 | Combination of Concurrent license + Named license | Processor license | Not Allowed |
| 20 | Combination of Concurrent license + Public license | Processor license | Allowed |
| 21 | No license | Public/Named/Concurrent/Processor | Allowed |
Is that mean there is different license key available to download for Public Document License?
Post authorYes, there is a new license key for Public Document License and the expectation is to use it only for Public systems (also known as Public internet). Such licenses should be used in a separate deployment from other license models.