These are the general steps that you should always follow when upgrading and existing PhixFlow instance from one release to another.
...
If necessary, upgrade to supported versions of Java, Tomcat and Oracle, SQL Server or MySQL / MariaDB.
See above 1051526346for details.
Remember, if you are upgrading tomcat, to restore any JDBC drivers needed for datasources that use database technologies or versions not supported for PhixFlow's own connections. See Install Tomcat Installation for details, but in brief, make sure that any additional JDBC drivers you use are placed in:
...
- phixflow-datasource.xml
- phixflow-instance.xml
- log4j.properties
- phixflow-domainslogin.xmllog4j.properties
E.g. copy $CV_ARCHIVE/phixflow-<current date>/WEB-INF/classes, to $TOMCAT/webapps/phixflow/WEB-INF/classes
If you have configured PhixFlow to show your company logo, also copy $TOMCAT/webapps/phixflow/gui/images/customerLogo.svg. from the archive to the corresponding directory in the new PhixFlow webapp.
Upgrade the Database
Run all migration scripts run in sequence from the starting version to this version e.g.:.
| Note | ||
|---|---|---|
| ||
Please note that some of the scripts can generate warning messages. One example of this is Caution: Changing any part of an object name could break scripts and stored procedures. Generally, these warning messages do not indicate a problem. However, in the event that you see any error messages, please contact your PhixFlow support team. |
Oracle
E.g. for Oracle users:
| Code Block |
|---|
cd $RELEASE/schema/oracle/migration/X.Y sqlplus myUsername/myPassword @migrate_schema_from_x_y_z_to_X_Y_Z.sql |
SQL Server
E.g. for SQL Server users:
| Code Block |
|---|
cd $RELEASE/schema/sqlserver/migration/X.Y sqlcmd -S myServer\myInstance -U myUsername -P myPassword -d myDatabase -i migrate_schema_from_x_y_z_to_X_Y_Z.sql |
| Note | ||
|---|---|---|
| ||
Please note that some of the scripts can generate warning messages. One example of this is Caution: Changing any part of an object name could break scripts and stored procedures. Generally, these warning messages do not indicate a problem. However, in the event that you see any error messages, please contact your PhixFlow support team. |
Re-start Tomcat
Import new Templates package
Go to the Administration Menu → Import Configuration.
Select the new Templates file from {phixflow_release_folder}/install/phixflow_templates_{version_number}. The system will import new templates set (Styles, Layout Templates, Palettes). The user can choose to use new templates or stay with the current ones.
...
MariaDB (MySQL)
| Warning | ||
|---|---|---|
Some MariaDB PhixFlow migration scripts create or use privileged functions and/or procedures, and must have privileges not required by the regular PhixFlow user. You can permanently allow functions like this to run by updating a setting in your my.cnf file. See Running non-deterministic functions in MariaDB for details. If you do not make this change, then you must make sure that either:
|
| Code Block | ||
|---|---|---|
| ||
cd $RELEASE/schema/sqlserver/migration/X.Y
mysql -h myServer -u myUsername -p -D myDatabase
source migrate_schema_from_x_y_z_to_X_Y_Z.sql |
Re-start Tomcat
Complete
The upgrade is now complete.