ISV Options File

The ISV options file lets you control which users should have access to the licenses, for example, only serve licenses to specific users or countries. You can also use the ISV options file to dedicate license pools for development or build servers. Options are provided to reserve licenses (RESERVE), to either allow (INCLUDE or INCLUDEALL) or disallow (EXCLUDE or EXCLUDEALL) license usage. Additionally, options are provided to create groups of users (GROUP) or hosts (HOST_GROUP), or IP addresses (INTERNET_GROUP), and to control the maximum number of licenses a user or group can check out (MAX).

For more information about ISV files please visit the ISV Options File chapter of the RLM Reference Manual, which is intended for license administrators at organizations using RLM licensed products, or for additional information you can see RLM Option File page too, which allows control over access to the status, reread, shutdown administration commands as well as control over the editing of options files.

The HighTec ISV options file has a set name which is "hightec-rt.opt". This file should be kept in the same directory as your license file. The opt file can be generated automatically through the RLM web interface (see further down the page) or created manually.

Create and edit ISV options files

The easiest way to create and edit the ISV options file is to do it via the RLM web interface.

  1. In a web browser, enter https://<host_name>:<port_number>

  2. Log in to the RLM web interface.

  3. Click the status icon.

  4. You will see a bar stating: "ISV servers". Under "OPTIONS", click the button called: "hightec-rt".

  5. You will now see a blank space called "Edit ISV Options". Fill in the preferred options according to the pattern stated above.

  6. Click Update Options.

  7. Restart your license server.

License pool settings with ISV options file

Here is an example of how to set up a license pool to only serve a specific group of users.

In the ISV options file, you need to:

  • Create a group of users (the users that should have access to the license), this can be based on IP addresses, user names, etc. For example:

    GROUP IT_users user1 user2
    Note: you need to name the users according to their identification

  • Set up the parameters of the access to the license, that is, the options for these users. For example:

    INCLUDE tricore-gcc GROUP IT_users id=20

    • The INCLUDE line simply indicates that only the users listed can access this license pool.

    • There are other options available apart from INCLUDE that can be found in the RLM manual.

    • The tag "id=nnn" is important, but the number is arbitrary.

  • Add the same id tag to the license file, prepending an underscore to it. For example:

    LICENSE hightec-rt tricore-gcc 2023.07 permanent 1 share=uh
    client_cache=300 id=20 client_cache=300 max_roam_count=0 start=07-mar-2023
    platforms="x64_l x86_l" contract=SENxxxxx replace options=ver=4.9.x

  • Adding this tag to the license file can be done without HighTec needing to verify the change.

  • If you want to remove these specifications you can delete the entries, or the whole ISV options file.

ISV Options File Advanced Example

Generic template for GROUPs and INCLUDEs

Template:

GROUP [group-name] [add users with space in between]
INCLUDE [toolchain-type] GROUP [group-name] id=[id-number-for-license-pool]

Notes:

  • for id field the id=10 for CI and id=20 for Developer is recommended

  • for group names we recommend the following Naming convention:

    • for CI : [type]_[stakeholder]

    • for Developer : [type]_[stakeholder]_[department]_[location]

CI example:

GROUP ci_xxx user1 user2
INCLUDE tricore-gcc GROUP ci_xxx id=10

for CI licenses, xxx stakeholder

Developer example:

GROUP dev_xxx_94xxx_got user1 user2
INCLUDE tricore-gcc GROUP dev_xxx_94yyy_got id=20

for Developer licenses, xxx stakeholder, 94yyy department and SITE:Gothenburg

Advanced CI license pool example

# CI, GLOBAL, WINDOWS license pool
# All stakeholder groups with respective accounts
GROUP ci_exx epxxx epsxxx
GROUP ci_bxx autoxxx
GROUP ci_vxx vdxx
INCLUDE tricore-gcc GROUP ci_exx id=10
INCLUDE tricore-gcc GROUP ci_bxx id=10
INCLUDE tricore-gcc GROUP ci_vxx id=10

Advanced developer license pool example

# Developer, GLOBAL, WINDOWS license pool
# All stakeholder groups with respective accounts
# EPS Stakeholder Groups - All Gothenburg.
GROUP dev_exx_97xxx abxxx acxxx cbxxx dkxxx jhxxx naxxx vgxxx
GROUP dev_exx_97xxx aaxxx axxx axxx asxxx bxxx ifxxx jxxx kbxxx vxxx wxxx
GROUP dev_exx_97xxx axxx anxxx cxxx dvixxx eexxx kxxx mxxx nxxx pxxx pbxxx pkxxx psxxx spxxx tsxxx
INCLUDE tricore-gcc GROUP dev_exx_97xxx id=20
INCLUDE tricore-gcc GROUP dev_exx_97xxx id=20
INCLUDE tricore-gcc GROUP dev_exx_97xxx id=20