System planning

System planning to clarify the sales proposal. This includes deciding:

• the size of server required, with cost estimates
• network topology
• security frameworks
• physical location of servers
• any other details for 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.

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.

At this stage, system administators

• install the platfrom components on the server: Java, Tomcat, databases,
• install PhixFlow
• complete essential configuration steps.

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.