...

 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 v4.x - 4.1.6

Upgrading from v4.1.7+

...

Upgrading from v5.1.x

Upgrading from 5.0 (r22491) or v5.2 patch 8/9+ or v5.3.8 or 6.1

...

.

...

1

...

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 v5 server's forms and users databases.
3. Backup the v5 server's installation directory so that you have a copy of all custom configuration parameters.
4. Stop the v5 server using stop-frevvo.[bat,sh] or through the Computer Management Services console if is running as a window's service.
5. Install a fresh v6  server:
   1. Download the latest v6.1 software.
   2. 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). 

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

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

7. If you are using the tomcat servlet, follow the steps below to configure the v6.1 <frevvo-home>\tomcat\conf\catalina\localhost\frevvo.xml file for migration.
   
   1. Navigate to <frevvo-home>\tomcat\conf\catalina\localhost\frevvo.xml in the v6.1 directory structure.

   2. Point v6.1 frevvo database to your v5.2 patch 1+ or v5.3+ frevvo database. An example for MySQL is shown below:
      
       
       

   3. 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"/>".  
      
      
   4. Set the value of frevvo.users.schemaName in the v6.1 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.
      
      

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

   
   
   

8. 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: 
   

   Code Block
   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. 
   

   Info
   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

   .

9. If you are using the JBOSS container, make the following additions to the configuration files:
   
   

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

      "org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.MSSQLDelegate" 

       

   2. JBOSS + SQL server : "SelectMethod=cursor" has to be added to the connection url in frevvo-ds.xml file as follows : 

      "<connection-url>jdbc:sqlserver://localhost:1433;databaseName=frevvo;SelectMethod=cursor;</connection-url>" 
      
      

   3. The Quartz parameter is not required for starting the frevvo server if you are using WEBLOGIC. 
      
      
10. Configure the new installation
    • If you made changes to the following files in your  v5 installation, you will need to make the same changes in the new v6 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.

...

• Login as a tenant admin
• Click on the Configuration Checklist link to verify that all configurations are complete
• Login as a tenant designer user
• View and edit a form/flow
• View submissions that existed before
• Test forms/flows 
  

Troubleshooting:

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:

...

Applying a Minor Patch Update

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.  

You can download the latest build from frevvo download page.

...