configuration properties are configured in the frevvo-config.properties file in the <frevvo-home>\tomcat\conf directory. The frevvo-config.properties is a standard java properties file. Any valid context parameter can be configured as a property in this file. This file contains properties that define global customizations that apply to the frevvo.war and the frevvo connector warfiles (Database Connector, Filesystem, SharePoint). For example, you can provide the client secret information for the Google Connector with a property in this file.

The properties that can be added to the frevvo-config.properties file are discussed below. The configuration properties in the frevvo-config.properties file will override the properties configured in <frevvo-home>\tomcat\conf\server.xml file. Parameters, previously configured in the web.xml file included in the frevvo.war must be added to the frevvo-config.properties file as well.

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

Converting Context Parameters to Properties

The configuration properties follow a simple property name=value syntax. Let's say you had context parameters to default the tenant login and customize the placeholder on the login screen in the frevvo.xml file of your previous installation.

The context parameters in frevvo.xml would look like this:

frevvo.xml from your previous Live Forms installation

<Parameter name="frevvo.default.login.tenant.id" value="your_tenant_id" override="false"/>
<Parameter name="frevvo.login.username.placeholder" value="user@<your_tenant_name>" override="false"/>

The configuration properties follow a simple property name=value syntax. Follow these steps to convert configuration parameters from previous releases to properties in the frevvo-config.properties file.

Navigate to <frevvo-home>/tomcat/conf directory.
Edit the frevvo-config.properties file.
The Parameter name becomes the property name.
Add an equal sign
Add the value after the equal sign
Repeat this for all custom parameters
Save the file

frevvo-config.properties file in the v7.4.x installation

#Custom Tenant Id and Placeholder
frevvo.default.login.tenant.id=<your_tenant_id>
frevvo.login.username.placeholder=<@<your tenant name>

Here is an example of a frevvo-config.properties file that provides the client id and secret for the Box connector, the URL for the Filesystem connector, a property to turn on/off the Insight Server and a property to turn on DEBUG level logging for the frevvo.log and any frevvo connector logfiles.

frevvo.box.connector.client.id=bttkldgy9r5td0kdu57v0h6h2gotjf03
frevvo.box.connector.client.secret=EM08T1IjiMFuyCP5OJWm5QPyTz0qcL4A 
frevvo.filesystem.connector.url=http(s)://<your server>:port/filesystem 
insight.enabled=true insight.service.url=http(s)://<your server>:port/insight 
frevvo.sharepoint.connector.url=http(s)://<your server>:port/sharepoint 
logging.level.root=DEBUG

Updating the frevvo-config.properties requires server re-start. You do not have to restart the Insight server.

frevvo tomcat bundle

In the frevvo tomcat bundle, the frevvo-config.properties file is located in the <frevvo-home>\tomcat\conf directory. The path to the frevvo-config.properties file is specified in the <frevvo-home>\tomcat\bin\sentenv.bat.sh files

set CATALINA_OPTS=%CATALINA_OPTS% -Dspring.config.location="file:///%CATALINA_HOME%/conf/,file:///%CATALINA_HOME%/conf/frevvo-config.properties"

On this page:

Changing the admin password

Login to your
server as user admin@d, password admin.
On the page that is displayed, click the Manage Tenants link.
Click the
icon to manage tenant named d (Default tenant)
Click Manage Users
Click the
edit admin user icon for the admin user. This displays a profile form.
Change the password as desired and submit the form.

Email configuration

The forgot password functionality and form submissions sent via email both require proper configuration of

' smtp component.

Edit <frevvo-home>\tomcat\conf\server.xml
Configure the Mail Resource
Save the file

Here is a sample mail/frevvoDS resource configuration:

server.xml

<!-- 
        Mail Resource 
-->     
<Resource name="mail/sharedfrevvoDS" auth="Container" type="javax.mail.Session"

 mail.smtp.host="{your.smtp.host}"
 mail.smtp.port="{your.smtp.port}"
 mail.smtp.auth="false" - If your SMTP server does not require a user/password for out bound emails, it may require that all emails are sent as a user with an account in your corporate domain. Set mail.smtp.auth="false" in this case
 mail.smtp.starttls.enable="true" - If your email server does not use TLS connection security, change mail.smtp.starttls.enable from true to false.
 mail.smtp.user="{your.smtp.user}"
 password="{your.smtp.password}"
 mail.debug="false" /> - Turning on this property sends more debugging info to the tomcat log files

