Managing Licenses

You can request license files for test and production systems from OPTIMAL SYSTEMS by e-mail or via the license service.. License files must be staged in yuuvis® RAD and activated.

Licenses are permanently assigned to a yuuvis® RAD installation by way of the cluster ID.

The properties of a license file can be viewed in yuuvis® RAD monitor using the following call:

http://<host-gateway>rest-ws/index.html?continue#PAGE:monitor/license

If the database is reinstalled, the cluster ID changes and a new license will be required.
Conversely, changes to the properties of the hardware environment do not have any effect on the cluster ID and do not require a new license.

License Expiration Date

License files contain an expiration date. Users are shown a corresponding message in yuuvis® RAD client one month before the license expires.

The Notify about system events operation can be used to activate the sending of an administrative e-mail 30 days prior to the license expiring.

Users can access yuuvis® RAD for three more days but cannot create or edit any objects after this date has passed.

The 'root' technical user can log in to yuuvis® RAD at any time and update the license, regardless of the expiration date.

The Notify about system events operation can also request a new license from the OPTIMAL SYSTEMS license service and, if a new one is available, deploy, check, and update it.

Licenses for Users

A distinction is made between two types of user licenses in license files: concurrent licenses and named licenses.

• Concurrent Licenses

  The number of concurrent licenses determines how many users can be logged in at the same time. If no concurrent license is available, a user cannot log in and is shown a message to this effect when logging in.

  The number of users currently logged in with a concurrent license and the available concurrent licenses can be viewed using the following call in yuuvis® RAD monitor:

  http://<host-gateway>/rest-ws/index.html#PAGE:monitor/sessions

  The number of logins that were rejected because no concurrent licenses were available can be viewed by opening the security log:

  http://<host-gateway>/rest-ws/service/monitor/seclog?event=ACCOUNT_USER_LOGIN_REJECTED_CONCURRENT_USER&offset=0&limit=-1

  There is no limit in terms of the number of concurrent licenses in the case of TEST licenses.

• Named Licenses

  The number of named licenses determines how many users can be assigned a named license to ensure they can always log in independent of concurrent licenses. Named licenses are assigned to individual users in the user administration.

  The 'root' technical user can log in to yuuvis® RAD at any time, regardless of the number of concurrent and named licenses and irrespective of the expiration date.

Licenses for Object Types

License files contain the maximum number of object types. If the schema contains more object types than is permitted, an error message appears when the project schema is checked in yuuvis® RAD designer. The license can be activated, but a project schema that is changed at a later time can only be staged if the number of object types has been reduced.

There is no limit in terms of the number of object types permitted in the case of TEST licenses.

License Service

OPTIMAL SYSTEMS provides a license service through which new licenses can be made available.

The license key and address of the license service must be specified in yuuvis® RAD management-studio: Main menu > System > Settings > Core service > Global > Server > License. You can request and receive a specific license key. The address of the license service is prepopulated. The license service must be accessible.

The license service can be queried via the Notify about system events operation or in yuuvis® RAD monitor via the following page: <host-gateway>rest-ws/index.html?continue#PAGE:monitor/license.

The following data is transferred when connecting to the license service:

Key	Description	Example
base.HostInfo	Host name, IP4 or IP6 address, primary MAC.	core-service-host.com,10.10.168.16,005056BDA710
base.AppVersion	Version	10.4.0
org.NamedUserCount	Number of named users	2
tps.CustomTypesNonAbstract	Number of abstract object types	23
tps.CustomTypes	Number of object types	26
tps.Groups	Number of object type groups	3
org.UserCount	Number of users	33
org.ObjectsCount	Number of organization objects – users and groups	45
crs.DBProdName	Database	Microsoft SQL Server
crs.DBType	Database type	MICROSOFT_SQL_SERVER_16
crs.DBProdVersion	Database version	16.00.1000
crs.JVMStart	JVM start time	2024-05-08T08:18:57.654Z