Registering the AppScan® Source Database with AppScan® Enterprise Server

During AppScan® Source installation, if valid settings have been entered, the AppScan® Source Database should automatically be registered with the server. However, in the event that database registration does not complete or succeed, follow the instructions in this topic for completing the registration.

Note: As of AppScan® Source 10.0.7, the AppScan® Source Database uses TLSv1.2 to connect to the AppScan® Enterprise Server. Select TLSv1.2 during installation or specify -forceTLSv12 when setting appscanserverdbmgr.bat parameters from the command line.

Note: If you are connecting to an existing Oracle database server, make sure the Oracle database user (ounce by default) has a strong password with at least 16 characters.

Note: AppScan® Source server components, such as the AppScan® Source Database, are not supported on macOS.

AppScan® Source includes a utility that allows you to register the database with the server. The tool is <install_dir>\bin\appscanserverdbmgr.bat (where <install_dir> is the location of your AppScan® Source installation) - or <install_dir>/bin/appscanserverdbmgr.sh on Linux™. If you are having database/server connection problems, this tool can be run at a command prompt (after the server and client components have been installed) with these parameters:

Table 1. appscanserverdbmgr.bat parameters
Parameter	Description	IBM® Security AppScan® Enterprise Server Database Configuration graphical user interface equivalent
None	Launches a graphical user interface that allows you to enter and validate your AppScan® Enterprise Server and AppScan® Source Database configuration information, as described below.
`-s`	URL for your AppScan® Enterprise Server instance. For example, `https://localhost:9443/ase/`.	Server URL
`-u`	AppScan® Enterprise Server and AppScan® Source Database administrator user ID.	Product Administrator
`-p`	Password for your AppScan® Enterprise Server and AppScan® Source Database administrator user ID.	Password
`-forceTLSv12`	Specify `true` with this setting only if your AppScan® Enterprise Server is enabled for NIST 800-131a compliance (failing to do this will cause server connections to fail). If your AppScan® Enterprise Server is not enabled for NIST 800-131a compliance, specify `false` with this setting.	Force TLSv1.2
`-dbClient`	Specify `1` if your AppScan® Source Database is solidDB®. Specify `2` if it is Oracle.	Oracle
`-dbConnString`	Database connection string (for example, `"Driver={Oracle 7.0 32-bit - (ANSI)}"`). You can specify a TNS alias if you have configured the server according to Oracle TNS Alias configuration.	Connection String
`-dbConnInfo`	Database connection information (for example, `"tcp myhostname.mydomain.com 2315"`). Note: If `localhost` is specified rather than a fully-qualified host name, only the user of the local machine will be able to connect to the database.	Connection Info
`-dbUserid`	User ID for your database user account.	Database User ID
`-dbPassword`	Password for your database user account user ID.	Password

If you are using the graphical user interface, click Validate Connection after completing all entries in the AppScan® Enterprise Server section. Once the entries have been validated, complete the entries in the AppScan® Source Database section and click Validate Connection. When the database entries are validated, click Apply changes to register the database with the server.