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

What to communicate to the team

Your team of developers, managers, build engineers(s), and administrator(s) need to know the following:

  • the URL of the Klocwork Server, so that managers and developers can access Klocwork Static Code Analysis and Klocwork Code Review, and install their own desktop analysis plug-ins
  • that the URL of the Klocwork Server with "/documentation" added to it will give them all of the Klocwork online documentation
  • the location of the projects_root directory (Klocwork administrators only)
  • the host and port of the License Server
  • who has permission to start and stop the Klocwork Servers, under what user ID, and, for Windows, whether the servers must be managed as Windows Services

If anyone else needs to access the database, for example, to do backups, and you have locked the database with a password, give the person the password. See Setting a password for the Klocwork database for more information.