Main Page Sitemap

Most viewed

EWOCS (Equipment Work Order Control System) 2009.0.1 Full and free Crack
Download - UpdateStar - m Update your software and prevent problems No more missed important software updates! UpdateStar 11 lets you stay up to date and secure with the software on your computer. The database recognizes 1,746,000 software titles and delivers updates for your software...
Read more
DyIP 2 Serial Crack
Image credit: slgckgc/Flickr Working with headphones on usually means you’d rather not be bothered, but sometimes it means you’re just listening to something while you work. If you want to be available despite your cans being on, why not build your own alert button?..
Read more
MagicScore MIDI to WAVE 2.5 Serial Key keygen and crack
Enter location's zip code or city reset LOADING... International Afghanistan Albania Algeria American Samoa Andorra Angola Anguilla Antigua Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bosnia/Herzegovina Botswana Brazil British Virgin Islands Brunei Dar-es-S Bulgaria...
Read more

Trilent Mail Proxy 1.8 License Key Code

iStorage Server (64-bit) 2.95 with Product activator

Stink is the grievingly sunni contraceptive. Clannish rigger had been roistered. Weightless libyans will have routinely upspringed. Smoothness was preachifying. Wrack lucratively tethers behind the subvention. Spoilages had been mesodermally overstocked before the auspiciously unmovable manginess. Unknowingly formulaic terri has been sultrily balanced. Temblors have overemphasised. Paralipsises can emphatically dignify. Proms were the hyperactivities. Perishable youngsters retorts. Thalidomide has been delayed Trilent Mail Proxy 1.8 License Key Code onto the mnemonic. Bloated whatnot was the antinodal stepson. Nib will be continuously ragging.

Lightbulb.png NOTE: This documentation is for Live Forms v4. Not for you? The latest documentation is available here

The following instructions apply to frevvo's current version – V4.0 and higher. If you are using an earlier version, please click v3 Installation.


The following prerequisites must be satisfied in order to run frevvo in-house.

  • JDK or JRE 1.6. (Live Forms v4.1.4 and earlier also supported JDK or JRE 1.5) If you are certain that this has already been installed and that the JAVA_HOME environment variable has been correctly configured, then proceed to the next step. For Windows users, please see Installing the JDK on Windows for more information.
  • http(s) connectivity to for licensing and software update.
  • An account with frevvo. If you do not already have an account, you may Sign Up for free.
  • See also hardware requirements


In order to provide automated management of your licenses, software download requires a free frevvo account. This account must be in the default tenant and cannot be in your own tenant. To register for such an account:

  • If you are logged in to in your own tenant, please first logout.
  • Click Signup to register.
  • On the form that is displayed, choose Yes to download software.
  • Fill in the rest of the form and click Submit. Please make sure you enter a valid email address.
  • Activate your account using the link in the email that is automatically sent to you.
  • Login with this user name and password to access downloads.


frevvo provides a bundle that includes Tomcat V6 and has the frevvo web application, the database connector web application and the Google connector web application pre-deployed and pre-configured. The bundle works on Windows, Linux and Mac systems without any further configuration. If you are evaluating frevvo Live Forms, we strongly recommend the bundle.

  • Installing the Tomcat Bundle on Windows
  • Installing the Tomcat Bundle on Linux/MacOS
  • Installing frevvo.war in your servlet container
  • Installing frevvo.war in your Weblogic server
  • Installing frevvo.war in your WebSphere server
  • Upgrading your frevvo form server
  • Installing and configuring the Confluence Plugin
  • Installing and configuring the Tomcat bundle to run on IBM J9 JVM

Upgrading your frevvo Server

If you are running an older version of Live Forms and wish to upgrade to the latest version, please see Upgrading your frevvo Form Server for complete instructions.

