Before you begin the migration process:
Determine Your Upgrade Path
Please follow the instructions on this page, to perform your upgrade.
does not support the use of HSQLDB for use beyond demo/trials of the Live Forms software. If by mistake you continued to use the demo/trial HSQLDB database for production use, you will need to first migrate your data to one of supported production databases BEFORE you can use the automated migration scripts to upgrade to later versions of Live Forms.
Although v5.3.9 is no longer supported, we are happy to help you upgrade to v7.1. If you are upgrading from v5.3.9 you must upgrade your v5.3.9 installation to v7.0 first and then upgrade your v7.0 installation to v7.1. Please refer to the v7.0 Update Guide for the instructions. When the v7.0 upgrade is complete, return to this page and continue with the instructions below.
Please read the following upgrade steps prior to starting the migration.
v7 License Key Required:
A v7 license key is required for this version of if you are upgrading from a version prior to v7.0. Request a v7 license by emailing firstname.lastname@example.org BEFORE you begin the upgrade. v5 and v6 licenses will not work.
Stop the server using stop-frevvo.[bat,sh] or through the Computer Management Services console if is running as a window's service.
If you are using SQL Server as your Live Forms database, it is highly recommended that you turn on the READ COMMITTED SNAPSHOT setting in the database BEFORE performing the upgrade to v7.1.
You do not have to do this if you are using MySQL or Oracle databases because the READ SUBMITTED SNAPSHOT is turned on by default.
There are two ways to turn on the option:
Navigate to <frevvo-home>\tomcat\conf\server.xml in the v7.1.x directory structure.
Database configuration has been removed from the <frevvo-home>\tomcat\conf\Catalina\localhost\frevvo.xml file. It is now done in the <frevvo-home>\tomcat\conf\server.xml file. Also, notice the database resource name has been changed to jdbc/sharedfrevvoDS. When you configure your database, make the changes to the v7.1.x server.xml. Do not copy configured sections from a frevvo.xml of a previous release into the v7.1.x server.xml file.
Point the v7.1.x frevvo database to your current frevvo database.
All database initialization and/or upgrade will be automatically done by frevvo.war as part of the v7.1.x startup.
Copy the frevvo.users.schemaName property from <frevvo-home>\tomcat\conf\catalina\ocalhost\frevvo.xml to the v7 <frevvo-home>\tomcat\conf\catalina\ocalhost\frevvo.xml.
Compare the frevvo.users.schemaName property in the frevvo.xml file from the version of you are upgrading from to the frevvo.xml file in v7.1 installation directory. If they are the same, do not do the copy in Step 6 - proceed to Step 7.
8. Follow the steps for your Operating system to start the Insight server BEFORE starting .
Open a command prompt. Navigate to <frevvo-home>\solr-5.4.1.Type bin\solr.cmd start to run the Insight server in the background, listening on the default port 8983.
You will see this message:
If you close the Insight server (Solr) startup window, the server will stop running. Leave the window open or set up Live Forms and the Insight Server to run as Windows services.
9. Start the v7.1.x server by running the start-frevvo.bat or start-frevvo.sh files in the <frevvo-home>\frevvo directory depending on your Operating system.
During the upgrade the Insight server batch job will automatically run preparing your submission data for the Reports feature and the submissions view.
It is recommended that you do not change or delete the frevvo.users.schemaName property in frevvo.xml after the first startup of v7.1.x. If the property is changed or deleted post migration you may see this error:
Follow these steps to rectify the situation:
You may see an unexpected error due to a misconfiguration. One likely cause is that you have copied an older version of frevvo.xml or web.xml from your old Live Forms server into your new Live Forms server. The upgrade will detect this error and alert you that an upgrade error may have occurred. To solve this replace frevvo.xml and/or web.xml with the version that came with your new Live Forms software. To transfer configuration customizations from your old server software to you new server, edit frevvo.xml and/or web.xml and copy the changes over manually.
If you start before the Insight server, you will see this message when you browse the login URL. Follow these steps to start the servers in the correct order:
If you're applying a minor patch update, for example, applying patch 7.1.2 to your installed v7.1.x Live Forms server, you can follow these simple steps instead of the more lengthy upgrade steps.
The latest major version and latest connector versions are available on the public Software Downloads page.
Copy the \temp\frevvo\tomcat\webapps\frevvo.war file.
Replace the frevvo.war file in your installation with the one copied above.
If you made any configuration changes in the web.xml file inside the frevvo.war, we recommend that the configuration context parameters be moved to the <frevvo-home>\tomcat\conf\localhost\frevvo.xml instead. This keeps all your changes in one place and makes migration to major new versions easier. If you choose not to move the configuration to frevvo.xml, you can follow the steps here to make the changes in the v7.1.x web.xml or you can just copy the old web.xml and replace the new one with it.
Delete everything inside \frevvo\tomcat\temp directory of your installation.
Start the Insight server. Refer to Step 8 above for the instructions.
If you are running Live Forms for Confluence please follow the same instructions above to upgrade your server. Please refer to the Confluence Add-on Release Notes compatibility matrix. The server and the Confluence Add-on versions must match.
If you do not find your Confluence server version in the Confluence Add-on Release Notes compatibility matrix, please contact email@example.com.
If you are using the database connector, you must reinstall and configure it again for the v7.1.x installation.
If you are using any of the connectors, you must reinstall and configure them for the v7.1.x installation.
The Box Connector is available for cloud customers. Installation instructions for in-house customers are listed in the Box.com Connector chapter.