...

<!-- 
		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)

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;"

...

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"/> 

...

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.

     Warning
     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

...