This topic includes the pages:
| Child pages (Children Display) | ||
|---|---|---|
|
...
From Proposal to Deployment
The following diagram illustrates a typcial typical process for going from a proposal to depoymentfor a PhixFlow installation to its deployment.
| Drawio | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
This is by no means the only approach, as described below.
...
The following table provides more details of the stages for this process.
| Stage | Description | 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, Installing PhixFlow | |
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 | Proposal from Sales / proposalteam | 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. | Initial discussions with IT | Infrastructure planning |
| PhixFlow installation | At this stage, system administators
| ProjectInstallation by system administrators | |
| 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
...
Your PhixFlow Installation
Upgrade the platform components (OS, database, Java, Tomcat) are largely indepdent of each other, providing that you meet the such as the server operating system, databases, Java and Tomcatas as required by the providers. Usually this can be done independently of upgrading PhixFlow. However, the platform components must:
- meet PhixFlow's System Requirements and Compatibility
...
Operating system and database
...
- be
...
Java and Tomcat
...
- configured as required for the operation of PhixFlow
...
- .
| Tip |
|---|
We recommend that you follow PhixFlow's suggested installation or upgrade method for Java and Tomcat; |
...
see: |
To upgrade PhixFlow:
- Check for any Special Upgrade Instructions that you need to follow
- Combine them with the standard steps in Upgrading PhixFlow.
...
Configuration
Once PhixFlow installed, you can configure the system. For information about the configuration and ongoing maintenance of PhixFlow, see Administration.
| Tip |
|---|
Remember to install the Theme palettes, which are provided as packages; see Installing Template Packages. |
What's Next?
This topic includes the pages:
| Child pages (Children Display) | ||
|---|---|---|
|