Versions Compared

Old Version 14

changes.mady.by.user Anthony George

Saved on

compared with

New Version Current

changes.mady.by.user Fiona Sargeant

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: removed phixflow-domains.xml

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 for details, but in brief, make sure that any additional JDBC drivers you use are placed in:

...

  • phixflow-datasource.xml
  • phixflow-instance.xmlphixflow-domains.xml
  • log4j.properties
  • phixflow-login.xml

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.

...

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.

Specifically, one of the following must be true:

  • the migration user has SUPER privilege, or
    • the mysql global variable '

    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:

    • Your session has the log_bin_trust_function_creators setting switched on. You can do this with the command:
    Code Block
    set global log_bin_trust_function_creators
    ' is set to trueIf neither are true, the migration script may fail and would require manual recovery
     = 1;
    • Or that the migration user has SUPER privilege.


    Code Block
    titleE.g. for MariaDB users
    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

    ...