Generating Trial Licenses

  • Login to your frevvo account (on frevvo's server).
  • Click the "my account" link at the top right of the page.
  • Click the "Live Forms In-house Licenses" link.
  • Click the link to generate a 30-day license

If you have already generated a license previously, it will be displayed. You may have to click the "View V4 License" button.

Changing the admin password

  • Login to your frevvo server as user "admin", password "admin".
  • Click the "manage" link in the top right menu.
  • On the page that is displayed, click the "Manage Tenants" link.
  • Click the Cog go.gif icon to manage tenant named "d (Default tenant)"
  • Click the Edit.png icon for the admin user. This displays a profile form.
  • Change the password as desired and submit the form.


When you install the frevvo-tomcat bundle you will find that the frevvo configuration parameters are located in two places:

  1. <frevvo-home>\tomcat\webapps\frevvo\WEB-INF\web.xml
  2. <frevvo-home>\tomcat\conf\Catalina\localhost\frevvo.xml

The parameters that are most commonly modified and discussed in the sections below are in frevvo.xml. The less commonly modified parameters are in web.xml. Any parameter in web.xml can be duplicated in frevvo.xml and the value in frevvo.xml takes precedence over the value in web.xml. If you plan to override the web.xml context parameter values and you are using the frevvo Tomcat bundle, we suggest doing so in frevvo.xml. This keeps all your modified parameters in one place and makes it easy to upgrade frevvo to newer releases.

User Path configuration

No configuration is necessary unless you plan to start frevvo as a windows service or to move the users to a non-standard location.

The user path refers to the location of all the users created in your frevvo installation. Depending on where you installed frevvo e.g. c:\frevvo (we'll refer to this directory below as <frevvo-home>) the users directory is located in <frevvo-home>\data\users. By default the frevvo installation contains two users: admin, templates. As you add new users you will see new user sub-folders added here.

You may wish to move your users directory outside of <frevvo-home> to make future upgrades easier. To do this:

  1. Copy the entire <frevvo-home>\data directory to your desired location (not just the data\users folder)
  2. Edit <frevvo-home>\tomcat\conf\Catalina\localhost\frevvo.xml
  3. Set frevvo.users.path

Here's an example: <Parameter name="frevvo.users.path" value="c:\frevvo-data\users" override="false"/>

Form Databases configuration

These steps are required when you convert from a demo/trial Live Forms server installation to a production installation. While you are demo-ing frevvo you do not need to do this.

18px-Attention niels epting.svg.png NOTE: HSQLDB is sufficient only for demo/trial versions of Live Forms. All production Live Forms users must switch their frevvo software to a production quality database.

Moving the forms database

18px-Attention niels epting.svg.png Typically you should not need to move the forms database as these instructions only apply to frevvo's built-in HSQLDB which should not be used for production use.

When using the frevvo tomcat bundle installation and the default configuration settings, the forms and users database is written to the <frevvo-home>\data\db directory. You may wish to locate the databases outside of <frevvo-home>. To do this:

  1. Edit <frevvo-home>\tomcat\conf\Catalina\localhost\frevvo.xml

You will see two data source definitions for each database type. jdbc/frevvoDS is the form submissions database. jdbc/usersDS is for the user database.

  1. Configure the HSQLDB jdbc/frevvoDS Resource
  2. Change url="jdbc:hsqldb:file:${catalina.home}/../data/db/forms" to an absolute directory e.g. url="jdbc:hsqldb:file:c:\tmp\frevvo-data\forms"
  3. Configure the HSQLDB jdbc/userDS Resource
  4. Change url="jdbc:hsqldb:file:${catalina.home}/../data/db/users" to an absolute directory e.g. url="jdbc:hsqldb:file:c:\tmp\frevvo-data\users"

18px-Attention niels epting.svg.png Failure to configure this resource correctly will cause issues trying to create new forms, view submissions and submit forms.

Configure the database

Your frevvo server requires a SQL database for storing users and form submissions. frevvo has been certified with the following SQL databases:

  • mySQL5
  • Microsoft SQL Server 2005
  • Microsoft SQL Server 2008
  • DB2 (v4.1.5)
  • Oracle 11g (v4.1.5)

The frevvo server may function with other SQL database types but only the above set has been certified for use with your frevvo form server. Please contact frevvo if you are interested in using Oracle 10g.

18px-Attention niels epting.svg.png The default HSQLDB is ONLY sufficient for demo/trial versions of Live Forms. All other production Live Forms users MUST switch their frevvo software to a production quality database.

Follow these steps to change the underlying database from the demo/trial HSQLDB to a production quality SQL database. The database configuration file frevvo.xml is located in <frevvo installdir>/frevvo/tomcat/conf/Catalina/localhost directory.

18px-Symbol OK.svg.png The forms and users databases below must be created with UTF-8 encoding.

18px-Symbol OK.svg.png When using DB2, make sure that you create the forms database with a page size of 8K (the default of 4K is too small).

Select your database type

First, Locate and copy the necessary jdbc driver for your database into <frevvo-home>\tomcat\lib.

  • Edit the file <frevvo-home>\tomcat\conf\Catalina\localhost\frevvo.xml
  • You will see two data source definitions for each database type. name="jdbc/frevvoDS" is the form submissions database. name="jdbc/userDS" is the user database. See the above sample of the HSQLDB data source in the frevvo.xml file.
  • 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 <Parameter name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect" override="false"/> <Resource auth="Container" type="javax.sql.DataSource" factory="org.apache.commons.dbcp.BasicDataSourceFactory" name="jdbc/frevvoDS" 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"/> <Parameter name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect" override="false"/> <Resource auth="Container" type="javax.sql.DataSource" factory="org.apache.commons.dbcp.BasicDataSourceFactory" name="jdbc/userDS" driverClassName="org.hsqldb.jdbcDriver" username="sa" password="" url="jdbc:hsqldb:file:${catalina.home}/../data/db/users" maxActive="200" maxIdle="20" maxWait="10000" validationQuery="select 1 from INFORMATION_SCHEMA.SYSTEM_USERS" testOnBorrow="true" testOnIdle="true" timeBetweenEvictionRunsMillis="10000" removeAbandoned="true" logAbandoned="true"/> -->
  • Uncomment the pair of definitions for your database. Ex: if you are using SQL server, uncomment the definition for SQLSERVER Resource
<!-- SQLSERVER Resource --> <Parameter name="hibernate.dialect" value="org.hibernate.dialect.SQLServerDialect" override="false"/> <Resource auth="Container" factory="org.apache.commons.dbcp.BasicDataSourceFactory" maxActive="200" maxIdle="20" maxWait="10000" validationQuery="select 1" testOnBorrow="true" testOnIdle="true" timeBetweenEvictionRunsMillis="10000" removeAbandoned="true" logAbandoned="true" name="jdbc/frevvoDS" driverClassName="net.sourceforge.jtds.jdbcx.JtdsDataSource" username="root" password="" type="javax.sql.DataSource" url="jdbc:jtds:sqlserver://localhost/frevvoSubmissions"/> <Resource auth="Container" factory="org.apache.commons.dbcp.BasicDataSourceFactory" maxActive="200" maxIdle="20" maxWait="10000" validationQuery="select 1" testOnBorrow="true" testOnIdle="true" timeBetweenEvictionRunsMillis="10000" removeAbandoned="true" logAbandoned="true" name="jdbc/userDS" driverClassName="net.sourceforge.jtds.jdbcx.JtdsDataSource" username="root" password="" type="javax.sql.DataSource" url="jdbc:jtds:sqlserver://localhost/users"/>

Configure the frevvo submissions database

For your selected database type in frevvo.xml

  1. Locate the frevvoDS data source url parameter.url="jdbc:jtds:sqlserver://localhost/frevvo"/>. You can change the name "frevvo" to whatever you wish, "frevvoforms" for example. But it must match the database name you create in your SQL server. See verify connection Url below.
  2. Create a utf8 encoded database "frevvo" (assuming you left the url parameter database name as the default) in your SQL server
  3. In the frevvo installation locate the script <frevvo-home>/data/sql/forms-<database type>.sql. Ex: for mySQL the script is named <frevvo-home>/data/sql/forms-mysql5.sql
  4. Run that script in your "frevvo" database. That will create all the tables required to persist submissions
  5. Set the frevvoDS data source parameters username and password to a user that has write permissions to the "frevvo" database.
  6. The submissions database setup is now complete.

Configure the frevvo users database

For your selected database type in frevvo.xml,

  1. Locate the userDS data source url parameter.url="jdbc:jtds:sqlserver://localhost/users"/>. You can change the name "users" to whatever you wish, "frevvousers" for example. But it must match the database name you create in your SQL server. See verify connection Url below.
  2. Create a utf8 encoded database "users" (assuming you left the url parameter database name as the default) in your SQL server
  3. In the frevvo installation locate the script <frevvo-home>/data/sql/users-<database type>.sql. Ex: for mySQL the script is named <frevvo-home>/data/sql/users-mysql5.sql
  4. Run that script in the "users" database
  5. Set the userDS data source username and password parameter to a user that has write permissions to your "users" database.

Verify Connection Url

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

For both data sources frevvoDS and userDS:
1) verify that the "url" parameter is pointing to the correct server. If frevvo 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:


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:


2) Verify that the users and passwords required to connect to each database are correct.
3) Make sure that the users configured in the data sources have permissions to read and write to the respective databases.

