3.15 Configuring Database

SSPR uses two types of databases:

  • LocalDB: LocalDB is a local embedded database. SSPR uses it for storing local data. LocalDB requires no administration or maintenance, and the default values are sufficient.

  • RDBMS: SSPR can use a traditional RDBMS database to store data for certain functions. Any standard RDBMS that supports a standard Java JDBC driver can work. SSPR connects to the database and create necessary tables. You can configure multiple SSPR server instances to the same database instance. SSPR officially supports MS SQL database.

Configure the following settings if you select RDBMS:

  • Database Class: Name of the database class. Specify the Java JDBC full driver class name.

    The classpath must include the corresponding JDBC driver JAR or ZIP file, typically, in the WEB-INF/lib directory or the application server's lib directory. For example, in Tomcat, it is <TOMCAT_HOME>/webapps/<SSPR>/WEB-INF/lib or <TOMCAT_HOME>/lib. The default folder name under which the application is deployed is <SSPR>. If you have changed this name, use the appropriate path name accordingly.

  • Database Connection String: Specify the database connection string in the standard JDBC format.

  • Database Username: Specify the user name that can connect to the database.

  • Database password: Specify a password for the database user.

NOTE:The RDBMS settings are applicable only if you have selected Active Directory - Store Responses in a Database.

This section discusses:

3.15.1 Configuring Database Server

  1. Create a database.

    For more information about how to create a database, see the related product documentation.

  2. Create a database administrator for that database. You need to specify this administrator during SSPR configuration.

  3. Create a user and associate it to the database you created in Step 1.

  4. Ensure that the user has enabled the SQL server authentication mode and has suitable rights to open the database:

    1. Go to the SQL Server Object Explorer.

    2. Expand the server and instance and select Security.

    3. Under Security, select Logins.

    4. Under Logins, create a new user. While creating the user, select the authentication as sqlserver authentication instead of the default Windows authentication.

    5. Select LocalDB as the default database for the user. Assign the user required administrator’s roles.

      After creating the user, map it to LocalDB.

3.15.2 Configuring Database Settings

If you want to store responses in the database, configure some specific settings. This section discusses about how to configure the database for your LDAP directory.

Perform the following steps:

  1. Select a template in Configuration Manager under Template.

  2. Click Settings > Database.

  3. Configure the following settings:

    Field

    Description

    Database Class

    Specify the Java JDBC full driver class name. The corresponding JDBC driver JAR or ZIP file must be included in the classpath, typically in the WEB-INF/lib directory or the application server's lib directory.

    Database Connection String

    Specify the database connection string in the standard JDBC format.

    Database Username

    Specify a username.

    Database Password

    Set a password for the database user.

    Database Key Column Type

    Specify the database column type for key columns. The column type is used only during schema creation. All tables contain two columns, a key, and a value column. For most databases, the standard VARCHAR column format is appropriate for the key column. Generally, the data stored in the key column is US-ASCII key.

    For the Oracle database, set this to VARCHAR2.

    Database Value Column Type

    Specify the database column type for value columns. The column type is used only during schema creation. All tables contain two columns, a key, and a value column. For most databases, the standard TEXT column format is appropriate for the value column. Generally, the data stored in the value column is be UTF-8 formatted XML, JSON, or other text-based value data.

    For the Oracle database, set this to CLOB.

    Database Trace Logging

    Select this check box to log the data and the read/ write activity to the TRACE debug output. This option can send security-sensitive information to the debug output, including passwords.

  4. Click Actions > Save.