Each integration project is created with default configuration files. You can edit these default files as well as create and import new ones. Once you've imported a configuration file, you need to run an analysis to see the results.

You need the "Change project settings" permission to view and manage configuration files.

To manage configuration files, log into Klocwork Static Code Analysis, locate a project in the Projects list, and click configuration. Here you can view, edit, import and delete files for a particular project.

Configuring a single project or an entire projects_root

You can import a configuration file into a single project or into an entire projects_root. When you import a configuration file to a projects_root, the file is copied to all projects created after that point, unless you purposely remove it from a particular project. Project-specific configuration files may be used in addition to or instead of the default configuration files for the projects_root.

There are two ways to import a configuration file into a single project:

In Klocwork Static Code Analysis, locate a project in the Projects list, click configuration, and click the plus sign.
Use kwadmin import-config:

kwadmin import-config <project_name> <file>

To import a configuration file into a projects_root, use kwadmin import-config:

kwadmin import-config workspace <file>

Use kwadmin delete-config to remove a configuration file from an entire projects_root:

kwadmin delete-config workspace <file>

Encoding

All configuration files used in Klocwork analysis must be UTF-8 encoded if they contain multibyte characters (for example, Japanese). If your configuration files contain multibyte characters, you must convert them before using them in Klocwork analysis.

Configuration files that you can import into integration projects

Note: You can upload files up to 2 GB in size.

File name	Description	Purpose of file	More information
.h	macro override file for C/C++	suppresses the expansion of specified macros, or replaces undesired macro definitions with more suitable ones	Tuning C/C++ analysis
.jkb	Java knowledge base file	tunes Klocwork issue detection to your Java software project	Tuning Java analysis through knowledge bases
.kb	C/C++ knowledge base file	tunes Klocwork issue detection to your C/C++ software project	Tuning C/C++ analysis
.mconf	metrics thresholds configuration file	changes the thresholds at which Klocwork reports issues	Changing the thresholds for reported metrics
.pconf	checker configuration file	allows you to enable, disable and organize checkers	Configuring checkers for the integration build analysis
.sow	source ownership file	associates the name of a person or group with a file or class of source code. Only one `.sow` file is used for an analysis. An `.sow` file can only be imported into a project; it cannot be imported into the projects_root directory.	Tracking issues by owner
.szt	size-of-types file	specifies the size of bytes of your built-in types, so that the "bytes of" metrics are correctly calculated	Specifying sizes for built-in types
.tconf	taxonomy configuration file	allows you to add new custom checkers to taxonomies or categories and to add reference information to existing checkers	Configuring checkers for the integration build analysis
.tpl	build specification template file	a version of build specification that uses variables for any paths that may differ on local machines where the analysis is run	Providing a build specification template for your developers
.ume	user-defined metrics file	allows you to define your own metrics, apply them to a specific source file or class, and report on them in Klocwork Static Code Analysis	Customizing metrics reports in Klocwork Static Code Analysis