AppScan® Enterprise configuration

With new installations of AppScan® Source version 10.0.2 and newer, you must configure AppScan® Enterprise if you want to work in connected mode. These tasks need to be performed once.

As covered in Installing topics, AppScan® Source can be configured in these ways:

Configuring AppScan® Source and AppScan® Enterprise to use SolidDB/Oracle to store data.

When upgrading AppScan® Source from version 10.0.1 or earlier to version 10.0.2 or later, AppScan® Source can continue to use the previously configured SolidDB/Oracle database to store data.

After upgrade, the database should be registered with AppScan® Enterprise Server. Use appscanserverdbmgr.bat/ to (re)register the database with AppScan® Enterprise Server.

If AppScan® Source needs to publish assessments then AppScan® Enterprise Server should be installed with both User Administration and Enterprise Console. If you do not intend to publish assessments, then AppScan® Enterprise Server can be installed just with User Administration alone.

Note: The AppScan® Enterprise instance should be version 10.0.0 or later.

Using the AppScan® Database Service integrated with AppScan® Enterprise to store data

With new installations of AppScan® Source version 10.0.2 and newer, you must configure AppScan® Enterprise if you want to work in connected mode. This section covers steps related to configuring AppScan® Enterprise to support AppScan® Source installations.
Note: With new installations of AppScan® Sourceversion 10.0.2 and newer, AppScan® Enterpriseversion 10.0.2 or later is required. Older versions of AppScan® Enterprise are not supported. In addition, AppScan® Enterprise Server must be installed with both User Administration and Enterprise Console.
Configuring AppScan® Enterprise for use with AppScan® Source version 10.0.2 and newer has two major steps. After the AppScan® Database Service is configured, AppScan® Source user management and data backup is performed in AppScan® Enterprise:

Configuring the AppScan® Database Service

With AppScan® Enterprise Server version 10.0.3 and later, create and configure the AppScan® Database Service as a Windows service using the Configuration Manager utility in AppScan® Enterprise.

Note: You must have administrator privileges in AppScan® Enterprise and appropriate permissions to create a new database in MS-SQL to perform these steps in the Configuration Manager.
Launch the Configuration Manager in one of two ways:
  • Through the AppScan® Enterprise Configuration Wizard.
  • From AppScan® Enterprise Server install location:
For complete information on using the Configuration Manager, see Configuring AppScan Source Database Service from AppScan Enterprise.
Important: Take care in naming the database and configuring the storage path for the AppScan® Database Service. Attempting to change the name or the path later will corrupt data.

Configuring AppScan® Enterprise Server for AppScan® Database Service

After configuring the AppScan® Database Service using the Configuration Manager tool, the AppScan® Enterprise Server needs to be restarted manually.

Note: Each time you modify the AppScan® Database Service port, you must restart AppScan® Enterprise Server service for the changes to take effect.

User management

When AppScan® Source version 10.0.2 or later is configured to use the AppScan® Database Service, user management takes place in AppScan® Enterprise. The following AppScan® Source-specific user permissions have been added to AppScan® Enterprise Server:
  • Create and share a custom rule.
  • Delete a published assessment on the server.
  • Publish a new assessment to the server.
  • Retrieve a published assessment from the server.
  • Share a filter using the server.
  • Share a scan configuration using the server.
  • Create a PBSA scan rule on the server.
The AppScan® Enterprise administrator can create or modify user types by configuring these AppScan® Source-specific permissions and assign users to appropriate types.

Data backup

Back up AppScan® Source-related information regularly to avoid inadvertent data loss. Data is stored in two locations in AppScan® Enterprise Server
  • The MS-SQL database holds the metadata of all the shared information. The database name is configured in
  • The file system holds the actual files that are shared from AppScan® Source. This file system path for the data is configured in
Back up both locations at the same time to avoid data conflicts. Backing up data asynchronously risks rendering the data unusable.