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 (and cost estimates); 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 and delivery | 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. 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, so the database installation may be covered in some detail, and indeed fully delivered, at this stage. | 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 |
Upgrading
Upgrading PhixFlow and any of the platform components (OS, database, Java, Tomcat) are largely indepdent of each other, providing that you meet the System Requirements and Compatibility.
Operating system and database
Upgrades to operating systems and databases can be performed as standard (i.e. according to the instructions of the provider).
Java and Tomcat
This is also true for Java and Tomcat, providing that these are then configured as required for the operation of PhixFlow (see Install Tomcat), but in general we recommend that you follow PhixFlow's suggested installation method for Java and Tomcat; in turn, there are pages that cover upgrading these components in line with the recommended installation methiod.
PhixFlow
- Check for any Special Upgrade Instructions that you need to follow
- 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.