Additional Email Properties

The additional email properties found in the <frevvo-home>\tomcat\conf\frevvo-config.properties file are shown below. Edit this file and add the # to comment out the properties that you do not want. Properties configured in this file take precedence over the server.xml settings.

frevvo.mail.from.email - Although this property can be used to set up a from email address, it is recommended that you use the frevvo UI to set up the from email and display name
frevvo.mail.bounce.email - Sets an address to receive emails that cannot be delivered to the to email recipients
frevvo.mail.debug - Turning on this property sends more debugging info to the tomcat log files
frevvo.actions.debug - This property controls whether or not additional info log messages are included when form actions, DOC URIs and doc actions are performed.
frevvo.rule.debug - Turning on this property sends more debugging info about rules to the tomcat log files

frevvo-config.properties

# SMTP Settings
frevvo.mail.from.email= .
frevvo.mail.bounce.email={email address for bounced emails}
frevvo.mail.debug=false
frevvo.actions.debug=true
frevvo.rule.debug=true

Email log entries

If you are using tomcat, emails sent are tracked in the <frevvo-home>\tomcat\logs\frevvo.log file when the INFO log level is enabled. Look for an entry like "Sending email to <email address> with subject <the subject of your email>. If an error occurs when sending, the message "Could not send email to <email address> with subject <the subject of your email> including the actual exception that caused the problem will be logged.

Email over SSL

If the SMTP server requires traffic to be sent over SSL, add the following properties in the mail resource configuration, and then specify values for them:

frevvo-config.properties

mail.smtp.socketFactory.port="465"
mail.smtp.socketFactory.class="javax.net.ssl.SSLSocketFactory"
mail.smtp.socketFactory.fallback="false"

Default the Tenant Login

is a multi-tenant application. See the administration section on Manage Tenants. However, it is possible that all you need is a single tenant. If this is your case, it simplifies the

server login if you default the @<tenantname> so the user only needs to enter their username to login. Customers who default the tenant login normally would also customize the placeholder on the login screen. Please read that topic for details.

Stop Live Forms if it is running.
Navigate to the <frevvo-home>\tomcat\conf directory
Open the frevvo-config.properties file with a text editor.
Add the frevvo.default.login.tenant.id property to the <frevvo-home>\tomcat\conf\frevvo-config.properties file and set the param-value to the name of your one tenant.
frevvo-config.properties
frevvo.default.login.tenant.id=<your_tenant_id>
Save the file
Restart
.

In-house customers, logging in as the

' server superuser admin, must still login with username admin@d.

Customizing the placeholder on the login screen

You may want to customize the user@tenant placeholder on the login screen to reflect the name of your

tenant to minimize confusion for your users or to remove the @tenant from the placeholder if you have defaulted the tenant login.

In-house customers can change the default placeholder on the login screen by modifying the values for the frevvo.login.username.placeholder property.

Follow these steps to change the placeholder:

Stop Live Forms if it is running.
Navigate to <frevvo-home>\tomcat\conf
Open the frevvo-config.properties file with a text editor.
Add the property shown below with your modified value then save the file.
frevvo-config.properties
frevvo.login.username.placeholder=user@mycompany
Restart
.

Turn on the Unsaved Changes Warning

You may want to to turn on the browser specific warning that displays if your users close their browser/tab before saving or submitting a formflow. A description of the feature can be found here. Here is an example for the Chrome browser:

Add the frevvo.unsaved.warning property to the <frevvo-home>\tomcat\conf\frevvo-config.properties file in the tomcat bundle.The default value is false.

Stop Live Forms if it is running.
Navigate to <frevvo-home>\tomcat\conf
Open the frevvo-config.properties file with a text editor.
Add the the frevvo.unsaved.warning property with a value of true then save the file.
Restart

frevvo.unsaved.warning=true

Configure the Insight Server

Configuration properties for the Insight Server are located in the <frevvo-home>\tomcat\conf\frevvo-config.properties file.

