Select your database type

1. Locate and copy the necessary jdbc driver for your database into <frevvo-home>\tomcat\lib.
2. Edit the file <frevvo-home>\tomcat\conf\server.xml
3. You will see a data source definition for the frevvo database type name="jdbc/sharedfrevvoDS". See the sample below of the HSQLDB data source in the server.xml file.
4. Comment out the pair of the definitions for the default database (HSQLDB) using the <!-- --> comment characters. The entire section must be commented out:

<!-- 
		HSQLDB Resource 
	<Resource auth="Container"
		type="javax.sql.DataSource"
		name="jdbc/sharedfrevvoDS"
		driverClassName="org.hsqldb.jdbcDriver"
		username="sa"
		password=""
		url="jdbc:hsqldb:file:${catalina.home}/../data/db/forms"
		maxActive="200"
		maxIdle="20"
		maxWait="10000"
		validationQuery="select 1 from INFORMATION_SCHEMA.SYSTEM_USERS"
		testOnBorrow="true"
		testOnIdle="true"
		timeBetweenEvictionRunsMillis="10000"
		removeAbandoned="true"
		logAbandoned="true"/>
-->

5. Next, uncomment the pair of definitions for your database. Ex: if you are using SQL server, uncomment the definition for SQLSERVER Resource. Save the changes.

 <!-- 
		SQLSERVER Resource
 -->		
	  <Resource auth="Container"
		maxActive="200"
		maxIdle="20"
		maxWait="10000"
		validationQuery="select 1"
		testOnBorrow="true"
		testOnIdle="true"
		timeBetweenEvictionRunsMillis="10000"
		removeAbandoned="true"
		logAbandoned="true"
		name="jdbc/sharedfrevvoDS"
		driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
		username="root"
		password=""
		type="javax.sql.DataSource"
		url="jdbc:sqlserver://localhost:1433;databaseName=frevvo;"/>	

Configure the frevvo database

For your selected database type in server.xml:

1. Locate the sharedfrevvoDS data source url parameter and decide on a name for the frevvo database. For the SQL Server it would look like this: "url="jdbc:sqlserver://localhost:1433;databaseName=frevvo". You can change the name "frevvo" to whatever you wish, "" for example. But it must match the database name you create in your SQL server. See configure the connection Url below.
2. Create a UTF-8 encoded database "frevvo" (assuming you left the url parameter database name as the default) in your SQL server
3. Set the sharedfrevvoDS data source url parameter to your database server. See configure the connection Url below.

4. Set the sharedfrevvoDS data source username and password parameters to a user that has read and write permissions to the frevvo database.

5. The frevvo database setup is now complete.  will create all the necessary tables upon startup.

Configure the Connection Url

Configuration of the connection Url is key to successfully connect the  server to your database. Consult your DBA to assist with connection issues.

For your selected database type in server.xml:

1. Set the sharedfrevvoDS data source url parameter to your database server. If  and the database server are collocated "localhost" may be fine. The url parameters depend on the database type and installation choices made when your DBA installed your database software. Consult your DBA for the correct connection values. For example, SQL server installed on a non-default port and running on a machine named e00sca will require that you add a port number and host name to the Url. For example:

url="jdbc:sqlserver://e00sca:59377;databaseName=frevvo;"

As of SQL 2000, Microsoft SQL allows installation of multiple SQL named instances. If your SQL server was installed this way you must use the instance parameter. For example if you database instance was named xyzzy:

url="jdbc:sqlserver://e00sca:59377;databaseName=frevvo;instance=xyzzy"

2. Verify that the user and password required to connect to the frevvo database are correct.
3. Make sure that the user configured in the data sources has permissions to read and write to the frevvo database.

url="jdbc:sqlserver://localhost:1433;databaseName=frevvo;sendStringParametersAsUnicode=false"/> 

Non Standard Databases

If you are trying a different database type and do not see an example in server.xml for your database, you can create a new data source entry. Hibernate supports the following dialects however  has only been certified to run with a subset of these databases. For additional dialects see Hibernate documentation. Refer to our Supported Platforms for the list of Application Servers and databases supported/certified by frevvo.