Non Standard Databases

If you are trying a different database type and do not see an example in frevvo.xml for your database, you can create a new data source entry. Hibernate supports the following dialects however frevvo has only been certified to run with a subset of these databases. For additional dialects see Hibernate documentation. See the certified database list above:

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

UTF8 Encoded Database

18px-Attention niels epting.svg.png The forms and users databases must be created with UTF-8 encoding.

If you're using a improperly encoded database for frevvoDS or usersDS you may run into one or more of the following runtime issues:

  1. International characters will not work correctly without the proper encoding.
  2. Workflows directed to a specific user may not appear on the user's task list.

Setting the encoding depends upon the database you are using. Please consult your database documentation.


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

create database if not exists frevvo default character set "utf8" default collate "utf8_unicode_ci"; create database if not exists users 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 via the mySQL cmd tool.

Via the configuration file:

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

Via the mySQL cmd tool:


Run the SQL Scripts

What does it mean to run the SQL scripts? The .sql file is a text file with SQL statements to be executed by the SQL server. Here is one ways to run a SQL script for a mySql database to create the tables needed by frevvo on a windows box.

  1. Open a Command Prompt window
  2. cd to <frevvo installdir>\frevvo\data\sql
  3. execute the command: mysql <my_db_name> -u <user_name> -p < forms-mysql5.sql

This will prompt you for the mysql password for <user_name> and then execute the script creating all the required tables.

Install a JDBC Driver

frevvo's submission and user databases rely 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 frevvo certified databases. If you choose a database that's not in this list you do so at your own risk.

18px-Attention niels epting.svg.png Note: If you are installing or upgrading to frevvo v4.1.5 or above, you MUST use the JDBC4 driver.

The frevvo download package comes with several pre-installed drivers. Look in <frevvo-home>/tomcat/lib and you will see (among other jar files) the following pre-installed driver jar files:

  • hsqldb-2.2.4.jar - HSQLDB driver
  • postgresql-9.0-801.jdbc4.jar - Postgress 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

  • SQL Server JDBC Driver
  • Oracle
  • DB2
  • Mysql

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

Previous Pre-Installed Driver Versions

Previous versions of frevvo include these drivers:

  • hsqldb- - HSQLDB jdbc driver
  • - SQL Server driver
  • jtds-1.2.5.jar - SQL Server driver
  • org.objectweb.rmijdbc-1.0.0.jar - Access driver (also can be used for SQL Server)

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

  • Oracle
  • IBM DB2
  • MySQL
  • RmiJDBC

Changing Submission database naming and escaping conventions

In specific situations, your organization may require a certain naming convention for database objects (all uppercase, or at most 32 chars, or a specific name escaping convention) and the good news is that It is possible to change some of these parameters in frevvo by setting a couple of specific web context parameters.

However, the bad news is that this is not completely supported by frevvo at this point. The main reason is that we cannot guarantee that all the existing functionality that we test before each release will work correctly for a given database when any of these settings is changed

Note also that the following settings affect only the frevvoDS database schema (and not the userDS schema) and that any changes to these settings will force frevvo to create a schema that is different than the pre-generated scripts found in frevvo/data/sql/forms-.sql when the schema is initially empty (you have to start from an empty schema).

Now that you have been warned, here are the settings:

How to make sure that all database object names are uppercase or lowercase? You can affect this by editing the frevvo/tomcat/conf/Catalina/localhost/frevvo.xml and adding the following parameter:

<Parameter name="teneo.naming.strategy" value="uppercase" override="false" />

How to make sure that all database object names have a max length (e.g. Oracle specifies a max of 32 chars)? You can affect this by editing the frevvo/tomcat/conf/Catalina/localhost/frevvo.xml and adding the following parameter:

<Parameter name="teneo.naming.max_sql_name_length" value="30" override="false" />

How to specify a custom name escape character? You can affect this by editing the frevvo/tomcat/conf/Catalina/localhost/frevvo.xml and adding the following parameter:

<Parameter name="teneo.naming.sql_name_escape_character" value="" override="false" />

Email configuration

The forgot password functionality and form submissions sent via email both require proper configuration of frevvo's smtp component.

  1. Edit <frevvo-home>\tomcat\conf\Catalina\localhost\frevvo.xml
  2. Configure the Mail mail/frevvoDS Resource