The properties in the frevvo-config.properties file are:

frevvo-config.properties

# Insight settings 
insight.enabled=true
insight.server-url=http://localhost:8983/solr

The "Insight.enabled" property with a value of true enables Insight Server by default.
The "Insight.server-url" property points to the location of the Insight Server. The Insignt Server is included in the tomcat bundIe. In the unlikely scenario where the Insight Server (Solr) is in a different location than
, the <server:<port>> in this property can be changed to point to the location of the Insight Server (Solr) software.

Refresh Searchable Fields Configuration Parameters

If you are using the frevvo tomcat bundle, the Refresh Searchable Fields process is already configured. The insight.war web app is located in the <frevvo-home>\tomcat\webapps\frevvo.war. Insight.war is a web app that contains a batch process that extracts all the latest submissions from

and creates Solr Documents for them. The indexed submission data from the batch is stored in <frevvo-home>\data\solr directory and is used by the

Reports feature. The batch job is automatically run when you upgrade

but it can also be run manually if necessary.

If it is determined that the Refresh Searchable Fields process needs to be run for the entire tenant

Cloud customers must contact frevvo to request the batch process for your tenant.
In-house customers can use the Refresh Searchable Fields function to manually run the batch process.

There are some properties that can be added to the frevvo-config.properties file to override default values. Although, it is recommended to leave these properties with the default values, these properties can be added with different values if requested by frevvo support to troubleshoot an issue.

index.submission.batch.size=100 - this property specifies the number of rows read into memory during the batch process. The default value is 100.
index.submission.thread.pool.size=10 - this property specifies the maximum number of threads. In a multi-tenant installations, the batch process uses one thread per tenant
index.submission.start.date=<start date> - this property can be set to a date in the YYYY-MM-DD format. The batch will then exclude any submissions before this date.

Submission View configuration

Configuration properties that affect the

Submission view are discussed below.You can turn off the Legacy Submissions view, hide the Delete submission button and the Edit Submissions link and configure the maximum number of Searchable fields allowed per form/flow.

Follow these steps:

Stop Live Forms if it is running.
Navigate to <frevvo-home>\tomcat\conf
Open the frevvo-config.properties file with a text editor.
Add the properties with your modified values then save the file.
Restart

Turn Off the Legacy Submission View

Add this property with a value of false to the <frevvo-home>\tomcat\conf\frevvo-config.properties file to turn off the Legacy Submission view in the designers and when users access submissions using Shared Items. If the Legacy view is disabled, the Saved Fields tab in the Setup Searchable fields wizard is hidden in the designers and the Export of submissions to Excel feature is no longer available. The default value is false.

frevvo-config.properties

frevvo.deprecated.submissions.view.enabled=<true or false>

Forms Home Page when the Legacy Submissions View is turned off.

If the Legacy view is disabled, the Saved Fields tab in the Setup Searchable fields wizard is hidden in the designers.

Set a Maximum Number for Searchable Fields

Add this property with the value of the maximum number of searchable fields you want to allow per form or flow to the <frevvo-home>\tomcat\conf\frevvo-config.properties file. The default value is 20.

frevvo-config.properties

frevvo.max.searchable.fields=<maximum number of searchable fields per form/flow>

Designers see a message when an attempt is made to add a searchable field that would exceed this max number.

The message appears on the lower right of the screen and disappears after a short time. Any fields in excess of the max configured will not be allowed.

Show/Hide the Delete Submissions Button

Add this property with a value of false to the <frevvo-home>\tomcat\conf\frevvo-config.properties file to hide the Delete button on the Submission Table. If configured, the Delete button in the Legacy Submission view is also hidden. The default value is true.

frevvo-config.properties

frevvo.submission.delete.buttons=<true or false>

Disable the Submission Edit Link

Add this property with a value of false to the <frevvo-home>\tomcat\conf\frevvo-config.properties file to disable the Submission Edit link in the on the submission details popup everywhere it is displayed. If configured, the link is disabled for the Legacy Submission view as well. The default value is true.

frevvo-config.properties

frevvo.submission.edit.link value=<true or false>

Administration of reCAPTCHA Keys

