| Warning | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Before you begin the migration process, there are a few migration items that you need to consider. Please read and understand the Planning for v6.2 which may require your action before you begin your upgrade. Determine Your Upgrade Path
Please follow the instructions on this page, to perform your upgrade. Click on the link for the section(s) that apply.
|
...
Upgrading from 5.0 (r22491) or v5.2 patch 8/9+ or v5.3.8 or 6.1
...
Please read the following upgrade steps prior to starting the migration.
...
If you are using the tomcat servlet, follow the steps below to configure the v6.2 <frevvo-home>\tomcat\conf\catalina\localhost\frevvo.xml file for migration.
- 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"/>".
- Set the value of frevvo.users.schemaName in the v6.2 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.
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:
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
Customers upgrading to v6.2 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 v6.2 version frevvo.xml BEFORE starting the v6.2 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 v6.2 UI.
...
- 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.2. 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.2.1 to your installed v6.2 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.
...