•  org.hibernate.dialect.HSQLDialect
•  org.hibernate.dialect.MySQL5Dialect
•  org.hibernate.dialect.MySQL5InnoDBDialect
•  org.hibernate.dialect.Oracle9Dialect
•  org.hibernate.dialect.OracleDialect
•  org.hibernate.dialect.PostgreSQLDialect
•  org.hibernate.dialect.SQLServerDialect
•  org.hibernate.dialect.Sybase11Dialect

UTF-8 Encoded Database

MySQL UTF-8 Example

These commands will create the proper frevvo utf8 encoded database in mySql:

create database if not exists frevvo default character set "utf8" default collate "utf8_unicode_ci"; 

You can convert a database and/or table to UTF-8 using the MySQL configuration file or the MySQL cmd tool.

Configuration file:

[mysqld]
default-character-set=utf8
default-collation=utf8_unicode_cii

MySQL cmd tool:

ALTER DATABASE frevvo CHARACTER SET utf8 COLLATE utf8_unicode_ci;
ALTER TABLE `frevvo16089`.`formsubmission` CHARACTER SET utf8 COLLATE utf8_unicode_ci; 

Configure Snapshot Isolation for SQL Server Databases

If you are using SQL Server as your Live Forms database, it is highly recommended that you turn on the READ COMMITTED SNAPSHOT setting in the database. You do not have to do this if you are using MySQL or Oracle databases because the option is turned on by default. There are two ways to turn on the option:

1. Using DDL (Data Definition Language) - Run the commands listed below

   ALTER DATABASE <your frevvo database schema> - replace <your frevvo database schema> with the name of your frevvo database schema 
   SET READ_COMMITTED_SNAPSHOT ON

2. Using SQL Server Management Studio: Turn on the “Is Read Committed Snapshot On” Option under database properties.

Install a JDBC Driver

database relies on the JDBC API. See the list of certified databases. If you choose a database that's not in this list you do so at your own risk.

1. The  download package comes with pre-installed drivers. For example:
   • the HSQLDB.jar file is located in WEB-INF/lib in the frevvo.war.

   • the SQL Server JDBC Driver - this driver (mssql-jdbc-7.2.2.jre11.jar ) is included in the frevvo tomcat bundle in the <frevvo-home>\frevvo\tomcat\lib directory.

     At this time, frevvo only supports the v7.2.2.jre11 version of the SQL Server JDBC driver.  This version of the driver is included in the frevvo tomcat bundle.

2. If you don't find what you need pre-installed you will need to locate a driver compatible to your database. Usually you can download your driver from the internet. Try one of these locations: 
   • MySQL - 8.0.x or later is recommended if you are using MySQL 5.6+
   • Oracle
     • If you are using Oracle12c as your database, the jdbc driver must be the version 7 ojdbc.jar which is certified for JDK 7 and 8 for the Insight Data batch process to function properly. 
     • If you are using Oracle 11g, continue to use the the ojdbc6 driver version 11.2.0.3+  which is certified for JDK 6, 7 and 8. Remember JDK 6 and 7 are no longer supported by frevvo.
3. Once you have the driver you need, copy it to <frevvo-home>/tomcat/lib.
   1. The <frevvo-home>\tomcat\logs\frevvo.log file will report an error if you do not copy the JDBC driver to lib directory. The verbiage may differ depending on the driver and database. For example, the error for MySQL is "Cannot load JDBC driver class 'com.mysql.cj.jdbc.Driver". Starting  without the correct jdbc driver displays an HTTP 404 error. Copying the correct jdbc driver to the <frevvo-home>/tomcat/lib directory should resolve the issue.
      
   2. It is also appropriate to copy the driver into any location that is in the CLASSPATH of your tomcat installation. Another location would be <CATALINA_HOME>/lib.

Transferring Your frevvo Data from HSQL to a Production Database

The bundle includes an HSQL embedded database. If you use the HSQL database during your trial period, you cannot migrate the data (user, roles, applications) automatically from HSQL to your production database. Once your production database is in place, you must manually: 

1. Create your production tenant.
2. Use CSV Upload of Users andRoles to move your users/roles to the tenant.
3. Download and upload the applications from designer user accounts in the trial database to the designer users in the new database.