You can use
Borland License Server (BLS) or FLEXnet License Server with
Atlas Hub. This gives you a choice between using a license server and using the
Atlas Hub native licensing found in this and earlier releases.
Important: BLS should be added to the
Microsoft Windows firewall exceptions (on the BLS server machine) when BLS is started as a
Microsoft Windows service. Otherwise the
Atlas Hub will be unable to connect to the BLS.
Note:
- If you use a license server, users must use their network logon names as their
Atlas Hub user names.
- A single license server can handle licenses for multiple releases and for multiple product releases.
- FLEXnet License Server configuration files on Linux are case sensitive.
- When
Atlas Hub starts up, it checks for slips and stores information about them in memory. It does not recognize new slips until the next
restart.
- When a user logs in from a client application,
Atlas Hub tells the client application what features are available to its user based on the license assigned to that user.
- If the user is assigned a license from a slip, but that slip is no longer in the license folder,
Atlas Hub displays an error message. If the license type for that user is
Unassigned, the user is not logged on and
Atlas Hub returns an exception.
The administrator does the following to configure the license server: