Chapter 1 The Reactis License Manager
The Reactis License Manager facilitates the sharing of floating licenses for the various software applications of the Reactis product line. Floating licenses can be shared by different members of your organization. If your organization has purchased such licenses, then the Reactis License Manager should be installed on a server visible over the network to all users of the Reactis products. Users install the Reactis client software on their own computer and then check out and occupy a license from the Reactis License Manager when they wish to use the Reactis software.
1.1 Installing the Reactis License Manager
The steps for installing the Reactis License Manager are as follows:
1.2 Monitoring License Usage in Real-Time
Two options are available for communicating with the Reactis License Manager to observe license usage in real-time. First, the License tab of the Settings dialog in the main Reactis application displays the number of licenses served by the Reactis License Manager, the number currently in use, and information describing which users currently occupy licenses. This information may alternatively be obtained from the Reactis License Monitor utility, which is invoked by selecting the following from the Windows taskbar:
Start -> Programs -> Reactis License Manager V2019 -> License Monitor
1.3 Disconnecting Users from License Manager
When using the Reactis License Manager, it is possible to forcibly disconnect users from the License Manager. Disconnecting a user will free up the license occupied by that user. The user’s Reactis session will be terminated after a grace period of 15 minutes, allowing them to save any work in progress.
1.3.1 Setting up the License Manager to Allow Disconnecting Users
The Reactis License Manager will only allow disconnecting users if a password is defined. A user attempting to disconnect another user will be queried for the password before proceeding.
To define the password, do the following
This will create file reactisl.pwd in the Reactis License Manager installation directory. Removing that file will disable the functionality to disconnect users.
1.3.2 Disconnecting a User
To disconnect a user, either open the License tab of the Reactis Settings dialog or start the Reactis License Monitor as described in Section 1.2.
In the “License users” list on the bottom of the window, right-click on the user you wish to disconnect. This will bring up a menu containing a “Disconnect” entry. Select “Disconnect” and enter the password established as described in Section 1.3.1. This will disconnect the user.
1.3.3 Effect of Disconnecting a User
When a user is disconnected from the Reactis License Manager, they are presented with a window allowing a 15 minute grace period to save any work currently in process (see Figure 1.1). Clicking the “Retry” button in the window will allow the user to re-connect to the Reactis License Manager and continue using Reactis. After the grace period expires, Reactis will be blocked until a connection to the license manager can be restored.
1.4 License Manager Logging
The Reactis License Manager may be configured to log license usage to two different locations: the Windows Application Event Log and a log file.
1.4.1 Logging to the Windows Application Event Log
When run as a service, the Reactis License Manager currently logs
the following messages to the Windows Application Event Log.
The ’xxx.xxx.xxx.xxx’ placeholders represent IP addresses of clients requesting or releasing licenses. After a client was granted a license, the client will send a message back to the License Manager indicating the user currently running Reactis. This is indicated by the “User is” message in the log.
The “Lost connection” message indicates that the License Manager did not receive a heartbeat from a client for over 4 minutes. When this happens, the License Manager considers the connection to be broken and releases the license (indicated in a subsequent message).
The “Cannot listen on port N” message indicates that the License Manager was unable to accept incoming connections on port N (default is 3999). The most likely reason for this is that another application (possibly another instance of a Reactis License Manager) is already using that port. You must either terminate other applications using the port or contact Reactive Systems to obtain a new license file instructing the License Manager to use a different port.
The logging of the messages with ID 109 can be disabled by setting the following Windows registry key to 0:
Reactis License Manager V2019\Parameters\SystemLogLevel
You need to stop and restart the License Manager Service in order to make changes to this registry key become effective.
1.4.2 Logging to a File
The Reactis License Manager may be configured to record license usage
information to a comma separated value (CSV) file.
The log file is named
The CSV file will log all messages listed above except those with ID 100 and 101. Logging to the CSV file is disabled by default, but can be enabled by setting the following Windows registry key to 1:
Reactis License Manager V2019\Parameters\CsvLogLevel
The location of the CSV file is stored in the following Windows registry key and can be modified if you prefer a different location:
Reactis License Manager V2019\Parameters\CsvLogFile
You need to stop and restart the License Manager Service in order to make changes to these registry keys become effective.
Each line in the CSV log file consists of six columns as can be seen in the following example:
"01/25/06 11:27:34", "", "License Manager Started", 0, "", "n/a" "01/25/06 11:27:59", "192.168.1.107", "License granted", 1, "Reactis", "5555" "01/25/06 11:27:59", "192.168.1.107", "User: John Doe on XYZ", 1, "Reactis", "5555" "01/25/06 11:28:03", "192.168.1.107", "License released", 0, "Reactis", "5555"
The following lists the meaning for each of those columns:
The license manager can also produce a log file when run as an application when initiated from the command-line. When running as a service, the license manager reads the Windows Registry keys as described in Section 1.4.2 to determine whether logging is enabled and the location of the log file. When running as an application, those registry keys are NOT read. Instead, you can give a command-line argument to enable logging and specify the location of the log file.
For example, to run the license manager as an application, you would type the following commands:
This is equivalent to clicking the Start menu item:
where -c is followed by the path to the .csv file.
Note: When run as an application, the License Manager currently does not log the "License Manager Started" and "License Manager Terminated" messages but it does log all other messages as described in Section 1.4.1.