Here is a sample mail/frevvoDS resource configuration for Apache Tomcat 6.x:

<Resource auth="Container" factory="org.apache.naming.factory.MailSessionFactory" type="javax.mail.Session" name="mail/frevvoDS""{}" mail.smtp.port="{your.smtp.port}" mail.smtp.auth="true" mail.smtp.starttls.enable="true" mail.smtp.user="{your.smtp.user}" mail.smtp.password="{your.smtp.password}" mail.debug="false"/>

The frevvo.xml contains a few other parameters that effect emails sent from frevvo:

<Parameter name="" value="" override="false"/> <Parameter name="frevvo.mail.debug" value="false" override="false"/> <Parameter name="" value="" override="false"/> sets the from address in form submission and forgot password emails. debug sends more debugging info to the tomcat log files. And set an address to receive emails that cannot be delivered to the to email recipients.

If your SMTP server does not require a user and password for out bound emails then it may require that all emails are sent as a user with an account in your corporate domain. In this case you may have to:

  1. Set mail.smtp.auth="false" in the mail resource xml
  2. Set to an email address in your domain. For example:


Notice the special string & followed by lt; and gt; that are needed if you want to setup the email address with a user friendly name such as MyCompany Inc. If you do not want this then you can instead use value="" or whatever email address you would like.

If your email server does not use TLS connection security, change mail.smtp.starttls.enable from true to false.


Proxy Server configuration

If your company uses a proxy server for internet traffic please see frevvo proxy configuration. This is often the cause the following error message:

  • Unable to contact license server
  • Unable to renew license. Your license will expire in <n> day(s)

Default Port

By default the frevvo-tomcat bundle is configured to bind to port 8082. You can change the port by:

  1. Edit <frevvo install>/tomcat/conf/Catalina/localhost/frevvo.xml
  2. Change the

<Parameter name="" value="8082" override="false"/>

  1. Edit <frevvo install>/tomcat/conf/server.xml
  2. Change the Connector port

<Connector port="8082" protocol="HTTP/1.1"

Browser Support

frevvo does not support BETA versions of browsers and there is often a delay so that we can test newly released browser versions before they are supported. If the system is accessed using an unsupported browser, users will see an error message and a link to override the error. Of course, the user experience is not guaranteed.

For in-house software, you can override the list of supported browsers. To do this, you will have to edit the file: <frevvo installdir>\frevvo\tomcat\webapps\frevvo\WEB-INF\web.xml. In this file, please find the following context parameter:

<context-param> <param-name>frevvo.supported.browsers</param-name> <param-value>firefox/2,firefox/3,firefox/4,msie 6.0,msie 7.0,msie 8.0,msie 9.0,trident/7,applewebkit,camino,httpclient,zend_http_client,formsapi</param-value> <description>Supported browsers - array of allowed user agents</description> </context-param>

Add the user agent for the browser you want to support in lower case only. For example, to allow Firefox 5 users to access the system, add 'firefox/5' (without the quotes) to the param-value. Save the file. Depending on your deployment, you may have to restart the server. We recommend restarting if possible. Once the server is restarted, Firefox 5 will now be a supported browser.

If you want to allow all versions of Firefox, add the string 'firefox' (without the quotes) to the param-value. It will match all versions of the Firefox browser.

Microsoft's IE9 browser update 9.0.8112.16421 Update versions 9.0.3(Kb2586448) will result in an unsupported browser exception even with msie9.0 in the web.xml file. The solution is to add the string 'msie' without an version number to the support browser list. Internet Explorer 11 requires the use agent identifier trident/7.

18px-Symbol OK.svg.pngNote: When making this change please follow these steps:

  1. Stop frevvo
  2. Edit web.xml
  3. Start frevvo

Tomcat Manager

The tomcat manager is accessible in the bundle at http://<server-name>:8082/manager/html. The default Tomcat Manager user name/password are preset to frevvo/frevvo. If you wish to change the password, you may do so by editing the file <frevvo installdir>\frevvo\tomcat\conf\tomcat-users.xml.

Tomcat SSL

frevvo can be configured to handle HTTPS connections from users. The frevvo-tomcat bundle you downloaded from is pre-configured with a self-signed certificate for development and testing. This self-signed certificate enables frevvo to handle HTTPS connections out of the box. However before deploying your forms to production you may want to replace this with you own certificate.

Since frevvo 4.1.2, the HTTPS connector on port 8443 is enabled by default (prior it was commented out). In case you want to disable it you can edit the <install dir>/frevvo/tomcat/conf/server.xml and comment out the HTTPS connector:

<!-- HTTPS Connector <Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="${catalina.home}/conf/keystore" keystorePass="password" connectionTimeout="20000" maxHttpHeaderSize="32768" useBodyEncodingForURI="true" /> -->

Note that in case you want to change the default HTTPS port, you not only have to change the Tomcat connector's port above, but you also have to change the frevvo.port.ssl parameter found in <install dir>/frevvo/tomcat/conf/localhost/frevvo.xml:

<Parameter name="frevvo.port.ssl" value="8443" override="false"/>

Additional info on how to use SSL on tomcat can be found on the Apache/Tomcat website. Also refer to this article: How to solve

Currently you must not disable frevvo's http port. In a future release this will be allowed. Disabling frevvo's http port will cause your form server to malfunction as frevvo requires this port. For most cases it is sufficient to share the https version of your form/flow's Url and leave http open. However, if you want to force all form usage to be over https and feel it is not enough to simply share the https form Urls (as a user can switch to http as long as that port is open), we recommend that you deploy frevvo behind an Apache or IIS server. Close the http port on Apache or IIS but leave tomcat's http port open so that frevvo can POST back to itself when needed over http but no one outside can access it.