provides a default reCAPTCHA key. No other configuration steps are required for on-premise customers that choose to use the default key. This default reCAPTCHA key is:

NOT configured to a particular host/domain server
NOT configured for Google to perform any host/domain name checking on the challenge step. However,
will perform a host/domain verification on the verification step so that any attempts at site key spoofing are blocked.
Considered secure.

In-house customers who want the maximum possible protection from form spamming, will need to create their own reCAPTCHA key and configure to their domain (example.com).

Follow these steps:

You will need a google account.
Follow the instructions on this Google site to register your domain and create the site and secret keys.
1. You can also choose "Domain Name Validation" on this key to have Google check the domain on the challenge step.
Copy the site and secret keys from the Registration page for your site
Add the frevvo.reCAPTCHA.sitekey and the frevvo.reCAPTCHA.secretkey properties to the <frevvo-home>\tomcat\conf\frevvo-config.properties file.
frevvo.recaptcha.sitekey=<your custom site key here> frevvo.recaptcha.secretkey=<your custom secret key here> frevvo.recaptcha.hostcheck=<true or false>

The frevvo.recaptcha.hostcheck property controls the domain/host verification on the verification step that is done by

. The values for this property can be set to true or false. If you use a custom key with Domain Name Validation configured, add this property to the frevvo-config.properties file with a value of false. Otherwise, add it to frevvo-config.properties with a value of true.

Proxy Server configuration

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

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

External URLs

Sometimes running

behind a proxy server can cause unintended changes to the form server's external URLs. The following configuration properties address this issue. Add these properties to the <frevvo-home>\tomcat\conf\frevvo-config.properties file.

frevvo.forms.server.external.url - If set, all share dialogs for forms and flows will use this as the external URL. Use the syntax shown in the example. change the <myexternalhost>and <port> to your external server name and the port that you are using for
on this server.
frevvo-config.properties
frevvo.forms.server.external.url=http://<myexternalhost>:<port>>
frevvo.internal.baseurl - If set, all URLs used internally by the form server will use this base url. This may be needed when using frevvo.forms.server.external.url if that external url is not also accessible from the form server machine. Use the syntax shown in the example. change the value "http://localhost:8082" to the server name and port of your
server.
frevvo-config.properties
frevvo.internal.baseurl=http://localhost:8082

Default Port

By default the

tomcat bundle is configured to bind to port 8082. You can change the port by:

Editing the <frevvo-home>/tomcat/conf/server.xml file.
Search for this line in the file:
<Connector port="8082" protocol="org.apache.coyote.http11.Http11NioProtocol"
Change the Connector port

Browser Support

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. In previous releases,

was configured to use a list of supported browsers. An error message and a link to override the error would display if the system was accessed using an unsupported browser. If you want to warn users if they access

using an uncertified browser, configure a list of allowed browsers using the the frevvo.supported.browsers parameter in the <frevvo-home>\tomcat\conf\frevvo-config.properties file

Stop Live Forms if it is running.
Navigate to <frevvo-home>\tomcat\conf
Open the frevvo-config.properties file with a text editor.
Add the properties with your modified values then save the file.
Restart

Add the user agent for the browsers you want to support '''in lower case only'''. For example, to allow all versions of Firefox, add the string 'firefox' (without the quotes) to the property value. It will match all versions of the Firefox browser. Internet Explorer 11 requires the use of the agent identifier, trident/7. Separate the values with a comma.

frevvo-config.properties

frevvo.supported.browsers=firefox,trident/7

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-home>\tomcat\conf\tomcat-users.xml.

Tomcat SSL

can be configured to handle HTTPS connections from users. The

tomcat bundle you downloaded from www.frevvo.com is pre-configured with a self-signed certificate for development and testing. This self-signed certificate enables

to handle HTTPS connections out of the box. However before deploying your forms to production you may want to replace this with your own certificate.

The HTTPS connector on port 8443 is enabled by default. If you want to disable it, edit the <frevvo-home>/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" />
-->

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 javax.net ssl. SSLHandshakeException?

Currently you must not disable

's http port. In a future release this will be allowed. Disabling

' http port will cause your form server to malfunction as

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

