In this section:

About Tool Settings

You can configure project-specific settings for Parasoft test execution and code analysis tools (C/C++test, dotTEST, Jtest, SOAtest). When the tools are connected to DTP, they import and use these settings, which enables you to centrally configure code analysis and test execution properties. The settings specified in the tool's .properties file, however, take precedence over the settings configure in this section. See the specific tool documentation for details on available settings.  

1. Choose Report Center Settings from the settings (gear icon) menu.
2. Click Projects in the Administration tab and click on a project. 
3. Enter your settings in the Parasoft Tool Settings section. Enter each setting on a new line. Use the # character to add comments.
    
   You can also click the information icon in the label for additional information and to view example settings.
   

You can also configure the settings for all projects. See Configuring Parasoft Tool Settings for All Projects. 

Example Settings

#License Settings
license.network.host=dtp.company.com
license.network.port=2222
license.use_network=true
#Mail Settings
report.mail.domain=company.com
report.mail.from=john.doe
report.mail.password=123456789
report.mail.server=mail.company.com
report.mail.username=john

About File Encoding

By default, DTP assumes that source code is encoded in UTF-8. If the source code is encoded with a different character set, you can specify it in the Parasoft Tool Settings form by adding the file.encoding.name property. For example:

file.encoding.name=UTF-16

You can configure this setting for individual projects or for all projects if all source code is encoded in the same way. See Configuring Parasoft Tool Settings for All Projects for additional information.

Auto-configuring Code Analysis and Test Execution Tools

Set the dtp.autoconfig property set to true in the Parasoft tool's .properties configuration file to enables the tool to use the settings configured in DTP. See the documentation for your tool for details. 

For example, the following settings would be added to the test execution and code analysis tool's configuration file:

dtp.autoconfig=true
scontrol.svn.exec=C\:\\Program Files\\svn\\bin\\svn.exe

This would enable the tool to use the following example configurations set in the Global Tool Settings field:

scontrol.svn.exec=/usr/bin/svn
scontrol.rep1.type=svn
scontrol.rep1.svn.url=http\://foo.bar.com/svn/repos
scontrol.rep1.svn.login=foo
scontrol.rep1.svn.password=65707c

In some cases, settings reused by Parasoft tools and DTP require additional customization. For instance, DTP may require different SCM credentials than the tools.

Auto-configuration can still be used by adding the server. prefix to identify the setting as a DTP Server-only setting. In the following Parasoft Tool Settings, the SVN executable directory is specified for the Parasoft tool with the scontrol.svn.exec setting, but for DTP the directory is set with server.scontrol.svn.exec:

scontrol.svn.exec=C\:\\Program Files\\svn\\bin\\svn.exe
server.scontrol.svn.exec=/usr/bin/svn
scontrol.rep1.type=svn
scontrol.rep1.svn.url=http\://foo.bar.com/svn/repos
scontrol.rep1.svn.login=foo
scontrol.rep1.svn.password=65707c
server.scontrol.rep1.svn.login=bar
server.scontrol.rep1.svn.password=19787a

DTP prioritizes the server. prefix value if the same non-prefixed also appears.

The following precedence of overwriting settings is used in DTP when the same setting appears in Global Tool Settings and project-specific Parasoft Tool settings:

• Project specific Parasoft Tool Settings with server. prefix
• Project specific Parasoft Tool Settings without server. prefix
• Global Tool Settings with server. prefix
• Global Tool Settings without server. prefix