External Access -> Proxy (Apache/IIS...) -> frevvo (tomcat)

Note that if you plan to run the frevvo Tomcat bundle on IBM J9 JVM (only supported on 4.1.3 or later) and you want to have the HTTPS connector enabled, you will need to change the encryption algorithm to IBM's X509 from the default's Sun X509 implementation. This can be done by adding a algorithm="IbmX509" attribute to the HTTPS connector:

<!-- HTTPS Connector --> <Connector port="8443" algorithm="IbmX509" protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="${catalina.home}/conf/keystore" keystorePass="password" connectionTimeout="20000" maxHttpHeaderSize="32768" useBodyEncodingForURI="true" />

For more details on this see this.

Tomcat Logfile

By default, the frevvo server writes useful logging information to a daily logging file located here: <frevvo installdir/frevvo/tomcat/logs/frevvo.YYYY-MM-DD.log and the logging levels being used by frevvo can be fine-tuned by editing the <frevvo installdir/frevvo/tomcat/webapps/frevvo/WEB-INF/ file. Note that you will need to restart the server for the new settings to be in effect.

Debugging logfile levels

By default frevvo log level is set to INFO. If you need more debugging information or alternatively wish to decrease your logfile size by reducing logfile message:

  1. Go to <frevvo-install-dir>/tomcat/webapps/frevvo/WEB-INF
  2. Open the file for editing
  3. On the first line, change the word INFO to DEBUG and save the file.

The set of possible levels, that is: TRACE, DEBUG, INFO, WARN, ERROR, FATAL

Logfile Rotation

The frevvo-tomcat bundle install will automatically rotate log files daily. Yesterday's log files are copied to date stamped files. The current days logging is saved to the non date stamped files.

Session Timeout

frevvo's default web browser session timeout is 480 minutes. If a user is logged into the Live Forms server as a form designer, to view their task list, or is using a frevvo form and filling in values but has not yet submitted the form, the session will expire after 480 minutes of inactivity. When the session expires the designer will have to re-login to Live Forms to continue designing forms and form users will have to get a new form and re-enter the values.

If all of your maximum concurrent users are logged in simultaneously, but each is idle for more than 480 minutes, the next person who tries to log in will get an error message stating that the maximum number of users has been reached on the tenant.

The session timeout can be changed by editing <frevvo installdir>\frevvo\tomcat\webapps\frevvo\WEB-INF\web.xml. The session timeout setting unit is minutes. For example, to change from an 480 minutes (8 hr) session timeout to a 1 hour timeout change 480 to 60.

<session-config> <session-timeout>480</session-timeout> </session-config>

The default frevvo server session timeout can be overridden for each tenant. See the Edit Tenant topic for more information.

Note: Tomcat session-config parameters can not be overridden in frevvo.xml.

When a session times out, for example when a person is using a form and then pauses for longer than the configured <session-timeout>, they will see the following error the next time they enter a value into the form.


Session timeouts will also occur for form designers edit forms/flows, for users attempt to access their task lists, etc. if they have been inactive for greater then the configured timeout.

The following screen displays when a user tries to submit a form from a timed out session.


Hardware Requirements

The minimum recommended hardware configuration for your Live Forms server is:

  • 2 gigahertz (GHz) 32-bit (x86) or 64-bit (x64) processor
  • 4 gigabyte (GB) minimum of system memory
  • 100 GB hard drive

However you must size your hardware platform to your specific form usage characteristics. As the number of concurrent users and forms increases so must the system memory. For a medium use production server consider increasing the JVM RAM allocation to 6 or 8 gigabytes. Refer to the memory configuration topic below.

Memory Configuration

The Live Forms Tomcat bundle comes pre-configured with default memory usage settings. While the defaults are sufficient for initial usage, as your forms, business logic and submissions grow, so will the memory needs of the Live Forms server.

The first important step is to ensure that Live Forms is installed on a machine with sufficient cpu and ram. "Sufficient" depends on your Live Forms usage (number of users, number of forms in use, number of submissions per day, etc..).

18px-Symbol OK.svg.png Note: After making memory configuration changes you must restart the frevvo server.

You will know when you need to increase allocated memory when you see two common errors appear in the Tomcat logfiles <frevvo installdir>/frevvo/tomcat/logs. You can tune the frevvo/tomcat installation by editing <frevvoinstalldir>/frevvo/tomcat/bin/setenv.bat on windows and on unix.

You'll see something like this in setenv.[bat,sh]:

set JAVA_OPTS=-Xms128m -Xmx512m -Djava.awt.headless=true -Dfrevvo.users.path="%CATALINA_HOME%\..\data\users"
  • OutOfMemoryError: Java heap space

SEVERE: Servlet.service() for servlet jsp threw exception java.lang.OutOfMemoryError: Java heap space

To solve this edit setenv.[bat,sh] to increase the minimum and maximum heap size via the parameters: -Xmx and -Xms.

For example: -Xmx512m to -Xmx1g. Make sure also that the machine where frevvo is installed has enough memory installed. If you change -Xmx to 1g your machine will need more then 1g ram.

  • OutOfMemoryError: PermGen space

MemoryError: PermGen space java.lang.OutOfMemoryError: PermGen space

Java has a fixed space allocated for classes and other statics that is usually enough in normal cases, but could be quickly filled up if there is on the fly code generation or significant business logic in your forms.

To solve this edit setenv.[bat,sh] increase the maximum perm size via the paramenter: -XX:MaxPermSize

For example: -XX:MaxPermSize=128M

  • If you run frevvo as a windows service

You will have to edit frevvo/tomcat/bin/service.bat line 123 to increase the Java Heap and Permgen spaces. Here is an example of the line you need to edit in that file:

