- Used to manage access to licenses
- Allows access to licenses using as criteria: hostname and username
- The OPT file allows:
- Enable the use of licenses;
- Restrict the use of licenses;
- Reserve licenses;
- Restrict the number of licenses available
1. How to create OPT file
- Using a text editor (notepad, notepad++)
- Create the esss file with the .opt extension: esss.opt
- Save this file in the same directory where the Rocky license file is stored: C:\Program Files\ESSS\License Manager 1.4.1\bin\lmadmin\licenses, by default:
- When the OPT is correct and stored in the directory where the license is located, it is necessary to "reread" the license. Access http://localhost:8090/ > Vendor Daemon Configuration > Reread License Files
2. Recommendations for creating the OPT file
- Create user groups based on departments or projects to facilitate the management and assignment of licenses;
- Information such as hostnames and usernames are case-sensitive by default. To disable this, it is recommended to add GROUPCASEINSENSITIVE ON at the beginning of the OPT file;
- Comments can be included in the file, preceded by #;
- It is recommended to include detailed information in the file, through comments, to facilitate the management of the OPT. For example:
- Summary of features and corresponding licenses;
- List of users, informing the person's name for each login
The OPT file is created based on the installed license file. The license is a text file with the .lic extension that has the following structure:
When we refer to the feature throughout this text, it is the word that comes after INCREMENT, for example rocky_solver_professional, rocky_prepost_professional.
3. Keywords used in the creation of the OPT
3.1 GROUP
Used to define user groups
Syntax: GROUP <group name> <user1> <user2> …
Example: create group dep_rocky with users: user1, user2, e user3:
GROUP dep_rocky user1 user2 user3
3.2 HOST_GROUP
Used to define groups of computers, by hostname
Syntax: HOST_GROUP <group name> <pc1> <pc2>...
Example: create group dep_part with the following computers: host1, host2 e host3:
HOST_GROUP dep_part host1 host2 host3
3.3 INCLUDE
Allows access of a feature to a selected user or group. Only users on the INCLUDE list can use the feature.
Syntax: INCLUDE <feature> <TYPE> <nome>
Example: make Rocky Solver available to the user username1.
INCLUDE rocky_solver_professional USER username1
Example: make Rocky Prepost available to the user username2.
INCLUDE rocky_prepost_professional USER username2
3.4 EXCLUDE
Restricts a feature's access to a selected user or group
Syntax: EXCLUDE <feature> <TYPE> <nome>
Example: deny Rocky Solver access for user username1
EXCLUDE rocky_solver_professional USER username1
3.5 INCLUDEALL / EXCLUDEALL
Same functions as INCLUDE and EXCLUDE, but control access to all features.
Syntax: INCLUDEALLL <TYPE> <nome>
EXCLUDEALL <TYPE> <nome>
Example: make all the features available to the username1 user
INCLUDEALL USER username1
Exemplo: deny access to all features for the mechanical group.
EXCLUDEALL GROUP mechanical
3.6 Order of precedence:
- If there is only one EXCLUDE list for a feature, any user outside that list has access to the licensed feature;
- If there is only one INCLUDE list for a feature, only users on that list have access to the licensed feature;
- If there is no list, all users have access to the feature;
- EXCLUDE takes precedence over INCLUDE. If a user is on both lists, he will not have access to the license feature.
3.7 MAX
Defines the maximum number of features that can be requested by the group or user simultaneously.
Syntax: MAX <number of licenses> <feature> <TYPE> <name>
Example: limit dep_rocky group access to 5 Rocky Solver licenses
MAX 5 rocky_solver_professional GROUP dep_rocky
3.8 RESERVE
Reserves a certain amount of features for a group or user.
Syntax: RESERVE <number of licenses> <feature> <TYPE> <name>
Example: reserve 2 Rocky Solver licenses for dep_part group
RESERVE 2 rocky_solver_professional GROUP dep_part
3.9 Difference between MAX and RESERVE:
- With MAX, the maximum number of licenses that will be used is predetermined, but they will only be consumed when activated;
- With RESERVE, licenses are permanently separated for the selected group;
For example, consider that there are 3 Rocky Solver licenses on the server and the following OPT is used:
MAX 2 rocky_solver_professional GROUP gp1
RESERVE 1 rocky_solver_professional GROUP gp2
- The gp1 group can use up to 2 Rocky Solver licenses simultaneously, and no more, even if the 3rd license is available.
- The gp2 group will always have 1 Rocky Solver license available, and there is no usage limit. It is possible for this group to use all 3 licenses, for example if the other 2 licenses are available.
4. OPT example
As we mentioned at the beginning, the OPT is based on the features contained in the license file.
We will use as an example a license file below:
The OPT example below will be used to allow access to licenses only for machines contained in the Rocky group:
Comments
0 comments
Article is closed for comments.