Publishing assessments to AppScan Enterprise

Depending on your installation, you can publish assessments to AppScan® Enterprise and/or the Enterprise Console for access in the Published Assessments view. AppScan Enterprise and the Enterprise Console offer a variety of tools for working with your assessments, such as reporting features, issue management, trend analysis, and dashboards.

About this task

If you have upgraded to AppScan Source version 10.0.2 from an earlier version, you can publish to the AppScan Enterprise Console. If you have a new installation of AppScan Source version 10.0.2, you can publish directly to AppScan Enterprise or to the AppScan Enterprise Console.

Before you can publish assessments to AppScan Enterprise or the Enterprise Console, you must configure server settings in AppScan Enterprise. For information on configuring server settings in AppScan Enterprise, see AppScan Enterprise configuration. For information about setting preferences in AppScan Enterprise Console, see AppScan Enterprise Console preferences.

Note: For some versions of AppScan Source and AppScan Enterprise, the version and release level of the two products must match in order to publish from AppScan Source to the AppScan Enterprise Console. See How to enable connections and publish assessments for different versions of AppScan Source and AppScan Enterprise to learn which versions of AppScan Source and AppScan Enterprise are compatible when publishing assessments.

Restriction: When you scan multiple applications or projects, a parent node containing assessments for each scanned item is created in the My Assessments view. The individual child assessments cannot be managed in this case (for example, the child assessments cannot be removed or published individually). When multiple applications or projects are scanned at the same time, you can only manage the assessments as a group (the parent node).

Procedure

If you upgraded to AppScan Source version 10.0.2 or newer, use one of these methods to publish one or more assessments to the Enterprise Console:
1. Select one or more assessments in the My Assessments view and then click Publish Assessment to AppScan Enterprise Console.
2. Right-click the assessment (or a selection of assessments) in the My Assessments view and select the Publish Assessment to AppScan Enterprise Console menu item.
3. When an assessment is open, choose File > Publish Assessment to AppScan Enterprise Console from the main menu.
If you have a new installation of AppScan Source version 10.0.2, use one of these methods to publish one or more assessments to AppScan Enterprise or the Enterprise Console:
1. Select one or more assessments in the My Assessments view and then either click Publish Results to AppScan Enterprise to publish to the Enterprise Console or Publish Assessment file to AppScan Enterprise to save the assessment file to AppScan Enterprise.
2. Right-click the assessment (or a selection of assessments) in the My Assessments view and then either select the Publish Results to AppScan Enterprise menu item to publish to the Enterprise Console or Publish Assessment file to AppScan Enterprise menu item to save the assessment file to AppScan Enterprise.
3. When an assessment is open, choose File > Publish Results to AppScan Enterprise from the main menu to publish to the Enterprise Console or choose File > Publish Assessment file to AppScan Enterprise from the main menu to save the assessment file to AppScan Enterprise.
In the Publish to AppScan Enterprise Console dialog box:
1. Specify an AppScan Enterprise Console application to associate the assessment with. This is required when connected to AppScan Enterprise Server Version 9.0.3 and higher (unless you disable the requirement, as described here). Associating an application is optional when connected to earlier versions of AppScan Enterprise Server. If you are connected to an earlier version of AppScan Enterprise Server, by default, the application is set to the last application that was specified for publishing. If no applications have previously been specified when publishing, no application will be used by default. To specify an application:
  1. Click the Application field Select button.
  2. The Select Application dialog box opens, displaying all applications that already exist in the AppScan Enterprise Console. To view an application's attributes in the AppScan Enterprise Console, click View Profile next to it.
  3. Select the application to associate the scan with - or create a new application for this purpose by clicking Create new application. Clicking this link will open the AppScan Enterprise Console and allow you to create a new application. Once the new application's attributes have been saved, the Select Application dialog box will automatically refresh to include it for selection (if it does not automatically include the new application, click Refresh).
    Tip: In the Select Application dialog box, you can use the filter field to narrow down the list of applications. As you type, the filter is automatically applied to the list of applications. The asterisk (*) and question mark (?) characters can be used as wildcards. An asterisk matches any group of zero or more characters, while a question mark matches any single character.
  4. Click OK after you have selected the application.
2. Required: In the Name field, specify a name that the assessment will be saved as in the AppScan Enterprise Console.
3. Optional: When connected to AppScan Enterprise Server versions prior to version 9.0.3: Use the Folder field to set the location to publish to. By default, the location is set to the last location that was used for publishing. If no assessments have previously been published, your default AppScan Enterprise Console folder is selected (note that this is the default folder for the user ID that is specified in the AppScan Enterprise Console preference page). To choose a different folder to publish to, click the Folder field Select button and then choose the folder that you want (only folders that you have permission to publish to are available). If the folder that you want to publish to is not available, click Refresh to update the folder tree with any changes that have been made on the server.
Click Publish.

Results

When saving an assessment, AppScan Source for Analysis writes absolute paths to the assessment file to reference items such as source files. These absolute paths may cause difficulty in sharing the file on another computer that has a different directory structure. To be able to create portable assessment files, you should create a variable (see Defining variables or Defining variables when publishing and saving).

After the assessment has been published, a link to AppScan Enterprise (Enterprise Console) will be provided in an information message. Clicking the link will open the portal page in your default external web browser.

Tip: If publishing fails, check that the Enterprise Console server is running and that you are able to access its control center URL in a browser (use the same Enterprise Console URL that you have specified in the AppScan Enterprise Console preference page).

Note:

Large assessments may take longer to appear at the portal. If you receive no error messages after publishing and the report does not appear at the portal, check with your administrator.
Any attempts to publish an assessment that has the same name as one that is currently being processed by the Enterprise Console will fail. In addition, if you publish the commonly-named assessment after the first one has been processed, the second assessment will overwrite the first one (the Enterprise Console can provide a trending analysis for commonly-named reports if it has been configured to do so ahead-of-time). To determine if an assessment has finished processing, access the Enterprise Console control center in a web browser and then navigate to the appropriate user folder and check the status of the report.
AppScan Source does not support publishing to an Enterprise Console instance that has been configured to use proxy settings. Attempting to publish to an instance that uses proxy settings will result in an error.