behind an Apache or IIS server. Close the http port on Apache or IIS but leave tomcat's http port open so that

can POST back to itself when needed over http but no one outside can access it.

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

Tomcat Logfiles

By default, the

server writes useful logging information to a daily logging file located here: <frevvo-home>/tomcat/logs. You will see the logfiles listed below in <frevvo-home>/tomcat/logs. The current date appends to the logfile names.

catalina.YYYY-MM-DD.log - this log captures the stderr and stdout of the tomcat process including startup/shutdown messages. This is usually a small file.
frevvo_YYYY-MM-DD.log - all
messages are logged to this file. A new log with the current date appended to it is created daily.
localhost.YYYY.MM.DD.log - this tomcat logfile should be empty.
localhost_access_log.YYYY - MM - DD.txt - is used to log all HTTP accesses to Tomcat. It is enabled by the following entry in <frevvo-home>/tomcat/conf/server.xml. Comment out the statement below to turn off logging to this file if it is not needed.
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log" suffix=".txt" pattern="%h %l %u %{begin:dd/MM/yy:H:m:s.S}t "%r" %s %b "%{Referer}r" "%{User-Agent}r" [%I %{JSESSIONID}c %{X-Correlation-Id}o %{Location}o]" />
host-manager.MM-DD-YYYY.log - this logfile is part of the tomcat distribution and is empty by default. It is a log file for the host-manager web application that is used to manage virtual hosts in tomcat. The host manager web-app is typically not needed because
is preconfigured. Messages are written to this log only if the host-manager web application is being used.
manager.MM-DD.YYYY.log - this logfile is part of the tomcat distribution and is empty by default - this is the log file for the tomcat manager web application which is used to check the status of web apps, memory usage etc. Messages are written to this log only if the manager web app is being used.

The Database, Google, Filesystem, and SharePoint connectors will generate their own logs in the <frevvo-home>/tomcat/logs directory when configured. The connector logs capture entries for the respective connectors making troubleshooting issues easier.

database.connector.YYYY-MM-DD.log
google-connector.YYYY-MM-DD.log
file-connector.YYYY-MM-DD.log
sharepoint-connector.YYYY-MM-DD.log

There will be three additional logfiles when running Tomcat as a Windows service:
- frevvoforms - stderr.YYYYMMDD and frevvoforms - stdout.YYYYMMDD for standard error messages and standard output stream, respectively. This is the default Tomcat behavior.
- commons-daemon.YYYY-MM-DD.log for Windows Service errors
The Insight server no longer creates a log since the insight.war is integrated into frevvo.war. The messages formerly in the insight logs are now found in the in the <frevvo-home>/tomcat/frevvo_YYYY-MM-DD.log

Refer to the topics below for information about turning on DEBUG level logging.

Loglevels

Loglevels are : TRACE, DEBUG, INFO, WARN, ERROR, OFF, ALL. They are case sensitive so be sure to type them in upper case. The logging level is cumulative as shown below. Refer to this stackoverflow website for a description of the loglevels and some guidelines for using them.

OFF = turns all logging off
ERROR = ERROR
WARN = WARN + ERROR,
INFO = INFO + WARN + ERROR,
DEBUG = DEBUG + INFO + WARN + ERROR,
TRACE = DEBUG + INFO + WARN + ERROR
ALL= turns all logging on

Configuring the logging level for catalina.log, localhost.log, host-manager.log, manager.log and local_access.log is done in <frevvo-home>/tomcat/conf/logging.properties

Log Messages in the Live Forms log

frevvo Cloud log messages show session information and the names of the Log Message properties include an _ (underscore).

Session Information

Messages in the frevvo Cloud log the tenant.id, subject.id, correlation.id, session.id, owner.id, application.id, and type.id (formtype or flowtype) for all log messages.

This additional information can be extremely helpful when troubleshooting errors particularly in the frevvo cloud environment. The example shows an INFO message that specifies the tenant, mycompany and the userid, max associated with the entry:

22:05:12.471 |-INFO  [http-nio-8082-exec-1] [   c.f.u.HttpClientHolder] [mycompany max] [f7ec10f5-bd0e-4a3d-b848-9192e646a62d 61E88E450BC436C4087C136DB94F0DC2] [  ] - Installing HTTPClient credential for user maryann and scope BASIC 'frevvo Trac'@dev.frevvo.com

