Versions Compared

Key

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

This topic is for system administrators. It describes how to install a new instance of PhixFlow.

Prerequisites

Before you start installing PhixFlow, please complete the steps in Planning your PhixFlow System. Your IT system must meet the PhixFlow PhixFlow Minimum system requirements. In particular, you must have:

  • installed a database server
  • configured a database instance or schema and the user or login credentials
  • installed a (Linux or Windows) server to act as the web-application (webapp) host.

Optionally, you can install a Linux or Windows server to act as the reverse proxy / HTTPS proxy

If you are setting up an installation of PhixFlow for evalution, or a platform for development or testing that requires minimal planning, you can go straight into the installation process below.

If you are installing a large and/ or long-running installation of PhixFlow, please complete the planning steps described in Planning your PhixFlow System and Infrastructure Planning and Delivery.

Summary Installation Instructions

...

Do not run Tomcat as root on Linux as this constitutes a security risk.

Install reverse proxy and configure HTTPS:

Required or recommendedPage with detailsSummary
Required if Java is not already installedInstall JavaDownload and install Java.
Required if Tomcat is not already installedRequired

Install Tomcat

Download and install the Apache Tomcat web-application (webapp) server.
Recommended

Configure Tomcat for HTTPS

You are responsible for ensuring all PhixFlow communication is secure.

  • Either use HTTP communication behind a secure firewall.
  • Or you must configure Tomcat to use HTTPS communication with the PhixFlow webapp. You must also disable HTTP access to the webapp.
Recommended

Linux: Install Pound Reverse Proxy

Windows: Microsoft blog post about IIS as a reverse proxy

If you want to make your web server visible on the default ports (e.g. on Linux, http: 80, https: 443) we recommend that you use a reverse proxy to terminate the HTTPS session and to forward web requests using HTTP to the Tomcat server. The proxy and Tomcat servers must run on a private network or on the same server and the Tomcat server must not be directly accessible to normal users. In this configuration, the reverse proxy runs as root, which allows it:

  • to use privileged ports (up to port 1000)
  • to forward requests to the web server, which runs:
    • as a non-privileged user (normally 'tomcat')
    • on non-privileged ports (above 1000).

Options for reverse proxy servers are:

  • On Linux servers, Pound 
  • On Windows servers, IIS.
Warning
titleTomcat on Linux
Set up a reverse proxy to help manage the load on the PhixFlow server, offer secure connections over HTTPS, and help with certificate management for multiple instances of PhixFlow.


OptionalInstall LibreOfficeThis is only needed if you want to generate PDF versions of files to export or send via email (Configuring PDF Conversion)
RequiredUnpack PhixFlow Release Package

If you do not already have the PhixFlow package to install, you can download it from our support FTP site. Please email support@phixflow.com.

Log on to the webapp host and unpack the release package.

RequiredInstall the PhixFlow Database Schema

Create a database user and tables. Populate the tables with initial configuration data and set the customer name. See also the details in Database URLs.

OptionalSQLServer MS SQL Server Integrated AuthenticationEnable server support for integrated user authentication.
RequiredInstall the PhixFlow WebappCopy the PhixFlow webapp from the unpacked release package into Tomcat and configure it.
RequiredConfigure a Keystore and Aliases

Create a keystore for the database credentials and their aliases. Configure the following files to use the keystore:

  • phixflow-datasource.xml
  • phixflow-secret.xml
  • an environment variable (recommended).
RequiredStart PhixFlow on the Clientand Configure

Check that the application is running by starting the client and logging in with the username startup and password: Startup.

...