Home
Reference
Review reference information for the product.
Configuring Wizard topics
Learn about configuring wizard topics.
Database Connection
Enter the SQL Server name, port number, select the authentication mode and the name of the database you are connecting to. If you select SQL Authentication, enter the username and password before you click Test Connection to verify that you can connect to the SQL Server. The configuration wizard does not proceed until the connection is successful. When AppScan® Enterprise Server creates the database in SQL Server, it automatically configures the collation for it.

Reference
Review reference information for the product.
- Configuring Wizard topics
  Learn about configuring wizard topics.
  - License Server
  - Server Components
    Select the components you want to configure. The components available to you depend on the license.
  - Instance Name
    Specify the name of the instance you want to configure.
  - Database Connection
    Enter the SQL Server name, port number, select the authentication mode and the name of the database you are connecting to. If you select SQL Authentication, enter the username and password before you click Test Connection to verify that you can connect to the SQL Server. The configuration wizard does not proceed until the connection is successful. When AppScan® Enterprise Server creates the database in SQL Server, it automatically configures the collation for it.
  - Database encryption changes
    AppScan® Enterprise no longer uses proprietary encryption mechanisms to prevent unauthorized transfers of its database because there are other third-party mechanisms that are designed to specifically perform physical layer encryption with less impact on performance. This type of encryption is usually applied at the database server level; for example, SQL Server Enterprise Edition has a built-in encryption TDE mechanism (Transparent Data Encryption). TDE encrypts the data residing in the database or in backups on physical media. SQL Server Standard Edition uses Windows™ Encrypting File System.
  - Service Account
    Specify the service account that will be used by the services.
  - Server Certificate
    For security reasons, HTTPS is enabled for Enterprise Console. Choose a certificate from the list of certificates that are installed in IIS. Taking these actions will help you deploy a secure AppScan® Enterprise in your environment.
  - Restore AppScan Server settings
    Upon upgrade, you can choose to restore previous AppScan Server customized settings on the Liberty Server. This screen appears once upon upgrade; if you run the configuration wizard later, this screen won't appear.
  - Server Keystore
    If you choose to use a keystore that contains a trusted certificate chain for this host, complete the available fields.
  - Authentication Mechanism
    Select an Authentication Mechanism to use to log into the Enterprise Console. If you choose Windows, you must be part of a domain.
  - Product Administrator
    This user is licensed separately; if you want to reassign the Product Administrator license, you must rerun the configuration wizard.
  - Server Group Changes
    A server group is a group of items that can be tested as a unit; the same security tests will be applied to all the servers in the group. A server group can be any combination of domains and IP addresses. You must create one or more server groups to define what can be tested. Once a server group is created, you then assign it to a Job Administrator. That person then creates jobs that perform security tests on a specific group of servers. As of version 9.0, Server Groups are no longer defined by URL. Any existing URL definitions are removed from existing Server Groups and listed in the WFCfigWiz.log.
  - Server Configuration
    Configure the host name and port of the Liberty server for AppScan Enterprise Server to use. If you are using Windows authentication, prefix the host name with your domain name.
- Folder Explorer topics
  Learn about folder explorer topics.
- Triage with reports
  Reports are automatically generated after a job has run. They provide a way of managing issues so that you can helps you manage issues that are important to your organization and do so in a way that is supported both by the Enterprise Console's workflow and the workflows of other processes within your organization.
- Configuration Manager
- AppScan resources
  A GitHub collection of integrations, helper scripts, utilities, useful examples, libraries, and other resources related to HCL AppScan.

Database Connection

Enter the SQL Server name, port number, select the authentication mode and the name of the database you are connecting to. If you select SQL Authentication, enter the username and password before you click Test Connection to verify that you can connect to the SQL Server. The configuration wizard does not proceed until the connection is successful. When AppScan® Enterprise Server creates the database in SQL Server, it automatically configures the collation for it.

Note:

AppScan Enterprise supports Windows Authentication and SQL authentication to connect to SQL Database. Refer to Microsoft's article on Authentication Mode and choose the authentication mode that fits your requirement. You can change from one authentication mode to another, but make sure to re-run the configuration wizard.
The user must be assigned a sysadmin server role on the SQL server. The user must also have access to the database and must be granted a minimum of db_ddladmin, db_datawriter, and db_datareader rights or the db_owner rights.
The syntax for the SQL Server name has changed with the introduction of Liberty support. ".\SQL_SERVER_NAME" no longer works. Use "HOSTNAME\SQL_SERVER_NAME" instead.
If your environment uses a named SQL Server instance for the AppScan Enterprise database, make sure that TCP/IP is enabled in the SQL Server configuration manager, and restart the SQL services for SQL Server. Use the port number of the named SQL Server instance instead of the default port number (1443).
If you have multiple instances and want to remove an instance that is no longer required:
- Clear the Use default name check box.
- Select the name of the relevant instance, click Remove, confirm the removal when prompted, and finish the wizard.
The Set Recovery Mode to "Simple" checkbox
- This option does not have any impact in case of an upgrade to an existing database.
- When you create or erase a database:
  - Select the checkbox to run the database recovery in Simple mode.
  - Clear the checkbox, to run the database recovery in the database's default recovery mode. For more information, contact your Database Administrator.
While running the configuration wizard, clear the Set Recovery Mode to "Simple" checkbox if you use the Azure SQL managed database instance.