Forms/flows created on v5.2 patch 1+ or v5.3+ will not require further attention post migration. However, there are a few migration items that you need to consider. Please read and understand the Planning for v6.1 which may require your action before you begin your upgrade.
Please follow the instructions on this page, to perform your upgrade. Click on the link for the section that applies.
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.
You will need to upgrade to version 4.1.7 before migrating to version 5 and then to version 6. Refer to Upgrading Your In House Server to v4.1.7 for the details. When the upgrade to v4.1.7 is complete, return to this page and continue with the Upgrading from v4.1.7+ section below:
You will need to upgrade to version 5.3 before migrating to version 6. Refer to Upgrading from v4.1.7+ in the v5.3 documentation for the details. When the upgrade to v5.3 is complete, return to this page and continue with the Upgrading from v5.2 patch1+ or v5.3+ section below.
You will need to upgrade to version 5.3 before migrating to version 6. Refer to Upgrading from v5.1.x in the v5.3 documentation for the details. When the upgrade to v5.3 is complete, return to this page and continue with the Upgrading from v5.2 patch1+ or v5.3+ section below.
Your Live Forms server must be running v5.2.1 patch 1+ or v5.3+ before proceeding with the following steps
Please read the following upgrade steps prior to starting the migration.
The execution of SQL scripts is no longer required. All database initialization and/or upgrade will be done by frevvo.war as part of the v6.1 startup.
The users schema for the version you are migrating from must be located on the same database server instance as the new frevvo 6 schema. The upgrade process directly selects from the old users schema and inserts into the new frevvo 6 schema using a single sql statement.
Point v6.1 frevvo database to your v5.2 patch 1+ or v5.3+ frevvo database. An example for MySQL is shown below:
5.3 customers using LDAP must copy their LDAP config parameters from the frevvo.xml file of the version you are migrating from to the v6.1 version frevvo.xml BEFORE starting the v6.1 server for the first time. will then migrate the config to the tenant level on startup. LDAP parameters can then be edited in the v6.1 UI.
During the upgrade from 5.x to 6.1, Live Forms copies the data in the old users schema into the corresponding new tables in the frevvo schema. The users and frevvo schemas are being consolidated as part of the 6.1 release. In order to do this, Live Forms uses the frevvo database user to select the data from the old users schema. Therefore, the frevvo database user must have select access to all of the tables in the old user. In case your database is not already configured for this, you must grant select permission to the frevvo user on these tables BEFORE upgrading.
Below is an example of the queries needed to grant select permission on the users schema to the frevvo user for the Oracle database:
GRANT select ON users.resources TO frevvo; GRANT select ON users.roles TO frevvo; GRANT select ON users.spaces TO frevvo; GRANT select ON users.tenantcategories TO frevvo; GRANT select ON users.tenants TO frevvo; GRANT select ON users.users TO frevvo; GRANT select ON users.usersroles TO frevvo; GRANT select ON users.tenantroles TO frevvo;
If you are using a database other than Oracle, similar statements need to be executed. Please consult your database documentation for the correct syntax.
The frevvo db user id requires the database level privileges listed below on first startup. If your database is not set up for this already, privileges will be needed for the following actions:
JBOSS container : Quartz parameter has to be added to frevvo-config.properties file. e.g in case of MSSQL database, add the following in this file:
JBOSS + SQL server : "SelectMethod=cursor" has to be added to the connection url in frevvo-ds.xml file as follows :
11. Start the v6.1 server.
The users database, required for previous versions of , is no longer needed. The 6.1 automigration creates a new frevvo database that contains all the tables from frevvo and users databases of the the previous version along with any new ones.
12. Upgrade all users and their forms to v6.1. This step is VERY IMPORTANT. Follow these instructions:
It is recommended that you do not change or delete the frevvo.users.schemaName property in frevvo.xml after the first startup of v6.1. 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're applying a minor patch update, for example, applying patch 6.1.1 to your installed v6.1 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.
Follow these steps:
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 change in the web.xml file of your frevvo.war, then you will have to make those changes again in the web.xml file of the new frevvo.war. The steps to do this are explained here 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.
If you are running Live Forms for Confluence please follow the same instructions above to upgrade your server. If you are upgrading from for Confluence v5.3, then this upgrade does not require an upgrade to your frevvo-Confluence Add-on. 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 support at frevvo.com.
If you are using the database connector, you must reinstall and configure it again for the v6.1 installation.