How licensing works
How licensing worksThis section discusses how licensing works. Basic License Server installation and setup is straightforward, and is covered in Installing Klocwork. Klocwork issues build licenses, user licenses and, continuous integration licenses. Build licenseWhat tools consume a build license? How the build license works
User licenseWhat tools consume a user license?
How the user license works Klocwork Desktop tools check out one user license for each unique user ID, where the user ID is the name used to log in to the operating system (OS) (e.g. jsmith or 'John Smith'). When using Klocwork Desktop or the Klocwork plug-in for Visual Studio or Eclipse, be sure to use the same user ID you used to log in to your operating system. If you use a different user name to log in to either of these tools than was used to log in to your OS, an extra license will be consumed. If you have different user IDs when you log in to different operating systems, one license will be consumed for each (For example, Windows login: 'John Smith', Linux login: jsmith – a total of two licenses will be consumed). Once a license is checked out by a user, the rest of the user tools listed above are reserved for them. For example, you can use any number of these tools as one occurrence of a user license, as long as you log in with the same user ID. Example 1: LDAP or Single sign-on If you have LDAP or Single sign-on configured and you attempt to log in to both a Windows and a Linux machine where the user credentials are different, two licenses are consumed. For example, a user, John Smith, logs into Windows with full name ('John Smith'), and logs into his Linux machine which uses a short name like 'jsmith'. In this case, if John Smith uses Klocwork from Windows and Linux, two licenses are consumed. Example 2: Alternate access methods If you use an alternate access method such as NIS or Basic, a license is checked out for each user that logs into Klocwork or Code Review. When logging in, be sure to use the same login credentials that is used when running the command line tools. If you do not, an extra license may be consumed. Continuous Integration licenseWhat tools consume a Continuous Integration license?
How the continuous integration license works A continuous integration license is checked out when:
One continuous integration license is checked out for each unique host that the above tools are run on. For TeamCity, a license is required for each agent and for Jenkins, a license is required for each slave. The license is then reserved for the host it was checked out on. Definitions: Time-out, linger, fixed and individualKlocwork offers build, continuous integration and user licenses. Build licenses are used to run the Klocwork integration build analysis on a build server, and so build licenses are always node-locked to a host name, or "fixed". A fixed build license has a long linger period, generally two weeks (1,209,600 seconds). Continuous Integration (CI) licenses are used when kwconan is invoked, when kwbuildproject is invoked with the --conan option, or during the kwconan stage of the TeamCity and Jenkins plugin. They allow you to analyze and access the results of Continuous Integration builds. A CI license also has a linger period of two weeks (1,209,600 seconds). User licenses are used by everyone who uses Klocwork tools. A user license (sometimes called an "individual" license) has a linger time of 7 days (604,800 seconds). "Linger" is the amount of time after the last use of a license before it is free for another user to check out. Note that linger times start at the end of the inactivity time-outs that some Klocwork components have. Detailed look at how the user license works
|