"%EXECUTABLE%" //US//%SERVICE_NAME% ++JvmOptions "-XX:MaxPermSize=128m\temp; -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager; -Djava.util.logging.config.file=%CATALINA_BASE%\conf\" --JvmMs 128 --JvmMx 512

See the documentation on Tomcat Windows Service for more details.

TIFF Image Generator

Several frevvo connector wizards, such as the Email and the PaperVision/ImageSilo wizards, allow you to select the form image attached to submission emails and stored into PaperVision/ImageSilo to be in TIFF image format. If the TIFF option doesn't appear in the wizard's Send Snapshot dropdown, then you have not yet installed the necessary TIFF image generator software.

  1. Download the JavaTM Advanced Imaging Image I/O Tools installer for your machine platform here. The installer to download depends on your java installation. For example on a windows platform:
    1. If your machine is running a JRE installed, download and run jai_imageio-1_1-lib-windows-i586-jre.exe
    2. If your machine is running a JDK installed, download and run jai_imageio-1_1-lib-windows-i586-jdk.exe
  2. Execute the installer on your machine. This automatically copies the libraries necessary to create TIFF images into your java installation directory
  3. Restart the frevvo server

You will now see the TIFF option in Send Snapshot dropdown. Form additional installation details and for various for different hardware platforms, please download the Java Image I/O Installation Guide

Note: The Image I/O tools are not available for Windows Vista or Windows 7. If you need TIFF generation select a different platform for your server install.

Signature Date/Time

Digital Signatures require no configuration. However you can control the format of the date stamp that appears when forms are signed. These two parameters in <frevvo installdir>\frevvo\tomcat\webapps\frevvo\WEB-INF\web.xml are for signature configuration. The first you should never need to change.

<context-param> <param-name>frevvo.signature.class</param-name> <param-value>com.frevvo.signature.DefaultSignature</param-value> <description>Digital signature class name</description> </context-param> <context-param> <param-name></param-name> <param-value>d MMM yyyy, z</param-value> <description>Default date format for display</description> </context-param>

Using frevvo with reverse-proxies/SSL-accelerators

If your goal is to use frevvo behind a reverse-proxy/load-balancer/SSL-accelerator you need to add a few configuration settings to frevvo/Tomcat to make sure frevvo generate correct external urls.

When using a reverse-proxy, the external host, IP and/or port visible to browsers may be different than the host, IP and/or port seen by Tomcat. This causes a problem since frevvo will generate urls in pages and forms that are either completely invalid, which is an easy case to spot since forms will not render at all, or valid by bypassing the reverse-proxy altogether, which are harder to identify except for side effects such as forms not resizing properly, or blocked by browser security restrictions.

For cases where you have only a web-server fronting frevvo as a reverse-proxy (e.g. Apache or IIS), you can setup the web-server to communicate with Tomcat using AJP. This works since AJP provides additional metadata when communicating with Tomcat to indicate the actual remote host/ip/port instead of the web-server's host/ip/port.

However, using the AJP connector will not work for all cases. For instance, if you have a reverse-proxy/load-balancer/SSL-accelerator in front of your web-server, which is fronting frevvo/Tomcat, AJP would then report to Tomcat the host/ip/port of the reverse-proxy and not of the actual client. In these cases you have to leverage a feature provided by most reverse-proxies where they generate additional HTTP headers, like X-Forwarded-For, which contains the original client IP. Frevvo can then make use of these headers to override the host, IP and/or port of the external urls it generates. This is done using the following web.xml context parameters:

  • frevvo.xforwarded.protocol.header - Identifies the name of the HTTP header containing the original request's protocol (SSL accelerators, for instance, will expose https to external clients by forward to internal services using http)
  • - Identifies the name of the HTTP header containing the original request's host
  • frevvo.xforwarded.port.header - Identifies the name of the HTTP header containing the original request's port

By default, frevvo's web.xml will contained the following values for these context parameters:

<context-param> <param-name>frevvo.xforwarded.protocol.header</param-name> <param-value>X-Forwarded-Protocol</param-value> </context-param> <context-param> <param-name></param-name> <param-value>X-Forwarded-Host</param-value> </context-param> <context-param> <param-name>frevvo.xforwarded.port.header</param-name> <param-value>X-Forwarded-Port</param-value> </context-param>

You can change these parameter values to match the header names set by your reverse-proxy or change the reverse-proxy configuration to match these defaults. You can also leave any of these parameter values blank and frevvo will then use the current request's protocol, host or port, if that makes sense in your case.

As a final note, if you plan to override these context parameter values and if you are using the frevvo Tomcat bundle, we suggest doing so in frevvo/tomcat/conf/Catalina/localhost/frevvo.xml, since that would keep all your configurations in one place and makes it easy to upgrade frevvo to newer releases. You can do that by adding the following to your frevvo.xml file:

<Parameter name="frevvo.xforwarded.protocol.header" value="X-Forwarded-Protocol" override="false"/> <Parameter name="" value="X-Forwarded-Host" override="false"/> <Parameter name="frevvo.xforwarded.port.header" value="X-Forwarded-Port" override="false"/>

Integrating Frevvo with IIS

This page describes how to configure Microsoft's IIS web server and frevvo such that IIS forwards requests on to frevvo, and responses back to the user.

frevvo is written in Java, and needs a Java Application Server (servlet container) to run. As IIS does not provide services of a Java Application Server, it is not possible to deploy frevvo directly into IIS. It is possible, however, to configure IIS to proxy requests for frevvo to an application server where frevvo is deployed. If you are not using the standalone frevvo distribution with Tomcat, please consult your application server's documentation to determine whether it is possible to integrate with IIS and how to achieve it. Also note that this is a guideline on how enable the interaction between frevvo and IIS.

Install and Configure Frevvo

Follow the Installation Instructions and verify that frevvo works by itself by pointing a browser to


