Section

Column

configuration parameters are located in three places:

frevvo-config.properties - created by the System Administrator to override parameters in a container web.xml file. This is most often used when the container is not tomcat. See below for details.
<frevvo-home>\tomcat\conf\Catalina\localhost\frevvo.xml - recommended file to override context-parameters in the web.xml file when using the tomcat container.
WEB-INF\web.xml - this configuration file is included in the <frevvo-home>\tomcat\webapps\frevvo.war zipfile. Modifications to this file require unzipping/rezipping the frevvo.war file after the modifications have been made. See below for the instructions.

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.

A frevvo-config.properties file in a deployment using tomcat seems redundant since it basically does the same thing as the frevvo.xml file. If it does exist , the configuration parameters in the frevvo-config.properties file will override the frevvo.xml and web.xml files.

Modifying the frevvo.xml file.

Follow these steps to modify context parameters in the frevvo.xml file. You can also set up your database in this file as well. If you are using tomcat, making your configuration changes here, will make it easier when you upgrade :

Stop if it is running.
Navigate to <frevvo-home>\tomcat\conf\catalina\localhost\frevvo.xml.
Open the file with a text editor.
The installation tasks listed below will reference the frevvo.xml and web.xml files when appropriate. You can configure anything in frevvo.xml that you can configure in web.xml. When you add parameters to the file, use the same syntax as the ones already there. Here is an example of a parameter to control the Maximum Size of Attachments that users can upload.

Code Block
<Parameter name="frevvo.attachment.maxsize" value="10485760" override="false"/>

5. Save the file after all your changes are made. Restart .

Modifying the web.xml file

The web.xml file is included in the <frevvo-home>\tomcat\webapps\frevvo.war. The frevvo.war must be unzipped/rezipped after modifications have been made as outlined in the steps below:

Stop if it is running.
Unpack the frevvo.war file to a temporary location of your choice: e.g. c:\tmp\frevvo-war. Change the file extension from .war to .zip if necessary.
Edit c:\tmp\frevvo-war\WEB-INF\web.xml.
Make the desired configuration changes - see appropriate sections of this page for information on specific parameters. Save the changes to the web.xml file.
Rezip all the files in the c:\tmp\frevvo-war directory, even the ones you did not edit — if you change directories or zip them differently, Live Forms may not load correctly:
This is the correct structure for the frevvo.war zipfile.
Make sure you create the zipfile with the directory structure as shown in the image above. It is an easy mistake to include the containing directory in the zipfile. If you do this, Live Forms may not load correctly. Zip will often give your zipfile a .zip extension. Make sure you change this to a .war extension.
Copy the updated frevvo.war file to <frevvo-home>tomcat\webapps.
Restart your server.

Column

width	400px

On this page:

Table of Contents

maxLevel	1

...

If you enter an email address in the frevvo.xml parameter and leave the Email address fields on the Edit Tenant screen blank - Doc action emails will use the frevvo.xml from email value and task notification will use tenant admin's email address.
If you enter a value into the Email address fields on the Edit tenant page - Doc action and task notification emails will use this value. The value in the frevvo.xml file is overridden.

If you want to use the frevvo.xml value for Doc action emails, leave the tenant from email address blank. This would mean flow task notifications will use tenant admin's email address.

Debug sends more debugging info to the tomcat log files. And bounce.email sets an address to receive emails that cannot be delivered to the to email recipients.

...

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.

There are two files where the changes to default the tenant login to your tenant name can be made: web.xml or the frevvo.xml. The recommended approach is to add the configuration parameters to the frevvo.xm;l file as it keeps all your modified parameters in one place and makes it easy to upgrade to newer releases. Since the file is outside the frevvo war, you avoid the unzip/rezip of the of the frevvo.war that is needed if you make the changes in web.xml. Examples containing the context parameters for both files are shown below.

...

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

Note
If you plan to run the Tomcat bundle on IBM J9 JVM and you want to have the HTTPS connector enabled, you will need to change the encryption algorithm to IBM's X509 from the default Sun X509 implementation.

To run HTTPS on IBM J9 JVM, add algorithm="IbmX509" attribute to the HTTPS connector:

Code Block

language	html/xml

<!-- 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, see below.

...

Java 7 will throw a "SEVERE: java.net.SocketException: Invalid argument: no further information" error in the <frevvo-home>/tomcat/logs/catalina.YYYY-MM-DD.log when used on a Windows 2003 system with Tomcat version 7.0.29 or earlier and the NIO http connector. If you should encounter this error, check the version of Tomcat. If it is below 7.0.30, upgrade to that version. Run the <frevvo-home>\tomcat\version.bat (Windows) or <frevvo-home>/tomcat/version.sh (UNIX) files to determine the version of Tomcat installed on your system.

Tomcat Logfiles

By default, the server writes useful logging information to a daily logging file located here: <frevvo-home>/tomcat/logs/frevvo.log. You will see the logfiles listed below in <frevvo-home>/tomcat/logs. The current date appends to the logfile name for all the files except the frevvo log:

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.log - all messages are logged to this file.
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/

...

Tomcat Logfiles

