This topic includes the pages:
From proposal to deployment
The following diagram illustrates a typcial process for going from proposal to depoyment.
This is by no means the only approach, as described below.
| Stage of process | Reference | ||
|---|---|---|---|
| Minimum system requirements | As long as the minimum system requirements are met, you can take any approach and chose any platform configuration you wish. | Min system reqs | |
System planning | System planning results: indicative server sizings; proposed network topology; applicable security frameworks; physical location for solution. Often this is enough to support the sales/ proposal stage of the process, although in some cases this step of the process will require further detail, in particular elemetnts of the detailed infrastructure planning | Sales/ proposal | Planning your PhixFlow System |
| Infrastructure planning | This stage usually involves engagement between PhixFlow's technical team and yours. This is a chance to establish things like: software versions number; detailed backup plans; service configurations, including disk partitioning; detailed discussion of network components. | Infrastructure planning | |
| PhixFlow installation | At this stage, the base components for PhixFlow (Java, Tomcat, database, and PhixFlow itself) are installed and intially configured. | ||
| Proof of concept | In many cases, a proof of concept installation of PhixFlow is created early on in discussions, with only minimal consideration of long term planning concerns, and this runs through to the point at which PhixFlow is made available on the fully planned platform. The proof of concept built can be on any platform that meets the minimum system requirements, but we have also provided an example installation that you can run through from initial server creation to a fully operational PhixFlow, based on the Ubuntu distribution of linux, and the MariaDB database. | Min system reqs/ quick install start |
- System planning - establish planning outcomes, indicative server sizings, proposed network topology, security frameworks, location for solution
- Detailed infrastructure planning - servers configuration, including disk partitioning, network and network components, operating system
- PhixFlow installation - PhixFlow platform components (database, Java, Tomcat) and PhixFlow itself
This is by no means . In many virtualised platforms, databases will the either hosted as cloud native (or "serverless"), or will be created using pre-created image which includes partitioning of the server disks as well as the database installation itself.
Overview
Installing or upgrading PhixFlow itself is simple. However, PhixFlow depends on other parts of your system, including:
- databases
- Tomcat
- Java
- drivers.
Making any change to an interdependent system requires planning changes several weeks before you start to make them.
Stage 1: Planning
Several weeks before you intend to install or upgrade PhixFlow, make sure you know what changes you need to make to your existing infrastructure. There is help and information in:
- System Requirements and Compatibility: a list of the third-party software dependencies for each version of PhixFlow.
- Planning your PhixFlow System: what to think about.
Stage 2: Update Dependencies
At least one week before the planned PhixFlow installation or upgrade, complete any changes to your existing infrastructure infrastructure.
Stage 3: Backup
If you are upgrading an existing PhixFlow instance, remember to take a backup of your system.
Stage 4: Install or Upgrade PhixFlow
Installing PhixFlow: this includes how to install Tomcat, how to create the PhixFlow database and configure all necessary server-side files.
For upgrading:
- check for any Special Upgrade Instructions that you need to follow
- and combine them with the standard steps in Upgrading PhixFlow.
Stage 5: Configuration
Once PhixFlow installed, you can configure the system. For information about the configuration and ongoing maintenance of PhixFlow, see Administration.
Remember to install the Theme palettes, which are provided as packages; see Installing Template Packages.