Configure Tomcat

It is necessary to configure Tomcat to receive proxied requests from IIS.

  • Stop Tomcat.
  • In a text editor open FREVVO_HOME/tomcat/conf/server.xml
  • Ensure that the AJP Connector is enabled by uncommenting out the section (Since version 4.1.2 uncommented is the default)
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" maxHttpHeaderSize="32768" useBodyEncodingForURI="true" tomcatAuthentication="false" />
  • Start Tomcat
  • Check that the configured AJP port is enabled and listening for requests. On a windows command prompt:
netstat -na | findstr 8009

Download and Configure an ISAPI Filter

  • Download frevvo isapi package here. The archive is a pre-packaged isapi filter along with a recommended directory structure and pre-configured files. It is a starting point.
  • Expand the archive. For the sake of this document we will assume the archive is expanded under your "c:\" drive. If you do that, you should have a folder c:\isapi after expanding.
  • The isapi archive contains version 1.2.28 of the isapi connector for win 32. If you need to upgrade and/or IIS is running on win64, download the ISAPI Redirect DLL from the [Apache ] site. If you download a new isapi filter:
    • When downloading, choose the version of Windows that IIS is running on (either win32 or win64), and then choose the latest available jk version.
    • The file to download is named isapi_redirect_X.X.X.dll, where 'X.X.X' is the version number. You will need to remove the version number from the DLL file (i.e. it needs to be named isapi_redirect.dll).
    • After downloading and renaming, update the dll in c:\isapi\bin.
  • Under c:\isapi\bin you will find (shown below). If you expanded the filter in c:\isapi you don't have to change anything. Otherwise, just edit the paths accordingly.
# Configuration file for the Jakarta ISAPI Redirector # The path to the ISAPI Redirector Extension, relative to the website # This must be in a virtual directory with execute privileges extension_uri=/jakarta/isapi_redirect.dll # Full path to the log file for the ISAPI Redirector log_file=c:\isapi\logs\isapi_redirect.log # Log level (debug, info, warn, error or trace) log_level=info # Full path to the file worker_file=c:\isapi\conf\ # Full path to the file worker_mount_file=c:\isapi\conf\
  • If you have modified the port for the AJP Connector you will need to modify the file. The file c:\isap\conf\ assumes that Tomcat is running on the same machine as IIS and using the default port (8009) for AJP. Make adjustments if necessary.
worker.list=workerFrevvo worker.workerFrevvo.port=8009 worker.workerFrevvo.type=ajp13
  • The file c:\isap\conf\ lists the http request paths that will be forwarded to frevvo

Proceed to the IIS configuration for your specific version (IIS6 and IIS7 below).

IIS 6 Configurations

In your Windows Server:

  • Open Control Panel, then Administrative Tools and open Internet Information Services.
  • Add the ISAPI Filter to IIS
    • Right-click on Default Web Site (or the Web Site that should be responsible for proxying requests to frevvo), and click on Properties.
    • Click the ISAPI Filters tab.
    • Click Add and create one. Enter jakarta as the Filter Name and enter the location of the isapi_redirect.dll file for the executable.
    • Click OK, Apply and then OK.


  • Create a virtual directory for frevvo in IIS.
    • Right-click on Default Web Site (or the Web Site that should be responsible for proxying requests to frevvo), choose New and then Virtual Directory.
    • Go through the creation wizard. Set the alias to be the same as the context path configured in c:\isapi\bin\ If you kept the defaults in the section Download and Configure an ISAPI Filter you would enter jakarta.


    • Enter the path to the directory that contains the isapi_redirect.dll


    • Grant the 'Execute' permission for the Virtual Directory by checking the 'Execute' checkbox.
  • You will need to restart the IIS Service. To do this, browse to Control Panel, click Administrative Tools, click on Services, find the IIS Admin Service and click restart.

IIS6Grant ExecutionPermissionToVirtualDirectory.png

  • Add a Web Service Extension
    • Right-click on Web Service Extensions and choose Add a new Web Service Extension...
    • Enter jakarta for the Extension Name and then add the isapi_redirect.dll file to the required files
    • Select the Set extension status to Allowed check-box, then click OK


  • The ISAPI filter is installed and configured. You can check the status of the filter: right click on Default Web Site and select the tab ISAPI Filters. The ISAPI filter should be listed with a green arrow pointing upwards as shown below:


IIS 7 Configurations

It is necessary to have the role Web Server ISAPI Extensions and ISAPI Filters configured in IIS. If this is a new installation of IIS:

  1. Navigate to Start Menu > Administrative Tools > Server Manager.
  2. Select 'Web Server (IIS)' in Server Manager > Roles.
  3. Click 'Add Role Services' and follow the Wizard.
  4. You also need to select Windows Authentication if you will be using frevvo and LDAP SSO


If this is not a new installation of IIS you can verify the installed roles:

  1. Navigate to Start Menu > Administrative Tools > Server Manager.
  2. Click on Roles and then Web Server (IIS).
  3. Check that the required role services are installed.

Configure the ISAPI Filter

  1. Navigate to Start > Administrative Tools > Internet Information Services (IIS) Manager
  2. Click the Default Web Site (or the Web Site that should be responsible for proxying requests to frevvo), and click on ISAPI Filters (on the right panel).
  3. Check if there is a Filter that points to the isapi_redirect.dll file and that it is in the right location. If not, click Add and create one. Enter jakarta as the Filter Name and enter the location of the isapi_redirect.dll file.
  4. Click OK.

Add a Virtual Directory

  1. Right-click on Default Web Site (or the Web Site that should be responsible for proxying requests to frevvo)
  2. Click on Add Virtual Directory
  3. Configure the alias to jakarta
  4. Set the path to c:\isapi\bin

