Home
Configuring
Learn how to configure the product.
Preferences
Preferences are personal choices about the appearance and operation of AppScan® Source for Analysis.
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.
Tomcat
This topic describes the preferences that you need to set for configuring AppScan® Source to reference an Apache Tomcat application server other than one that is supplied with AppScan Source.

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.
    - Tomcat
      This topic describes the preferences that you need to set for configuring AppScan® Source to reference an Apache Tomcat application server other than one that is supplied with AppScan Source.
    - WebLogic 11 and 12
      This topic describes the preferences that you need to set for configuring AppScan® Source to reference an Oracle WebLogic Server.
    - WebSphere® Application Server
      This topic describes the preferences that you need to set for configuring AppScan® Source to referenceWebSphere® Application Server for JSP compilation.
  - 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.

Tomcat

This topic describes the preferences that you need to set for configuring AppScan® Source to reference an Apache Tomcat application server other than one that is supplied with AppScan® Source.

Apache Tomcat Versions 7 and 8 are included in the installation of AppScan® Source. If the Tomcat 7 and Tomcat 8 preference pages are not configured, AppScan® Source will compile JSP files using the supplied Tomcat JSP compiler that is currently marked as default. If you want to employ an external supported Tomcat compiler, use the Tomcat preference pages to point to your local Tomcat installation.

If you are using an external supported Tomcat compiler, go to the appropriate preference page and set the application server installation directory. Specifying the installation directory allows AppScan® Source to automatically find all application server dependencies when configuring projects.