License Check Order

A license is checked:

At each startup of Foresight Analytics Platform.
At each repository connection.
At addressing the tool or functionality.

If on startup and repository login no necessary valid licenses are found, the message requesting product activation is displayed. To activate, contact the BI server administrator.

If on using a tool or functionality a valid license for the corresponding feature is not found, a license restriction message is displayed.

License Check Order on Using License Server

To start Foresight Analytics Platform and to connect to repository, use the AnalyticsPlatform basic feature. One repository connection requires a license for each feature and checks it once. At each separate connection the license for the required feature is checked again. In other words, each separate request is considered as a request from different users.

At system login, the client application sends user name in upper case to the license server. If domain/integrated domain authentication is used, the user name is sent taking domain into account. Sending of user name in the UPN format depends on the USEUPN attribute in the Metabases.xml file. A client application is a web application and user application developed based on Foresight Analytics Platform.

The request to use the functionality or tool is sent to the license server via the licensing service. The license server checks if there is a valid license for a corresponding feature. In case of approval, the license server sends the corresponding message to the client application and the functionality becomes available for use.

If a limitation on the number of simultaneously working users is set in the network license, the available number of users is reduced by one during the work with a tool or functionality. The number of features is restored when the functionality is no longer used, for example, on closing a tool.

Features of network license use with a limited number of simultaneously working users:

A license server can approve a client application to use several copies of the same tool or functionality, that is, the available number of features for the tool in use is reduced several times. For example, the same tool is opened in the web application in different sessions: reports are opened in different browsers.

The client application sends a message to the license server about checking in a tool or functionality. The number of features is increased by one in this case. For example, the tool is being closed, another tool or functionality is being used.
A license server approves a client application to use a tool or functionality if, at the moment of sending a request, the server has the available number of features.

When one exits the repository, the license is released and checked in to the license server. If the user did not exit the repository in the web application and closed the browser tab, the license will be released only after the BI server work timeout. The BI server informs the license server about its activity each minute. An additional work timeout, which is 10 minutes by default, is also set on the license server on license generation. The additional server work timeout is used in case of BI server connection loss, during which the request to close repository connection was not received.

The user session depends on BI server work timeout, and the license can be checked out even if the license server is inactive. Such sessions can be closed by means of DBMS.