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
...
| Required or recommended | Page with details | Summary |
|---|---|---|
| Required if Java is not already installed | Install Java | Download and install Java. |
| Required if Tomcat is not already installedRequired | Download and install the Apache Tomcat web-application (webapp) server. | |
| Recommended | For secure communications, you must configure Tomcat to use HTTPS. PhixFlow must be configured:
| |
| Recommended | Linux: Install Pound 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:
Options for reverse proxy servers are:
|
Install reverse proxy and configure HTTPS:
| 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. | |
| Optional | Install LibreOffice | This is only needed if you want to generate PDF versions of files to export or send via email (Configuring PDF Conversion) |
| Required | Unpack 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 Log on to the webapp host and unpack the release package. |
| Required | Install the PhixFlow Database Schema | Create a database user and tables. Populate the tables with initial configuration data and set the customer name. See See also the details in Database URLs. |
| Optional | SQLServer MS SQL Server Integrated Authentication | Enable server support for integrated user authentication. |
| Required | Install the PhixFlow Webapp | Copy the PhixFlow webapp from the unpacked release package into Tomcat and configure it. |
| Required | Configure a Keystore and Aliases | Create a keystore for the database credentials and their aliases. Configure the following files to use the keystore:
|
| Required | Start 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. |
| Warning | ||
|---|---|---|
| ||
Do not run Tomcat as root on Linux as this constitutes a security risk. |
...
After Installation
After Once PhixFlow is installed, there are system set-up and configuration tasks:
...
,
...
see
...
- Configure Active Directory Integration: users are authenticated using one or more Active Directory servers in addition to users that are defined locally within the PhixFlow database.
- Configure SAML Integration: map the PhixFlow user groups to user groups in your existing single-sign-on system.
...
Administration for details of the configuration steps required immediately after installation, as well as the ongoing configuration and maintenance tasks.