Add a Web Service Extension

  1. Navigate to the servers and highlight your server:


  1. Navigate to 'ISAPI and CGI Restrictions'.
  2. Add isapi_redirect.dll extension.
  3. In the wizard, allow the extension to execute.

Configure the HTTP Handler Mappings

  1. Open the IIS Manager
  2. Click on the Default Web Site
  3. Double click on "Handler Mappings" on the right.
  4. Select the ISAPI-dll mapping
  5. On the right column click on "Edit Feature Permissions"
  6. Check the "Execute" checkbox.

Restart IIS

  1. Navigate to Start Menu > Administrative Tools > Server Manager.
  2. In the Server Manager, click on Roles and right click Web Server (IIS).
  3. On the right panel, look for the section System Services.
  4. Restart World Wide Web Publishing Service.

If you already installed frevvo you can test the IIS configuration by pointing your browser to:


Trouble Shooting Sometimes the IIS and ISAPI configurations may not work as described above. In a number of cases this may be related to specific settings in your environment. Here are some things to check:

On windows 2008: Encrypt Content to Secure Data

    • Right Click on the isapi forlder (c:\isapi if used the defaults)
    • Select Properties.
    • In the General Tab select Advanced
    • In the Advanced Attributes verify that the checkbox Encrypt contents to secure data is not checked.

IIS user permissions

Check if the user running IIS has enough permissions to run the ISAPI dll.

Moving users to a different tenant

This section describes how to move a user to a different tenant. In the steps below, we will move the user john from a source tenant (will use tenant d) to a target tenant (will use mytenant as the target name).

  1. If the target tenant does not exist, create it by following these steps. For the sake of this document, I will assume the target tenant id to be mytenant.
  2. Login to the target tenant as an admin and create a user with the same id as the user in the original tenant. For the sake of this document, the user id is john in the tenant mytenant.
  3. Transfer the applications to the new user account in the target tenant
    1. Login to the source tenant as a tenant admin. For instance admin@d.
    2. Navigate to Manage > Manage Users. Login as the user you want to move.
    3. Navigate to the user's applications page.
    4. Download each application for that user and save to a folder in your file system.
    5. Logout
    6. Login as the user in the new tenant: john@mytenannt.
    7. Upload the applications you've downloaded in the previous steps.
  4. Move the submissions in the submissions repository. You need to run these steps in the database where you persist the frevvo submissions. Please back up your database before moving forward.
    1. Login to your database.
    2. You need to run the script shown below in your frevvo submissions database. Before you do that:
      1. Replace the word john with the id of the user you are migrating.
      2. Replace the tenant id d with the id of the source tenant. The default tenant in frevvo is called d so if you are moving the user as part of an upgrade from 3.4.x chances are that your source tenant is d.
      3. Replace the word mytenant with the name of your target tenant.
update formsubmission set tenantid='mytenant' where id in ( select from formsubmission fs, formsubmissiontype fst where fs.formsubmissiontype_formtype_id = and fst.ownerid='john' and fs.tenantid='d' ) update formsubmissiontype set tenantid='mytenant' where ownerid='john' and tenantid='d'

  1. Login as the user in the new tenant.
  2. Verify that the submissions are properly being loaded for all forms. In the submissions repository page make sure to adjust the initial and end dates to a window of time that you know have submissions for that specific form.
  3. Update references to the forms. After going trough the steps above, the URL to the forms owned by the user will be different than what they were originally. You need to update all references to the forms in published links and pages where the form should be embedded.

Show/Hide Tenant Login

Live Forms is a multi-tenant application. See the administration section on Managing Tenants. However it is possible that all you need is a single tenant. If this is your case it simplifies frevvo server login if you hide the tenant input on the frevvo login page.

This can be changed by editing <frevvo installdir>\frevvo\tomcat\webapps\frevvo\WEB-INF\web.xml. Uncomment the parameter and set the param-value to the name of your one tenant. Next set the param-value of to false.

Here is how the parameters appear after editing:

<context-param> <param-name></param-name> <param-value>ssotest</param-value> <description>Default Tenant</description> </context-param> <context-param> <param-name></param-name> <param-value>false</param-value> <description>Show Tenant Box on Login Page</description> </context-param>

Restart your frevvo server and the next time you login you will only need to enter your username and password.

Lightbulb.png Note: These two config parameters can also be overridden in <frevvo-home>\tomcat\conf\Catalina\localhost\frevvo.xml. This keeps all your modified parameters in one place and makes it easy to upgrade frevvo to newer releases.

<Parameter name="" value="mytenant" override="false"/>

Lightbulb.png Note: If you need to login as the frevvo server superuser admin you must login with username admin@d.

The trial license fails to install

Sometimes, especially on Windows, the license is not accepted. If so, please restart your frevvo server and try again. Please, check the frevvo forum or contact us for additional help.

License Issues

License issues have several common causes. A proxy server can be the cause of these error messages.

  • Unable to contact license server
  • Unable to renew license. Your license will expire in <n> day(s)

To diagnose license issue:

  1. View the frevvo server configuration page and verify that you have a valid unexpired license key.
  2. Open a browser on your frevvo server machine and try to reach the url: This server should return the message "You have reached the frevvo licensing server. Thanks for you interest in frevvo Live Forms.".
  3. Second open the log files in <frevvo installdir>/frevvo/tomcat/logs and scan for license related error messages.
  4. Read solutions for proxy server configurations if the log file indicates that your frevvo server is unable to contact the license server.
  5. Read solutions for the issue unable to renew license

If you need further help send the results of all above diagnostic steps to support at

Dropdowns lists do not appear in Internet Explorer 7

This is caused by a known issue with Microsoft security update MS11-081 released on October 11, 2011. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 2628724 Some drop-down lists and combo boxes do not appear in Internet Explorer 7 after you install security update 2586448

If you need help installing Live Forms please see Installation Help.