By default, the server writes useful logging information to a daily logging file located here: <frevvo-home>/tomcat/logs/frevvo.log. You will see the logfiles listed below in <frevvo-home>/tomcat/logs. The current date appends to the logfile name for all the files except the frevvo log:

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.log - all messages are logged to this file.
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.

...

conf/server.xml. Comment out the statement below to turn off logging to this file if it is not needed.

Code Block

<Valve className="org.apache.catalina.valves.AccessLogValve" directory="${catalina.base}/logs"
               prefix="localhost_access_log." suffix=".txt"
               prefix="localhost_access_log." suffix=".txt"
               pattern="%h %l %u %t &quot;%r&quot; %s %b &quot;%{Referer}r&quot; &quot;%{User-Agent}r&quot; [%I %{JSESSIONID}c]" />

...

Note

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 following screen displays when a user tries to submit a form from a timed out session.

Editing Submissions

Designer users can view/edit submissions by clicking the edit link on the submissions panel. Non designer users can view/edit submissions by clicking on the Shared Items tab if they have been granted permission to do so by the designer via the Access Control feature. The frevvo.submission.edit .link parameter must be set to the default value of true, for the edit link to be visible to any user. To disable the edit link on the submission panel, change the default value of true to false for the frevvo.submissions.edit.link configuration parameter in <frevvo-home>/WEB-INF/web.xml file. The web.xml file must be unzipped from the frevvo.war before it can be edited. Follow the instructions above to unzip, modify and rezip the war file.

...

Info

If you are using MySQL, and you upload a large image or you are using a workflow that contains a large pdf, , you may see this error:

The default value of the max_allowed_packet parameter in your MySQL server may not be large enough. Refer to this website for detailed information about the MySql configuration parameter. Increasing the max_allowed_packet variable setting in your MySQL Server from the default (1M) to something like 16M (16777125) fixes the issue. To fix the issue temporarily, run the following commands:

Code Block

<context-param> <param-name>frevvo.security.provider</param-name> <param-value>org.bouncycastle.jce.provider.BouncyCastleProvider</param-value> <description> Set the Class name or JCE provider name

mysql -u root
set global max_allowed_packet=16777216

To permanently set it, choose one of the two methods listed below:

You can add the parameter - max_allowed_packet=16M to the mysqld command line or (mysqld_safe command line) as shown:

mysqld --max_allowed_packet=16M

Edit the MySql configuration file (my.ini on Windows/ my.cnf on Mac OS) and add max_allowed_packet=16777216 to the [mysqld] section.

Code Block
[mysqld] max_allowed_packet = 16M

Restart MySQL.
Restart frevvo.
The setting will permanently take effect.

On Mac OS, you can access the my.cnf file by typing

- sudo vi /etc/my.cnf

The location of the my.ini/my.cnf file varies by configuration.

IBM J9 JVM

supports IBM's J9 JVM. To use the J9 JVM add the '''algorithm="IbmX509" attribute to the frevvo/tomcat/conf/server.xml's HTTPS <Connector> element. So, instead of this:

Code Block

<!-- HTTPS Connector : add algorithm="IbmX509" when using IBM's J9 JVM --> <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" />

You need this:

Code Block

<!-- HTTPS Connector : add algorithm="IbmX509" when using IBM's J9 JVM --> <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" />

Or, of course, comment out the HTTPS connector altogether if it is not needed.

Also, to parse license files, the BountyCastle JCE provider should be downloaded and placed in the web container classpath. For the Tomcat servlet, copy the jar into the tomcat/lib folder. Once this jar is there, the provider will be picked up automatically by through the context parameter in web.xml: frevvo.security.provider shown below. This parameter defaults to org.bouncycastle.jce.provider.BouncyCastleProvider. It is ignored when the jar is not present.

Here is a link to the Bounty Castle download page. The name of the jar is the JDK 1.5 - JDK 1.7 provider: bcprov-jdk15on-148.jar. You can download it from here.

to

use when parsing license files. If the class doesnt exist in the ClassPath, it will be ignored. This setting is needed when running frevvo on IBM J9 JVM: just add Bounty Castle JCE provider to the classpath and restart the server. </description> </context-param>

the mysqld command line or (mysqld_safe command line) as shown:

mysqld --max_allowed_packet=16M

Edit the MySql configuration file (my.ini on Windows/ my.cnf on Mac OS) and add max_allowed_packet=16777216 to the [mysqld] section.

Code Block
[mysqld] max_allowed_packet = 16M

Restart MySQL.
Restart frevvo.
The setting will permanently take effect.

On Mac OS, you can access the my.cnf file by typing

- sudo vi /etc/my.cnf

The location of the my.ini/my.cnf file varies by configuration.

Send Signatures to ImageSilo

...

Versions Compared

Old Version 21

New Version 22

Key

Modifying the frevvo.xml file.

Modifying the web.xml file

Tomcat Logfiles

Tomcat Logfiles

Editing Submissions

IBM J9 JVM

Send Signatures to ImageSilo

Page Comparison

Versions Compared

Old Version 21

New Version 22

Key

Modifying the frevvo.xml file.

Modifying the web.xml file

Tomcat Logfiles

Tomcat Logfiles

Editing Submissions

IBM J9 JVM

Send Signatures to ImageSilo