Licensing Consoles and Web applications

This document describes licensing of the D2000 user consoles (D2000 HI, D2000 GrEditor, D2000 CNF, D2000 ODBC Driver, etc.).

The licensing is based on the principle of buying the necessary user consoles and the licensing model, which the most meets the requirements of an end-user.

D2000 System provides the following license models:

Named Device

This model is basically identical to the previous system of licensing. The license depends on the number of workstations, from which the users of D2000 HI consoles may log on to the System. This model is intended for applications where the group of workstations is unchanged or is changed rarely. It is not suitable in situations when the technology of remote access (e.g. Citrix, RDP, etc.) is used for access to the D2000 Server.

On the side of the server (D2000 Server), there is the list of consoles in the file ConsolesInfo.txt, which is in the installation directory of the D2000 System.
This is the example of the file contents:

 [CONSOLES]

 USERX_PC;13:04:00 03-09-2012
 USERY_PC;17:29:28 14-08-2012
 USERZ_PC;15:02:01 03-09-2012

This file is editable. After editing, the D2000 Server must be informed to refresh this file by the REFRESH_LICENCE  tell command.
A better way to modify the list of consoles is to use the module D2000 Application Manager.

Named User

The license depends on the number of users that are allowed to log on to the D2000 System. The multiple logins of one user or creating the users outside the license range is not permitted.

Concurrent User

The license depends on the number of users that are allowed to log on to the D2000 System in the given time. Multiple logins of one user are permitted. Each user login is counted separately.

Licensing the Thin clients (Web application)

The licensing of so-called thin clients (Web applications) means that the limited (defined) number of applications can be logged on to the System in the given time.

EDA Licensing

EDA enables two methods of licensing. The first one is explicit permission of "thick" EDA clients, without the use of an EDA server. Another method is to define the number of EDA servers that may run concurrently. When using this method, the usage of "thick" EDA clients is automatically enabled.

JAPI Licensing (D2Connector)

JAPI Licensing is defined by the maximum number of JAPI sessions that are logged in at the given time.