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:

A message requiring product activation is displayed in the web application. To activate, contact the BI server administrator.
In the desktop application, the Information dialog box opens displaying license search results.

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

TIP. In the desktop application one can view the features, for which there are valid licenses, in the About window. To open the window, select the Help > About item in the object navigator's main menu. Viewing features is available if Foresight Analytics Platform was activated via RMS without installation of licensing service.

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.

The request to use a tool or functionality is sent to the license server. The license server checks if there is a valid license for a corresponding feature. If the request is approved by the license server, an appropriate message is sent to the client application, and functionality becomes available for use. A client application is the web application, desktop application, and a custom application of Foresight Analytics Platform.

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. Examples:

In the web application the same tool is opened in different connections: reports are opened in different browsers.
In the desktop application, several tabs with repositories are opened and each repository has same tools opened.

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. Examples of checking in a tool or functionality: the tool is closed, the system opens another tool or functionality.
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 or disconnects from it, 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.