Log Message Property Names

Log Message property names that include a . (period) make it difficult to filter these messages using cloud watch filters. Properties have been renamed to include the _ (underscore) instead of the . (period) i.e. tenant.id = tenant_id.

Debugging log file levels

By default

log levels are set to INFO. Loglevels are changed by adding properties to the <frevvo-home>\tomcat\conf\frevvo-config.properties file. Changing the loglevel to DEBUG provides more information when troubleshooting.

If you want to delete the logs, stop

then delete the logfiles. They will be recreated on start up.

Changing the logging level for Live Forms log files

Add the three properties shown below with a value of DEBUG to the <frevvo-home>\tomcat\conf\frevvo-config.properties file to change the loglevel to DEBUG.

Create/Edit the frevvo-config.properties file in <frevvo-home>\tomcat\conf
Add the properties shown below to the file.
Save the file
Restart
.

frevvo-config.properties - These properties will turn on DEBUG level logging for the frevvo.log and all connector logfiles.

logging.level.root=DEBUG
logging.level.com.frevvo=DEBUG
logging.level.com.gauss=DEBUG

This property turns on WARN level logging.

logging.level.root=WARN

Turn on DEBUG for the Database Connector log

It is possible to turn on DEBUG level logging only for the Database Connector. Refer to the Database Connector Logfiles topic for the details.

Viewing the number of logged in users

Tenant, superuser or additional admin(s) can manage user session via the

UI. Refer to the Manage Logged in User Sessions topic for the details.

JMX Monitoring Enabled

JMX (Java Management Extensions) is enabled by default in the tomcat bundle.The following JMX options were added to the <frevvo-home>\tomcat\bin\setenv.bat,sh files. The <server>:<port> values default to localhost:9010.

Dcom.sun.management.jmxremote.local.only=false 
Dcom.sun.management.jmxremote.authenticate=false 
Dcom.sun.management.jmxremote.port=9010 
Dcom.sun.management.jmxremote.rmi.port=9010 
Dcom.sun.management.jmxremote.ssl=false 
Djava.rmi.server.hostname=localhost

Information can be accessed with jConsole, or a similar tool.

Session Timeout

's default web browser session timeout is 30 minutes. If a user is logged into the

server to design forms, or to view their task list, or is using a

form and filling in values but has not yet submitted the form, the session will expire after 30 minutes of inactivity. When the session expires the designer will have to re-login to

to continue designing forms and form users will have to get a new instance of the form and re-enter the values.

If the maximum number of concurrent users are logged in simultaneously, and any of them are idle for more than 30 minutes, the next person who tries to log in will be able to do so successfully.

The default

server session timeout can be overridden for each tenant. The tenant admin can edit the tenant and make the changes there.

When a person is using a form/flow then pauses for longer than the configured <session-timeout>, they will see the

login screen.

When a person is using a form/flow 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 or try to submit a form from a timed out session.

Live Forms 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 
-Djava.io.tmpdir=%CATALINA_BASE%\temp;
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager;
-Djava.util.logging.config.file=%CATALINA_BASE%\conf\logging.properties" 
--JvmMs 128 --JvmMx 512

See the documentation on Tomcat Windows Service for more details.

TIFF Image Generator

All

connector wizards allow you to select the form image attached to submission to be in TIFF image format. If the TIFF option doesn't appear in the wizard's Send Snapshot dropdown, follow these steps to install the necessary files:

Stop
Download the jai-imageio-core-1.3.1.jar here.
Add it to frevvo classpath i.e. tomcat/lib folder
Deploy pve.war (PVE Connector) in tomcat/webapps folder. Download the latest version of the PVE Connector from our DocuPhase Forms Software Downloads Directory.
Restart the
server. You will now see the TIFF option in the connector wizards Send Snapshot dropdown. The image shows the TIFF format option for the PaperVision or ImageSilo Connector wizard.

Signature Date/Time

Digital Signatures require no configuration. However you can control the format of the date stamp that appears when forms are signed.

