Understanding Licensing

Licenses determine how many users can access Atlas Hub. Users can have either named user or concurrent licenses. A named user license can be used only by the user who has been assigned that license. For example, if you have 5 named user licenses, the 5 users who are assigned the named user licenses are guaranteed access to the Atlas Hub. No one else can use their licenses.

A concurrent license can be used by any user who does not have a named user license. For example, users without named user licenses receive concurrent licenses on a first-come, first-served basis. After all the concurrent licenses are in use, users attempting to log on are notified that there are no more licenses available at this time. They can try again later.

You can add as many users as you choose, but access is granted only to users with named user licenses or to users who receive concurrent licenses as they log on.

Tip: You can import user information from Active Directory or OpenLDAP and assign users to license types or license server slips using LDAP QuickStart Manager. Refer to the LDAP QuickStart Manager Administrator Guide for more information.

The Server Administrator is automatically assigned a named user license which cannot be removed. This is a “free” license that is not counted against the number of named user licenses you have available.

Note: The Server Administrator should not have a password that is verified by a directory service because, if you change the service, the administrator will be locked out.

Atlas Hub can be licensed in either of two ways:

  • Atlas Hub licensing, also referred to as native licensing, which is internal to the product.
  • License Server licensing (using either BLS or FLEXnet Server).

If you have Atlas Hub native named user licenses, you must assign them to specific users in the User Manager dialog box. Everyone else is assumed to have a concurrent license. See the StarTeam Server online help for details.

If you have Borland License Sever (BLS) or FLEXnet License Server, users must be assigned to the correct slip in the User Manager dialog box, regardless of their named or concurrent user status. An additional status, Unassigned, may be used instead of a slip.