login Register forgot password or username?
Search:         
Cradle from 3SL, the complete Model Based Systems Engineering Toolsuite, specialising in requirements management, requirements capture, model based systems engineering and for systems engineering software, support and consultancy, the logical choice: Cradle from 3SL.

March 2010 [Cradle 6.2]

Named User Licences

3SL is pleased to announce that our new Cradle release, Cradle-6.2, introduces a new type of concurrent licensing into Cradle, called named user licensing.

Previously, all Cradle licences were concurrent user and completely unlocked. This meant that any user could access any Cradle licence (subject to the Module Access Rights that may had been set up in the user’s Cradle user profile) from any computer that could connect to the Cradle Database Server (CDS).

The new named user licensing mechanism introduces a restriction that the licence is locked to a specific Windows or UNIX/Linux username. The licences are still accessible from any computer that can access the CDS. Named user licences are effectively an alternative to the read-write connection licences.

This mechanism allows customers to purchase Cradle modules that are locked to one or more specific users. So in Cradle-6.2 you will be able to purchase the existing concurrent user licences of the Cradle modules:

  • Cradle-PDM, product data management
  • Cradle-REQ, requirements management
  • Cradle-SYS, system modelling
  • Cradle-PERF, performance assessment
  • Cradle-SWE, software engineering
  • Cradle-WEBP, web publisher
  • Cradle-MET, metrics
  • Cradle-DOC, document generation

and you will also be able to purchase named user licences for these modules.

Named user licences are cheaper than concurrent user licences! Contact 3SL for more details by clicking here.

The details of the new named user licensing mechanism are:

  1. A named user licence is a licence that is locked to a specific UNIX or Linux or Windows username
  2. Named user and concurrent user licences can be combined in the same Cradle system
  3. The named users’ usernames will be encoded into a named_users file that will be sent by 3SL by e-mail. The file contains the Cradle version number, the Host ID (used by the CDS) and the usernames, and is encrypted. The named_users file will be held on the Cradle installation on the server in UNIX/Linux systems as the file:
  4. $CRADLEHOME/admin/named_users
  5. and on Windows systems it will be the file:
  6. %CRADLEHOME%\admin\named_users
  7. The named_users file will be installed manually by the system administrator into the above directory. Until the named_users file is installed in this way, named user licences will not be available.
  8. A user whose UNIX, Linux or Windows username (as appropriate) appears in the named_users file will consume a named user licence when he/she logs-in to Cradle as a read-write user. A named user will never use a RW connection licence, even if such licences are available when he/she logs-in. Similarly, a user whose UNIX, Linux or Windows username (as appropriate) does not appear in the named_users file will consume a RW licence when he/she logs into Cradle as a read-write user and will never use a named user licence.
  9. Named user licensing WILL NOT be available for web-UIs accessed by Cradle-WEBA licences, they only apply to non-web-UIs (such as WorkBench) and to utilities (such as c_io)
  10. A user who is named in the named_users file will consume one named user licence each time that he/she logs in to Cradle. So if multiple named user licences are available, then a named user who logs-in more than once will consume multiple named user licences.
  11. A company can change the set of named users free of charge once per maintenance period or whenever they purchase new named user licences. Any other changes to the named user file will be charged.