Migrating from HSQLDB

 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.

Upgrading from v5.3.9, v6.1, v6.2 or v6.3

Please read the following upgrade steps prior to starting the migration.

1. Please read and understand the Migration Considerations which may require your action before beginning.

2. Backup the forms and users databases from your current installation.
3. Backup the current  server's installation directory so that you have a copy of all custom configuration parameters.

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

   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:

   1. Using DDL ( Data Definition Language) - Run the commands listed below

      ALTER DATABASE <your frevvo database schema> - replace <your frevvo database schema> with the name of your frevvo database schema 
      SET READ_COMMITTED_SNAPSHOT ON

   2. Using SQL Server Management Studio:

   • Turn on the “Is Read Committed Snapshot On” Option under database properties.
5. Install a fresh v7.0.x  server:
   1. Download the latest v7.0.x software.
   2. Request a v7 license if you have not already done so, before continuing.
   3. The download is a zip file. Extract the contents to any folder of your choice. This folder will be referred to as <frevvo-home> (note that the zip already contains a top level frevvo folder).
   4. If you increased Memory Settings in your previous installation, make those changes to the appropriate files in the v7.4.x installation. Refer to Hardware and Memory Requirements for the details

   5. Navigate to <frevvo-home>\tomcat\conf\server.xml in the v7.0.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.0.x server.xml. Do not copy configured sections from a frevvo.xml of a previous release into the v7.0.x server.xml file.

   6. Point the v7.0.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.0.x startup.

6. If you are upgrading from v6.1+, copy the frevvo.users.schemaName property from v6 <frevvo-home>\tomcat\conf\catalina\ocalhost\frevvo.xml to v7 <frevvo-home>\tomcat\conf\catalina\ocalhost\frevvo.xml.
   If you are upgrading from v6.1+, you can skip steps 7a  - 7b and go directly to step 8.
7. If you are upgrading from a version prior to v6.1, then you MUST perform these steps:
   
   

1. 1. If you are using the tomcat servlet, follow the steps below to configure the v7.0.x <frevvo-home>\tomcat\conf\catalina\localhost\frevvo.xml file for migration.

      1. For SQL server database migration: Uncomment " <Parameter name="frevvo.users.schemaName" value="users.dbo" override="false"/>" in frevvo.xml and comment out "<Parameter name="frevvo.users.schemaName" value="users" override="false"/>". 
      2. Set the value of frevvo.users.schemaName in the v7.0.x frevvo.xml file to the name of the users database of the version you are migrating from.  If you didn't change the name of the users schema in the version you are migrating from, then you can leave it as the default, users. Make sure you append .dbo to the users schema name if you are using an SQL server database.

      3. During the upgrade 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 consolidated in this release.  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:  

         • Create Table
         • Alter Table
         • Drop Table
         • Create Index
         • Create Sequence (Oracle)
         • Create Trigger

   2. Customers upgrading to v7.0.x from a Live Forms version prior to v6.1, using LDAP, must copy their LDAP config parameters from the frevvo.xml file of the version you are migrating from to the v7.0.x version frevvo.xml BEFORE starting the v7.0.x server for the first time. Live Forms will then migrate the config to the tenant level on startup.  LDAP parameters can then be edited in the v7.0.x UI.

8. Configure the new installation

• • If you made changes to the following files in your previous installation, you will need to make the same changes in the new v7.0 configuration files.
  • • <frevvo-home>/tomcat/conf/server.xml
    • <frevvo-home>/tomcat/conf/Catalina/localhost/frevvo.xml
  • We recommend that any changes that were made to the web.xml file be moved to frevvo.xml instead.
  • The three files mentioned above include:
    
    • Database Configuration
      •  Database Driver Installation
    • Email Configuration
    • Proxy Server Configuration
    • Default Port
    • LDAP Configuration, if applicable
      
      • Refer to Installation Tasks for more information.
        
        

     9. Follow the steps for your Operating system to start the Insight server BEFORE starting .

           Windows:

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

   2. Browse http://<your server:port>/ solr to verify the Insight server is running. The <server:port> default values are localhost:8983. Change localhost to the server name and 8983 to the port the Insight server is running on if they are different than the defaults. Do not include the angle brackets <>. You will see the Insight server (Solr) dashboard with the current status:

Linux:

1. 1. Ensure that the scripts are executable: chmod 755 <frevvo-home>/tomcat/bin/*.sh
   2. Navigate to <frevvo-home>/solr-5.4.1/bin. Run this command to make the solr startup file executable:
      chmod +x solr
   3. Navigate back to the solr-5.4.1 directory.
      cd ..
   4. Start the Insight server by typing:
      bin/solr start - this starts the Insight server in the background.
   5. Browse http;<your server:port>/solr to verify the Insight server is running. The <server:port> default values are localhost:8983. Change localhost to the server name and 8983 to the port the Insight server is running on if they are different than the defaults. Do not include the angle brackets <>. You will see the Insight server (Solr) dashboard with the current status:

     10.  Start the  v7.0.x server by running the start-frevvo.bat or start-frevvo.sh files in the <frevvo-home>\frevvo directory depending on your Operating system.

Things to Check:

1. Login as a tenant admin
   1. Click on the Configuration Checklist link to verify that all configurations are complete.
   2. Click on the Reports link. Click on one of the Reports to verify that submission data is displayed.
2. Login as a tenant designer user
   1. View and edit a form/flow
   2. View submissions that existed before
   3. Test forms/flows 
      
3. Login as the superuser admin.
4. Verify that the Insight server batch job ran and completed successfully.
   

Troubleshooting:

It is recommended that you do not change or delete the frevvo.users.schemaName property in frevvo.xml after the first startup of v7.0.x.  If the property is changed or deleted post migration you may see this error:

Follow these steps to rectify the situation:

1. Change the property back to what it was during migration and restart.
2. If step 1 does not fix the problem, delete all rows from the DATABASECHANGELOG database table and then restart. Use the command: delete from DATABASECHANGELOG. 

Unexpected Error

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.

Starting the Insight server before .

Applying a Minor Patch Update

If you're applying a minor patch update, for example, applying patch 7.0.2 to your installed v7.0.x Live Forms server, you can follow these simple steps instead of the more lengthy upgrade steps.  

1. Unzip the downloaded build zipfile to a temp directory. 

2. Copy the \temp\frevvo\tomcat\webapps\frevvo.war file.

3. Stop .

4. Replace the frevvo.war file in your installation with the one copied above.

5. Copy the <frevvo-home\frevvo\tomcat\lib\logback.xml file
6. Replace the logback.xml file in your installation with the one copied in step 5.

7. 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.0.x web.xml or you can just copy the old web.xml and replace the new one with it.

8. Delete everything inside \frevvo\tomcat\temp directory of your installation.

9. Start the Insight server if it isn't already running. Refer to Step 9 above for the instructions.

10. Start . 

Live Forms for Confluence

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@frevvo.com.

Database Connector

If you are using the database connector, you must reinstall and configure it again for the v7.0.x installation.

Google, PVE or Filesystem Connectors

If you are using any of the connectors, you must reinstall and configure them again for the v7.0.x installation.