Stop Live Forms if it is running.
Navigate to <frevvo-home>\tomcat\conf
Open the frevvo-config.properties file with a text editor.
Add the frevvo.signature.date.format property with your modified value then save the file.
Restart

This property will change the date format for text signatures to day,month, year

frevvo-config.properties

frevvo.signature.date.format=d MMM yyyy

Timezones

concanocolizes all form submission data to UTC. In other words no matter which timezone you are in when you submit a form with a date, date/time, or time control, the form server will convert and store those values in UTC. If your form submission data is not correctly converted and stored in UTC then you likely have to update the timezones in your installed JDK. Oracle provides a timezone update tool. Run the TZUpdater tool with the following command: java -jar tzupdate.jar -u

See Oracle's Timezone Updater Tool for full details.

Enabling Strong Passwords

Policy strength and effective date are configurable properties in the <frevvo-home>\tomcat\conf\frevvo-config.properties using following properties.

frevvo.password.policy.strength=3
frevvo.password.policy.effective.on=2019-05-07

To turn off the strong passwords feature, delete the line frevvo.password.policy.strength=<1-4>. To keep the feature but turn off only strength meter set frevvo.password.policy.strength=0.

Batch User Uploads

Uploading a CSV file to add or edit users normally runs quickly. However, if uploading a file in which the notifyIfNewUser property is TRUE for a large number of rows, this process may slow down on some email servers. Tenant Admins can configure

to run CSV-file user uploads in batches to improve upload time if needed. To adjust batch load size, configure the following property in <frevvo-home>\tomcat\conf\frevvo-config.properties.

frevvo.userloader.batchSize=25

Using Live Forms with reverse-proxies/SSL-accelerators

If your goal is to use

behind a reverse-proxy/load-balancer/SSL-accelerator you need to modify configuration settings to

/tomcat to make sure

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

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.

no longer supports the web.xml parameters for frevvo.xforwarded.protocol.header, frevvo.xforwarded.host.header, and frevvo.xforwarded.port.headers. The general recommendation is to rely on the Servlet Container for handling dynamic proxies. A better approach is to use tomcat's RemoteIp Valve instead. Please see this documentation on the Apache Tomcat website for information about the RemoteIp valve functionality. This tomcat valve has been incorporated into our

tomcat bundle.

 <Valve className="org.apache.catalina.valves.RemoteIpValve"
            internalProxies=".*" 
            remoteIpHeader="x-forwarded-for" 
            proxiesHeader ="x-forwarded-by" 
            protocolHeader="x-forwarded-proto" />

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

If the target tenant does not exist, create it by following these steps. For the sake of this document, the target tenant id is mytenant.

Installation Tasks

Converting Context Parameters to Properties

frevvo tomcat bundle

Changing the admin password

Email configuration

server.xml

Additional Email Properties

frevvo-config.properties

Email log entries

Email over SSL

frevvo-config.properties

Default the Tenant Login

Customizing the placeholder on the login screen

Turn on the Unsaved Changes Warning

Configure the Insight Server

frevvo-config.properties

Refresh Searchable Fields Configuration Parameters

Submission View configuration

Turn Off the Legacy Submission View

frevvo-config.properties

Set a Maximum Number for Searchable Fields

frevvo-config.properties

Show/Hide the Delete Submissions Button

frevvo-config.properties

Disable the Submission Edit Link

frevvo-config.properties

Administration of reCAPTCHA Keys

Proxy Server configuration

External URLs

Default Port

Browser Support

frevvo-config.properties

Tomcat Manager

Tomcat SSL

Tomcat Logfiles

Loglevels

Log Messages in the Live Forms log

Session Information

Log Message Property Names

Debugging log file levels

Changing the logging level for Live Forms log files

frevvo-config.properties - These properties will turn on DEBUG level logging for the frevvo.log and all connector logfiles.

This property turns on WARN level logging.

Turn on DEBUG for the Database Connector log

Viewing the number of logged in users

JMX Monitoring Enabled

Session Timeout

Live Forms as a windows service

TIFF Image Generator

Signature Date/Time

frevvo-config.properties

Timezones

Enabling Strong Passwords

Batch User Uploads

Using Live Forms with reverse-proxies/SSL-accelerators

Moving users to a different tenant