Configuring ELC by Editing Configuration Files

From ELC
Jump to: navigation, search

Go Up to Configuring AppWave Enterprise License Center


ELC user lists, IP list and various properties can be also configured manually by editing appropriate configuration files that are in plain text format. Any plain text editor can be used.

To configure the User List File for Named User Licenses

The user list file controls users and which products they are licensed to use. For named user licenses, this file is called userlist.txt and is located in the <ELC install>\conf directory. Issuers are guaranteed a product license as long as their name is in the user list file and they are connected to the server.

This file also controls the offline setting. Offline settings allow client product use without connection to the licensing server. A client switches to offline mode automatically when the connection to the licensing server is lost and back to online mode automatically when connection is regained. Offline mode has a fixed duration (maximum of 30 days), which is set in userlist.txt. Offline mode shields networked users from transient problems with the network or the licensing server. It is also useful for laptop users since they may frequently disconnect from the network.

The user list file is first checked for validity. If a user is on the user list, but the IP address used is not allowed, the license is denied. The following error message is displayed:

License server does not accept requests from this IP address.

The entries in the user list file must be in one of these formats:

  • For suite products, such as RAD Studio, there is one identifier per suite, per user: jsmith, *, 100_1_5, 30
  • For individual products, such as Delphi, the format is slightly different: jsmith, *, 2021, 0, 30

In both examples, the offline mode is set to 30 days. This setting allows the user to run the client product without being connected to the licensing server. If the user is not connected to the server, the user can use the product for a maximum of 30 days from the last successful connection.

Critical: The identifier you enter into your userlist.txt file is in the readme.txt file. You MUST read the readme.txt file to find the values to enter.

To configure the User List File for Concurrent Licenses

The user list file controls users and which products they are licensed to use. For concurrent licenses, this file is called userlist-concurrent.txt and is located in the <ELC install>\conf directory. If the user list file is not present, or has no entries, the concurrent license is non-restrictive. A non-restrictive concurrent license allows the first person who accesses the license to use it. However, this type of license cannot be checked out for offline use.

In addition to restricting user access, the user list file also controls the check-out (or borrow) period for the license use offline, which is set as days:hours. The user is permitted to keep the license for up to the specified amount of time, even when not connected to the server. When the specified check-out time is over, the client product displays a warning and stops running. Users can manually check out (borrow) and check in (return) a concurrent license from the Help menu, as long as user list settings allow them to do so.

Product identifiers in the user list file are in the following formats:

  • Suite Products Identifier Format
    For suite products, such as RAD Studio, there is one identifier per suite. In this example, the entry allows the user jsmith to run one copy of RAD Studio that includes all RAD products:
    jsmith, *, 100_1, 1:23
  • Individual Products Identifier Format
    For individual products, there is one product identifier and one SKU identifier. For example, the following entry allows the user jsmith to run one copy of Delphi:
    jsmith, *, 2021, 0, 1:23

In both examples, the check-out period is set to one day, 23 hours.

Critical: The identifier you enter into your userlist-concurrent.txt file is in the readme.txt file. You MUST consult the readme.txt file to find the values to enter.

Configuring Concurrent Licenses using Wildcards

The following examples illustrate how you can configure ELC concurrent licenses using wildcards.

  1. All users can checkout any product license for 7 days.
    1. *,*,*,7
  2. All users can checkout product X licenses for 7 days
    1. *,*,X, 7
  3. All users can checkout any product license for 7 days, but User A can checkout any product license for 30 days.
    1. *,*,*,7
      userA,*,*,30
  4. All users can checkout any product license for 7 days, but User A can checkout product X license for 30 days.
    1. *,*,*,7
      userA,*,X,30
  5. All users can checkout product X license for 7 days, but User A can checkout product X license for 30 days.
    1. *,*,X, 7
      userA, *, X, 30
  6. No checkout capability whatsoever (no entries in the userlist file).
  7. User A can checkout any product license for 30 days, but nobody else can checkout any product license. However EVERYONE can use any product license online. This is equivalent to entry *,*,*,0.
    1. userA,*,*,30
  8. User A can checkout product X license for 30 days, but nobody else can checkout. However EVERYONE can use product X online. This is equivalent to entry *,*,X,0.
    1. userA, *, X, 30
  9. User A can checkout product X license for 30 days, but cannot checkout product Y license, he can use Y only online. User B can checkout product Y license for 30 days, but cannot checkout product X license, he can use X only online.
    1. userA, *, X, 30
      userB, *, Y, 30
  10. User A can checkout all products for 30 days, but User B can only checkout Y for 30 days.
    1. userA, *, *, 30
      userB, *, Y, 30
  11. Deny all users to any product except User A who can use any product only online
    1. *,*,*,-1
      userA,*,*,0
  12. Deny all users to any product except User A who can use product X only online
    1. *,*,*,-1
      userA,*,X,0
  13. Deny all users to use product X except User A who can use it only online
    1. *,*,X, -1
      userA, *, X, 0
  14. User A can checkout product X license for 7 days, and any other product license for 30 days.
    1. userA,*,*,30
      userA,*,X,7
  15. All users can checkout product X license for 7 days, but User A can checkout product X for 30 days (specific user setting won’t be overwritten by any user setting)
    1. userA,*,X,30
      *,*,X,7
  16. All users can checkout any product license for 7 days, but User A can checkout product X license for 30 days.
    1. userA,*,X,30
      *,*,*,7
  17. All users can checkout any product license for 7 days, but User A can checkout any product license for 30 days.
    1. The last setting overwrites previous setting for the same user.
      userA,*,*,30
      *,*,*,7
      i. User A can checkout product X license for 7 days.
      userA,*,X,30
      userA,*,X,7
      ii. User A can checkout any product license for 7 days.
      userA,*,*,30
      userA,*,*,7
      iii. User A can checkout any product license for 7 days.
      userA,*,Y,30
      userA,*,*,7

See Also

Personal tools
PREVIOUS VERSIONS