Home
Configuring
Learn how to configure the product.
Preferences
Preferences are personal choices about the appearance and operation of AppScan® Source for Analysis.
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.

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.
  - 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.

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.

A tab page appears for each available language or project type: Java™, JavaScript™, ASP, Perl, ColdFusion, PBSA (for the pattern-based project type), COBOL, PL/SQL, T-SQL, VB.NET, .Net Assembly, VB, C/C++, ASP .NET 1.x, ASP .NET 2.x, WSDL, and C#, and Objective-C. When adding a new extension, identify if files with the new extension can be scanned, considered as a web file, or excluded.

Settings in this page are global. To set file extensions for individual projects, use the File Extensions tab of the Properties view for the selected project.

File extension settings

Table 1. File extension settings
Setting	Description	Usage examples
Scan or Assess	Include files with the indicated extension in full analysis.	If a .xxx extension is created for Java™ projects and marked as Scan or Assess, files with that extension will be compiled and scanned. A file can be part of a project but not marked as Scan or Assess if it should not be compiled and scanned (such as header files in C++). These files would be included in the project and searched during pattern-based analysis.
Web File	Mark files with the indicated extension for JSP compilation. This setting allows AppScan® Source to separate web sources from non-web sources.	If a .yyy extension is created for Java™ projects and marked as a Web File, files with that extension will be arranged as web sources in the projects. When AppScan® Source prepares for analysis, these files will be precompiled into classes to be analyzed.
Exclude	Do not create source files in the project for files with the indicated extension. Files with this extension will not be scanned.	Create a .zzz extension for files that are necessary to your projects for compilation, but do not need to be included in analysis.