Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

Setting up redundant license servers

Some large enterprises run three license servers on the same corporate subnet to ensure reliability. If you want to run redundant license servers, contact the Rogue Wave license team to obtain a special license.

A license for redundant servers must be locked to the FlexNet host ID of each host. The syntax of the redundant server license is different from the standard Klocwork license file, in that it has three SERVER lines. You cannot just add these extra lines to a standard license file. Attempting to add the lines destroys the license. Here is a sample of the first few lines of a redundant license file:

SERVER flex1.klocwork.com 000d602dbd58 27000

SERVER flex2.klocwork.com 000d603dbe62 27000

SERVER flex3.klocwork.com 000d814eFg99 27000

USE_SERVER

VENDOR klocwork

To set up redundant license servers:

  1. Place the license server executable (lmgrd) and the Klocwork vendor daemon (klocwork) on each of the hosts with a copy of the redundant license file, or place the license in a shared location that all three servers can access.
    For example:
    C:\Flexnet\Klocwork\Klocwork_license.lic
    <Server_install>\3rdparty\bin\lmgrd
    <Server_install>\3rdparty\bin\klocwork.exe
  2. Start the license servers with the -c option. For example, run the following command on all three machines:
    ./lmgrd -c license.lic -l lm.log
    
    or, in full paths:
    C:\Flexnet\klocwork\lmgrd -c C:\Flexnet\klocwork\klocwork_license.lic -l C:\Flexnet\klocwork\lm.log
    
  3. On the machine(s) hosting the Klocwork Server, use the command kwservice set-service-property to set the host name and port number of the master License Server. The master License Server is the first server in the list of redundant license servers in your license file. Be sure to use fully qualified domain names, to prevent networking issues. See Viewing and changing Klocwork server settings.
  4. On the machine where you will be starting the Klocwork Server, set the KLOCWORK_LICENSE_FILE environment variable as follows. <license-host-1> is the host name of the master License Server in the triad.
    1. Unix
      • Set the variable it in the shell environment where the servers will be started.
      • Use a colon (:) as separator.
      KLOCWORK_LICENSE_FILE=<license-port>@<license-host-1>:<license-port>@<license-host-2>:<license-port>@<license-host-3>
      
      Unix example:
      KLOCWORK_LICENSE_FILE=27000@flex1:27000@flex2:27000@flex3
      
    2. Windows
      • Set the variable at the System level.
      • Use a semicolon (;) as separator.
      KLOCWORK_LICENSE_FILE=<license-port>@<license-host-1>;<license-port>@<license-host-2>;<license-port>@<license-host-3>
      
      Windows example:
      KLOCWORK_LICENSE_FILE=27000@flex1;27000@flex2;27000@flex3
      
  5. Start the Klocwork servers as detailed in Starting the Klocwork Servers.
  6. On all machines where Klocwork clients (for example, build tools and Klocwork plug-ins) will connect to the License Server, set the KLOCWORK_LICENSE_FILE environment variable as in Step 4.

For more information about the various types of redundant server configurations and lmgrd options, refer to the FlexNet Publisher documentation.