Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

These release notes are for PhixFlow 5.9.0.

...

Table of Contents
maxLevel3

 

...

Installation / Upgrade

Prerequisites

...

PhixFlow 5.9 requires:

Java 7

Apache Tomcat 7

One of:

...

MariaDB (MySQL) 10.0.14 or later

Upgrade

Backup your Database

Ensure that you have a recent full backup of your database. If, for any reason, you need to rollback (see "Rollback Upgrade" below), your PhixFlow configuration and data will revert to this point.

Shutdown

Shut down tomcat. PhixFlow will not be available to users until the upgrade is complete.

Environment

If necessary, upgrade to supported versions of Java, Tomcat and Oracle, SQL Server or MySQL / MariaDB.

See above for details.

Unzip the PhixFlow Release

Unzip the PhixFlow release package into a temporary directory.

We will refer to the new PhixFlow release as $RELEASE.

Install the new Webapp

Move the live phixflow installation, i.e. the directory $TOMCAT/webapps/phixflow, to an archive location.

E.g. on unix/linux: mv $TOMCAT/webapps/phixflow $ARCHIVE/phixflow-<current date>

Copy $RELEASE/webapp/phixflow to $TOMCAT/webapps.

E.g. on unix/linux: cp $RELEASE/webapp/phixflow $TOMCAT/webapps/phixflow

Copy the following files from the WEB-INF/classes directory in the archive of the live installation into the corresponding directry in the new phixflow webapp:

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

E.g. copy $CV_ARCHIVE/phixflow-<current date>/WEB-INF/classes, to $TOMCAT/webapps/phixflow/WEB-INF/classes

Upgrade the Database

Ensure all migration scripts are run in sequence from prior version to this version e.g.:

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

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

Re-start Tomcat

...

The Email Sender and Fetcher accounts were previously configured in XML files. From 5.9 they are configured via the GUI.

The migration process is manual. If you have configured email accounts prior to5.9, you must re-enter the Email Account settings into the new configuration forms:

Email Sender
  1. Make a backup copy of the phixflow-datasource.xml file.
  2. Open the phixflow-datasource.xml file.
  3. Note the port, host, username, password and javaMailProperties values.
  4. Delete the mailSender bean from the phixflow.datasource.xml file.
  5. In PhixFlow go to AdminManage Email Accounts and add a new account.
  6. Tick the Outbound flag, type the account name and enter values from the step 2. The Properties have format: property.name=value. Each property should be entered in new line. Tick Enabled.

Info

You can test the configuration by entering a test email address and sending a test email by clicking the Test Configuration button.

Email Fetcher

  1. Make a backup copy of the phixflow-email.xml file.
  2. Open the phixflow-email.xml file.
  3. Note the enabled, port, host, protocol, username and password values.
  4. Delete the phixflow-email.xml file.
  5. In PhixFlow go to AdminManage Email Accounts and add a new account.
  6. Leave the Outbound flag unticked, type the account name and Enter values from the step 2. If you leave the Pooling Interval blank, the pollingInterval value configured in the server.properties file will be used.

Info

You can test the configuration by clicking the Test Configuration button.

Complete

...

Installation

To install a new PhixFlow instance, follow the standard installation instructions.

Upgrade

To upgrade an existing PhixFlow instance, follow the Standard Upgrade Instructions plus the special instructions for all intermediate releases.

This release includes these special instructions.

 

...

Features / Improvements

...