Importing AppScan data to use in reports

An import job takes the results from a data file, and integrates it into the AppScan® Enterprise Server database. Imported data can be used to create reports and dashboards. It can also be combined with data from content scan jobs to create a complete picture of your issues.

Before you begin

Any issues that are duplicated between a content scan job and an import job are merged in your reports; however, identical variants will not be merged, so there might be duplicate variants for issues in the same report.

About this task

User roles: Product Administrator; Job administrator (on the folder)

Procedure

  1. Go to the Folder Content Summary page and click the Create icon (Create).
  2. On the Create Folder Item page, select an Import Job and give it a Name and Description. Associate it with an Application from the list. Associated jobs appear in the application's Scans view in the Applications tab. Then click Create.
  3. On the What to Import page, select the Import type:
    • AppScan Standard Results Import (XML files exported from AppScan 7.7 or newer)
    • AppScan DE Results Import (SRPT files exported from AppScan DE 7.8 or newer)
    • AppScan Source Results Import (OZASMT files exported from AppScan Source 7.0, 8.0, 8.5, or newer) )
  4. Click Import data file now or Import data file on job run.
  5. On the Data File Upload page, click Browse to find the data file on your network, and click Import.
  6. From the Folder Explorer view, run the job to import the data into the database.
  7. Run the report pack to update it with the results.

Results

By default, a report pack is automatically created when you create an import job. The report pack contains reports that are most common to the type of data you have imported. You must run the report pack after the job to update the data in it.
Note: AppScan Enterprise V10.0.5 release provides administrators the ability to prioritize between User responsiveness while interacting with AppScan Enterprise over Publishing/Importing Scan assessment to AppScan Enterprise. This is based on feedback from users that interaction with AppScan Enterprise slows down while large assessment files are being published. As a result, you may notice increased time for publishing results from AppScan Source to AppScan Enterprise or while importing Issues into AppScan Enterprise from the Monitor tab.

If you prefer to have faster publish/import time and interaction with the AppScan Enterprise is minimal, this behavior can be controlled by performing the following steps:

  1. Locate the asc.properties file in the AppScan Enterprise installation location, which is typically available at C:\Program Files (x86)\HCL\AppScan Enterprise\Liberty\usr\servers\ase\config\asc.properties.
  2. Add the following line to the file:

    issue.import.batch.interval=0

  3. Save the file.
  4. Restart the HCL AppScan Enterprise Server service from Windows service.

The issue.import.batch.interval can have a value between 0 – 3 (Default is 1, when the value is not specified). This value is a factor that determines the nature of user responsiveness verses publish assessment duration.

  • 0 – Low impact on publish/import duration, User responsiveness may be slow especially when multiple parallel publish tasks are running(as before). Can be set if number of assessments are less, or if User interaction with AppScan Enterprise is minimal.
  • 1 (Default) – Medium impact on Upload duration, User responsiveness will better. You can set this when user interactions with AppScan Enterprise is more, and number of assessment published is of more.
  • 2- High impact on publish/import duration. User responsiveness will normal.
  • 3 – Highest impact on publish/import duration, User responsiveness would be normal. To be used when there is high interaction of users with AppScan Enterprise and there is need to publish/import multiple parallel assessments.

What to do next

You can get detailed help on configuration options by clicking the Help icon (Help) of each property page.