Home
Configuring
Learn how to configure the product.
Preferences
Preferences are personal choices about the appearance and operation of AppScan® Source for Analysis.
Enabling defect tracking with preferences
Defect Tracking System preferences allow you to enable the submission of findings to a defect tracking system - and determine how defects are submitted.
Quality Center preferences
You must first enable HP Quality Center as a General Defect Tracking System preference and then set the individual preference on the Quality Center tab.
Customizing Quality Center defect fields
Through a configuration file, you can customize the fields and interactions between these fields in the New Defect dialog box. You can find an example configuration file in <data_dir>\config\qc.dts (where <data_dir> is the location of your AppScan® Source program data, as described in topics/install_file_locations.html), which contains sample customizations and additional documentation. These customizations allow you to model your Quality Center Workflow script logic directly in the New Defect dialog box.

Configuring
Learn how to configure the product.
- Configuring applications and projects
  Before you scan, you must configure applications and projects. This section explains the Application Discovery Assistant, New Application Wizard, and the New Project Wizard. You will learn how to configure attributes for AppScan® Source for Analysis. In addition, this section teaches you how to add existing applications and projects for scanning - and how to add files to projects.
- Preferences
  Preferences are personal choices about the appearance and operation of AppScan® Source for Analysis.
  - General preferences
    General preferences allow you to tailor some of the AppScan® Source for Analysis default settings to fit your personal preferences.
  - AppScan® Enterprise Console preferences
    If your AppScan® Enterprise Server has been installed with the AppScan Enterprise Console option, you can publish assessments to it. The Enterprise Console offers a variety of tools for working with your assessments - such as reporting features, issue management, trend analysis, and dashboards.
  - Application server preferences for JavaServer Page compilation
    If you are scanning an application that contains JavaServer Pages (JSP), the AppScan® Source analysis engine must be able to compile the JSP code in order to analyze it. When you create your JSP project, you must specify the JSP compiler that AppScan Source should use (or accept the default compiler, which can be set in the Java™ and JSP preference page). If AppScan Source cannot compile your JSP files, use the application server preference pages to configure the JSP compiler that your application uses.
  - Defining variables
    When saving assessments or bundles, or publishing assessments, AppScan® Source for Analysis may suggest that you create a variable to replace absolute paths (without variables, AppScan Source for Analysis writes absolute paths to the assessment file to reference items such as source files). When you configure variables for absolute paths, you facilitate the sharing of assessments on multiple computers. It is recommended that you use variables when sharing assessments.
  - Enabling defect tracking with preferences
    Defect Tracking System preferences allow you to enable the submission of findings to a defect tracking system - and determine how defects are submitted.
    - Rational® ClearQuest® preferences
      To be able to complete Rational® ClearQuest® preferences, your Rational ClearQuest administrator must provide you with the required Rational ClearQuest settings. The settings are specific to your Rational ClearQuest environment.
    - Quality Center preferences
      You must first enable HP Quality Center as a General Defect Tracking System preference and then set the individual preference on the Quality Center tab.
      - Customizing Quality Center defect fields
        Through a configuration file, you can customize the fields and interactions between these fields in the New Defect dialog box. You can find an example configuration file in <data_dir>\config\qc.dts (where <data_dir> is the location of your AppScan® Source program data, as described in topics/install_file_locations.html), which contains sample customizations and additional documentation. These customizations allow you to model your Quality Center Workflow script logic directly in the New Defect dialog box.
    - Rational Team Concert™ preferences
      The Rational Team Concert™ preference tab allows you to configure a connection to a Rational Team Concert server and also to configure the values of work item attributes.
    - Team Foundation Server preferences
      The Team Foundation Server preference tab allows you to configure a connection to a Microsoft™ Team Foundation Server and to configure the values of work item fields.
  - Eclipse workspace importers: Eclipse or Rational® Application Developer for WebSphere® Software (RAD) preference configuration
    The AppScan® Source for Analysis installation provides a default Eclipse importer. This importer identifies the location of Eclipse and the JRE. If the default Eclipse importer is unable to import your workspace, it may be necessary to create a new Eclipse importer.
  - Email
    Configure email settings used to send findings under consideration as defects.
  - Java™ and JavaServer Pages
    Use this preference page to add, modify, or delete the Java™ Development Kit (JDK) that is used for scans (and to set a default JDK). In addition, use the page to set the default JavaServer Page (JSP) compiler.
  - Knowledgebase articles
    Use the Knowledgebase Articles preference page to set locations that contain AppScan® Source Security Knowledgebase articles.
  - Project file extensions
    Configure or add valid global file extensions for each project type, change the extensions to include in scans, exclude from scans, and specify extensions as web files.

Customizing Quality Center defect fields

Through a configuration file, you can customize the fields and interactions between these fields in the New Defect dialog box. You can find an example configuration file in <data_dir>\config\qc.dts (where <data_dir> is the location of your AppScan® Source program data, as described in Installation and user data file locations), which contains sample customizations and additional documentation. These customizations allow you to model your Quality Center Workflow script logic directly in the New Defect dialog box.

Available customizations include:

Displaying custom fields, missing fields, or both
Forcing fields to always display (overriding Quality Center settings)
Updating required state of fields based on selection of other fields
Dynamically updating list box options for a field based on the list box selection in another field