Using a SQL server database

To use SQL Server as the Application Security database, perform the following checks:

• Enable the Auto Update Stats Asynchronously (AUTO_UPDATE_STATISTICS_ASYNC) option for the database.

  For instructions, see the Microsoft SQL documentation website.

• Ensure that your SQL Server database schema collation is case-sensitive. The default installation of SQL Server is case-insensitive.

  Before you run the OpenText-provided SQL scripts, verify that there are no open connections to the database.
  

• Ensure that snapshot isolation is enabled (ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT are set to ON) on the database schema used for the installation.

• During SQL script executions, check the client tool to ensure that its ANSI null default option is set to ON.

  To do this, you can either use a SET command (set ANSI_NULL_DFLT_ON to ON) or the Query Editor.

Windows domain authentication

For Windows domain authentication, you must perform the following additional steps before you deploy Application Security:

1. Ensure that you add integratedSecurity=true to the JDBC URL.

2. Obtain the mssql-jdbc_auth-<version>-<arch>.dll file.

   For more information, see Connecting with integrated authentication On Windows Microsoft documentation.

3. Place the mssql-jdbc_auth-<version>-<arch>.dll file in the directory specified for the -Djava.library.path parameter of the JDK_JAVA_OPTIONS environment variable.
4. Place the mssql-jdbc_auth-<version>-<arch>.dll file in a directory that is included in the PATH environment variable (for example, C:\Windows\System32).

5. Do one of the following:

   • Use the autoconfig file to configure Application Security (see Automating Application Security configuration).

   • Configure Application Security with SQL authentication, and then remove the db.username and db.password parameters from the datasource.properties file.
6. Ensure that Tomcat is running with the domain account you want to use to connect to the database.