Versions Compared

Old Version 11

changes.mady.by.user Former user

Saved on

compared with

New Version 12

changes.mady.by.user Former user

Saved on

Key

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

These steps are required when you convert from a demo/trial server installation to a production installation.

Tip

While you are demo-ing you do not need to do the Database Setup steps discussed below.

Your  server requires an SQL database for storing users and form submissions.

Info

frevvo only supports/certifies the  running in the Apache Tomcat container. Refer to our Supported Platforms for the list of Application Servers and databases supported/certified by frevvo.

Tip
  • If you are using Oracle12c as your database, the jdbc driver must be version 7 ojdbc.jar for the Insight Data batch process to function properly. Refer to the Install a JDBC Driver topic for the details.
  • It is recommended practice to use a named user (schema) account with the proper privileges when connecting to Oracle databases. The built in SYSTEM user account will not work.

The default HSQLDB is ONLY sufficient for demo/trial versions of . All production users MUST switch their software to a production quality database.

Warning
  • 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.

Column
width240px

On This page:

Table of Contents
maxLevel1

...

It is recommended practice to use a named user (schema) account with the proper privileges
  • The sendStringParametersAsUnicode=false property has been added to the SQL Server database URL. This property is needed for better performance. Refer to Configure the Connection URL for more information.
Warning

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.

  • Notice the database resource name has been changed to jdbc/sharedfrevvoDS
  • The sendStringParametersAsUnicode=false property has been added to the SQL Server database URL. This property is needed to ensure better performance.

When you configure your database, make the changes to the server.xml in the tomcat bundle that you are installing . Do not copy configured sections from a frevvo.xml of a previous release into the newly installed server.xml file.

Tip
Tip

It is recommended practice to use a named user (schema) account with the proper privileges when connecting to Oracle databases. The built in SYSTEM user account will not work.

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.

Info
  • Where did the SQL scripts go? The server no longer needs the SQL scripts that used to be in <frevvo installdir>\frevvo\data\sql. The server automatically creates the necessary tables at first 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.

...

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.

Info

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. If you do not see the property, when configuring the Connection URL to your database, add it.

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. 

...

  • the HSQLDB.jar file is located in WEB-INF/lib in the frevvo.war.

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

    Warning

    At this time, frevvo only supports the v6.1.0.jre8 version of the SQL Server JDBC driver.  This version of the driver is included in the frevvo tomcat bundle. v6.2+ of the driver may cause an issue with downloading larger attachment files from the submission repository. v6.2+ versions should not be used until further notice.

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 - 5.1.45 or later is recommended if you are using MySQL 5.6+

  • Oracle

Info

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

...