111
The Database Connector is a web application and can be deployed under any Servlet container or run in a simple Standalone mode. The connector relies on the JDBC API. You can use any relational database as long as you have a JDBC driver for that database.
These instructions apply to Cloud and in-house customers.
On this page:
Installation Steps
The Database Connector can be configured to run in:
- A servlet container such as the frevvo-tomcat in-house bundle. We recommend this for in-house customers.
- Standalone mode - Recommended for cloud customers as no additional servlet container is needed. This mode is also useful for in-house customers who want to run the connector on a different server than the server installation.
Follow these instructions:
- frevvo-tomcat bundle Instructions or Standalone Instructions
- Connector Configuration Instructions - detailed steps to integrate the connector with your database.
Cloud customers must verify connector connectivity to the frevvo Cloud Server.
frevvo-tomcat bundle Instructions
These instructions assume that your frevvo-tomcat bundle is already installed and running successfully.
- Stop your server.
- Download the database.war into <frevvo-home>\tomcat\webapps.
- Install the JDBC driver
Start your server
- Browse the status url http://<host>:<port>/database/status
If the status returns failures or disabled:
Review the previous installation steps.
See starting and testing the connector installation for troubleshooting.
When the status returns Passed for each queryset, you are ready to configure the Database Connector.
Standalone Instructions
- Review Supported Platforms. Verify that the certified version of Java is installed and the Java_Home environment variable has been configured .
- Download the Database Connector Standalone bundle.
- Unzip the database.zip file to a location of your choice. We will refer to this directory as <db-home>
- Install the JDBC driver
- You can start the connector using plain java command or execute one of the files in this directory to install the DB Connector as a Windows service or *nix console instance:
- Choose one of these methods to start the connector:
- Method 1: Using java in a command window
- Navigate to the <directory where you unzipped the database.zipfile>
- Type java -jar database.war
- Method 2: for Windows OS
- Install the DB Connector as a Windows service by double clicking the Install-Service.bat file. Click the Start DBConnector Service.bat to start the service.
- Method 2 for *nix OS
- Execute the DB Connector.sh shell script for *nix operating systems.
- Method 1: Using java in a command window
- Choose one of these methods to start the connector:
- Test the connector installation by copying this URL directly into your browser:
http://localhost:8081/database/status - Note the standalone connector runs on port 8081 by default. - When the status returns Passed for each queryset, you are ready to configure the Database Connector.
If the status returns failures or disabled Connector Test failed then:
- Review the previous installation steps
- See starting and testing the connector installation for more detailed instructions and common problems.
Install a JDBC driver
The connector relies on the JDBC API. You can use any relational database as long as you have a JDBC driver for that database.
You MUST use a JDBC4 type driver, version 5.1.26 or later.
The download package comes with the pre-installed drivers listed below.
MS SQL driver
If you are running the Database Connector in Standalone mode, this driver is embedded in the database.war. However, you MUST copy the sqljdbc.jar to the <frevvo-home>/tomcat/lib directory if you are deploying the connector in the tomcat bundle
- DERBY driver
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. Refer to the Using the jTDS driver topic for information if you are using the jTDS SQL Server driver.
Once you have the driver you need, copy it to:
- <frevvo-home>/tomcat/lib if you are deploying the connector in the tomcat bundle
- <directory where you unzipped the Database Connector Standalone bundle \database-connector-2.5.x\lib
- When running the Database Connector in Standalone mode, the MSSQL driver is embedded in the database.war. However, you MUST copy the sqljdbc.jar to the <frevvo-home>/tomcat/lib directory if you are deploying the connector in the tomcat bundle
- There are some special considerations when defining datasources if you are using the jTDS driver. The validationQuery must be included in the resource definition. This query is used during the validation sequence.
- 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 location would be <CATALINA_HOME>/lib.
DB Connector Quick Demo
The BIRT (ClassicModels) and myStore querySets are preloaded with in-memory Derby databases and test data. This make it very easy to try out the connector. No configuration is necessary.
Follow the steps below to deploy the connector in the the tomcat bundle and you can get started very quickly
Review Supported Platforms. Verify that the certified version of Java is installed and the Java_Home environment variable has been configured .
Download the Database Connector warfile. Rename the file to database.war
Extract the tomcat bundle zipfile to a location of your choice. We will refer to this directory as <frevvo-home>.
Copy database.war to <frevvo-home>\tomcat\webapps.
Start the Insight server. and then start Live Forms.
- Test the connector installation by copying this URL directly into your browser:
http://localhost:8082/database/statusAfter performing these steps you will have:
- Successfully installed the database connector and retrieved data from the built-in test database
- Create a tenant.
- Create a designer user in the tenant
- Download the Database Connector Application and upload it to the designer user for some example forms that demonstrate the power of the Database Connector using built-in databases.