Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

These steps are required when you convert from a demo/trial

server installation to a production installation.


While you are demo-ing

you do not need to do the Database Setup steps discussed below.


 server requires an SQL database for storing users and form submissions. The following SQL databases have been certified:


server may function with other SQL database types but only the above set has been certified.

  • The default HSQLDB is ONLY sufficient for demo/trial versions of
    . All production
    users MUST switch their
    software to a production quality database.
  • You cannot migrate the data (user, roles, applications) automatically from HSQL to your production database. See this topic for the manual procedure details.

The following steps describe how to change the underlying database from the demo/trial HSQLDB to a production quality SQL database. The database configuration file, server.xml is located in <frevvo-home>/frevvo/tomcat/conf directory.


On This page:

Table of Contents


  1. First, 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:


Code Block
		SQLSERVER Resource
	  <Resource auth="Container"
		validationQuery="select 1"

Database configuration has been removed from the <frevvo-home>\tomcat\conf\Catalina\localhost\frevvo.xml file. It is now done in the C:<frevvo-home>\tomcat\conf\server.xml file. Also, notice the database resource name has been changed to jdbc/sharedfrevvoDS.  When you configure your database, make the changes to the v7.0 server.xml. Do not copy configured sections from a frevvo.xml of a previous release into the v7.0 server.xml file.

Image Added

Configure the frevvo database


  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.


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.


If you are using SQL Server, it is recommended that you append the sendStringParametersAsUnicode property with a value of false to your database connection URL. This property will improve performance. You can find more information about this property on this Microsoft website. If you do not see the property, when configuring the Connection URL to your database, add it.

Code Block

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. 


Code Block
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 READ SUBMITTED SNAPSHOT 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

    Code Block
    ALTER DATABASE <your frevvo database schema> - replace <your frevvo database schema> with the name of your frevvo database schema 
  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. You can use any relational database as long as you have a JDBC driver for that database, however. See the list of certified databases. If you choose a database that's not in this list you do so at your own risk.


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


Once you have the driver you need, copy it to <frevvo-home>/tomcat/lib.


It is also appropriate to copy the driver into any location that is in the CLASSPATH of your servlet container. In a tomcat installation another . Another location would be <CATALINA_HOME>/lib.