The
...
The Settings page in the LM-X License Server Web UI lets you change the LM-X license server configuration settings as needed.
General usage and details about each configuration setting area are described below.
...
The License Server Network panel lets you configure settings for network bindings and connections.
Settings in the License Server Network panel include the following:
...
Setting
...
Description
...
TCP listen port
The TCP port number the license server will listen on.
- TCP port is used for data traffic protocol. The default TCP port is 6200.
- UDP port is used for automatic server discovery protocol. The UDP port is fixed to 6200 and cannot be changed.
, including the TCP listen port and TCP bind IPv4 and PIv6 addresses.
Anchor webserver webserver
...
TCP bind IPv4 address
TCP bind IPv6 address
...
Limit which networks the license server allows for client connections.
When this setting is specified, the license server will only accept clients that connect from a network that uses the specified IP addresses. You can specify only one address for each IP version (one for IPV4 and one for IPV6).
This setting is useful when the license server is connected to more than one network (has more than one IP address) and you want to limit allowed connections based on which network the client is on.
When this setting is unspecified, the license server accepts clients from all available networks.
Web Server settings
You must enable the web server to configure web server settings. Web server configuration includes settings for the web client users, port, SSL certificate file, and private key file.
...
The Remote API Access panel lets you set the password used for remotely managing the license server using the admin API.
Pay Per Use
You must enable Pay Per Use to configure Pay Per Use, including database and anonymization settings.
...
To add an embedded license, click “Add License” in the Embedded licenses area. This opens a dialog for defining the license details, including the ability to upload a license file or paste license file text from the clipboard. After entering the license information, click Save to add the license.
*****old config page start – TO BE REMOVED*****
The vendor may supply a license server configuration file, named lmx-serv.cfg by default. This configuration file is an ASCII text file, which can be opened and modified using any text editor. You may replace the existing information in the configuration file as needed.
For example, assume we are using a floating license. This type of license allows any number of users to have the software installed, but only a certain number of users to use the software simultaneously. When all allotted licenses are in use, other users must wait until a license becomes available to use the software. If you want to use software licenses most efficiently and implement fair/desired distribution of licenses, then as an administrator of the LM-X server, you may set the following options in the LM-X License Server configuration file:
...
Limitations. You can limit the number of licenses that can be used by individual users or groups. Limitations can be done by a set of rules. In particular, limiting of users is done by a first match rule, so if a user belongs to more than one group specified in restrictions, the first restriction will apply to that user.
The configuration file includes instructions for using each setting in the file, which may include the following, depending on the options provided by your vendor. Some of the configuration settings can also be specified using the web-based UI, as described in Administration.
...
Syntax
...
Description
...
Examples
...
TCP_LISTEN_PORT = port number
...
The TCP port number the license server will listen on.
- TCP port is used for data traffic protocol. The default TCP port is 6200.
- UDP port is used for automatic server discovery protocol. The UDP port is fixed to 6200 and cannot be changed. See http://www.iana.org/assignments/port-numbers for more information.
...
TCP_LISTEN_PORT = 6200
...
TCP_BIND_ADDRESS = IP_address_1 IP_address_2
...
TCP_BIND_ADDRESS = 192.168.21.321 8000:8000:8000:8000:abcd:1234:12df:fd54
...
- HAL_SERVER1 is your master server, which allows both CHECKOUT and BORROW. HAL_SERVER1 should be your most powerful server.
- HAL_SERVER2 is your first slave server, which allows CHECKOUT but denies BORROW in the event that your master server goes down. HAL_SERVER2 should be your second most powerful server.
- HAL_SERVER3 is part of your configuration to ensure that everything works as expected, and does not allow any CHECKOUT or BORROW requests. HAL_SERVER3 should be your least powerful server.
Important: The HAL_SERVER list must be identical on all your servers for HAL to function properly.
...
HAL_SERVER1 = 6200@server1
HAL_SERVER2 = 6200@server2
HAL_SERVER3 = 6200@server3
...
LOG_FILE = path
...
LOG_FILE = c:\program files\lmx-server.log
LOG_FILE = /home/user1/lmx-serv.log
...
LOG_FORMAT= NORMAL
LOG_FORMAT=EXTENDED
...
LOG_EXCLUDE = message1, message2, etc.
...
Exclude messages from the log. The following messages can be excluded: CHECKOUT, CHECKIN, STATUS, BORROW, BORROW_RETURN, REMOVE_USER, REMOTE_RESTART and/or REMOTE_SHUTDOWN.
...
LOG_EXCLUDE = CHECKOUT, CHECKIN, STATUS
...
LOGFILE_ROTATE_INTERVAL = rotation_interval
...
LOGFILE_ROTATE_INTERVAL = day
...
MIN_USER_REMOVE_TIME = time in seconds
...
MIN_USER_REMOVE_TIME = 120
...
LICENSE_PATH = path
...
LICENSE_PATH = c:\
LICENSE_PATH = d:\server
LICENSE_PATH = d:\server\network.lic
LICENSE_PATH = c:\extra_file.lic
LICENSE_PATH = /home/user1/floating_license.lic
LICENSE_PATH = /home/user1/floating_license2.lic
...
USAGE_DATABASE = database path
...
Pay-per-use usage database (used for billing purposes). See Pay Per Use feature for EXTENDED information, including database format and an example of data printout.
...
USAGE_DATABASE = d:\server\usage.db
USAGE_DATABASE = /home/user1/usage.db
...
USAGE_LEVEL= detail level
...
Specify pay-per-use detail level.
- STANDARD includes basic usage information.
- EXTENDED includes user information in addition to the basic usage information.
...
USAGE_LEVEL = STANDARD
...
USAGE_WRITE_INTERVAL= number of actions
...
Specify the number of pay-per-use actions (checkouts, checkins, etc.) after which pay-per-use records will be written to the pay-per-use database file. The default setting is 1000.
...
USAGE_WRITE_INTERVAL = 1000
...
REMOTE_ACCESS_PASSWORD = password
...
REMOTE_ACCESS_PASSWORD = MyPassword123
...
FAST_QUEUE = feature1, feature2, etc.
or
FAST_QUEUE = ALL
...
FAST_QUEUE = f2, d5, app2
...
- Rules are attempted to be matched in the order they are written.
- If no rule matches the specific client, then that client is allowed.
...
Allow/deny specific clients from borrowing licenses.
...
LIMIT_USER_f2_5 = harry joe sam
LIMIT_IPADDR_f3_3 = 192.168.2.* 192.168.4.*
...
RESERVE_USER_f2_5 = harry joe sam
RESERVE_IPADDR_f3_3 = 192.168.2.* 192.168.4.*
...
BORROW_LIMIT_COUNT_ALL = limit count
BORROW_LIMIT_COUNT_feature name = limit count
IGNORE_BORROW_LIMIT_COUNT_USER_feature name = one or more users
IGNORE_BORROW_LIMIT_COUNT_HOST_feature name = one or more hosts
IGNORE_BORROW_LIMIT_COUNT_IPADDR_feature name = one or more IP addresses
Note: You can use IGNORE_BORROW_LIMIT_* flag to whitelist small and specific predicates blacklisted by broader BORROW_LIMIT_* predicate.
...
Limit/Do not limit the number of licenses that can be borrowed to prevent all licenses from being borrowed at the same time.
...
BORROW_LIMIT_COUNT_f2 = 1
BORROW_LIMIT_COUNT_ABCDEF = 5
The following example will allow the user ADMIN, and deny host and IP addresses on the list from borrowing more than 100 features.
BORROW_LIMIT_COUNT_F1 = 100
IGNORE_BORROW_LIMIT_COUNT_USER_F1 = admin
IGNORE_BORROW_LIMIT_COUNT_HOST_F1 = server
IGNORE_BORROW_LIMIT_COUNT_IPADDR_F1 = 192.168.1.*
...
BORROW_LIMIT_HOURS_ALL = limit hours
BORROW_LIMIT_HOURS_feature name = limit hours
IGNORE_BORROW_LIMIT_HOURS_USER_feature name = one or more users
IGNORE_BORROW_LIMIT_HOURS_HOST_feature name = one or more hosts
IGNORE_BORROW_LIMIT_HOURS_IPADDR_feature name = one or more IP addresses
Note: You can use IGNORE_BORROW_LIMIT_* flag to whitelist small and specific predicates blacklisted by broader BORROW_LIMIT_* predicate.
...
the
...
...
The following example will allow the specific users, and deny host and IP addresses on the list from borrowing any feature. Everyone else will be allowed.
BORROW_LIMIT_HOURS_f2 = 1
BORROW_LIMIT_HOURS_ABCDEF = 5
The following example will allow the user admin, and deny host and IP addresses on the list from borrowing more than 100 features.
BORROW_LIMIT_HOURS_F1 = 10
IGNORE_BORROW_LIMIT_HOURS_USER_F1 = admin
IGNORE_BORROW_LIMIT_HOURS_HOST_F1 = server
IGNORE_BORROW_LIMIT_HOURS_IPADDR_F1 = 192.168.1.*
...
FEATURE featurename
{
feature settings
}
...
license
...
_START_LICENSE_
FEATURE F1
{
VENDOR = XYZ
}
_END_LICENSE_
...
GROUP_name = member1 member2
...
.
...
You can create groups that contain users, host names and IP addresses. Groups can contain any other group, and there is no limit on the number of members that can be included in a group.
The names of groups and group members are case-insensitive.
...
The following example creates a group named "hr" with one member, "anna," and another group, "employees," which contains three individual users (joe, mary, and sam), plus includes the group "hr" as a sub-group.
GROUP_hr = anna
GROUP_employees = joe mary sam hr
After creating groups, you can apply permissions, reservations, and limitations described above to those groups in the same way you would individual users; for example:
DENY_USER_f1 = employees
RESERVE_USER_f2_2 = employees
LIMIT_USER_f3_2 = hr
...
DENIAL_STORE_PERIOD = time_in_seconds
...
Specify how long the license server will keep denial information, in seconds.
- Valid values are between one minute and one year, expressed in seconds.
- The value is numeric only; do not use commas or periods in the entered value.
- The default duration is one day (86400 seconds).
The following example sets the denial storage period to 1 day:
...