PhixFlow Help

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

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 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.

Summary Installation Instructions

Tha pages in this topic guide you through a complete PhixFlow installation. A summary of the steps is:

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

Install Tomcat


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

Configure Tomcat for HTTPS

For secure communications, you must configure Tomcat to use HTTPS. PhixFlow must be configured:

  • to allow HTTPS connections to the webapp
  • to disable HTTP access.

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. 

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).

This solution requires that:

  • the proxy and Tomcat servers run on a private network or on the same server

  • and that the Tomcat server is not directly accessible to normal users.

Options for reverse proxy servers are:

  • On Linux servers, Pound 
  • On Windows servers, IIS.
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.

Logon 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 Integrated AuthenticationEnable server support for integrated user authentication.
RequiredInstall PhixFlow WebappCopy the PhixFlow webapp from the unpacked release package into Tomcat and configure it.
RequiredStart PhixFlow on the Client

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


Tomcat on Linux

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

System Configuration After Installation

After PhixFlow is installed, there are system set-up and configuration tasks:

  • Configure the system directories; see System Configuration. The Temporary File Location is especially important as it is used when exporting and importing files between PhixFlow instances.
  • Create new users, including at least one administrator; see User Administration. When you have a working administrator login, you must disable or delete the startup user.
  • Optionally, configure PhixFlow to integrate with other authentication systems
  • PhixFlow can be configured to have a hot stand-by webapp shadowing the active webapp, such that the standby webapp will automatically take over in the event that the active server fails; see Configuring for Resilience.


  • No labels