Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Installation

The System Planning Guide explains how to prepare for your PhixFlow installation.

The Installation Guide explains how to install PhixFlow. This explains how to install Tomcat, how to create the PhixFlow database and configure all necessary Server side files.

The PhixFlow Active Directory Guide explains how to configure PhixFlow to delegate user authentication to a Microsoft Active Directory server.

Upgrade

...

Insert excerpt
_Banners
_Banners
nameInstallAndUpgrade
nopaneltrue

Quick installation

If you are setting up an installation of PhixFlow for evaluation, or a platform for development or testing that requires minimal planning, go directly to Installing PhixFlow.

From Proposal to Deployment

The following diagram illustrates a typical process for going from a proposal for a PhixFlow installation to its deployment.

Drawio
simple0
zoom1
inComment0
custContentId8633417859
pageId97734757
diagramDisplayNameproposalToDeploymentJourney.drawio
lbox1
contentVer2
revision2
baseUrlhttps://phixflow.atlassian.net/wiki
diagramNameproposalToDeploymentJourney.drawio
pCenter0
width451
links
tbstyle
height271

The following table provides more details of the stages for this process. 

StageDescriptionReference
Minimum system requirementsAs long as the minimum system requirements are met, you can take any approach and chose any platform configuration you wish.Minimum system requirements

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.
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 and Delivery
PhixFlow installation

At this stage, system administrators

  • install the platform components on the server: Java, Tomcat, databases,
  • install PhixFlow
  • complete essential configuration steps.
Installing PhixFlow
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 MySQL database.

Minimum system requirements, Installing PhixFlow

Upgrading Your PhixFlow Installation

Upgrade the platform components, such as the server operating system, databases, Java and Tomcats as required by the providers. Usually this can be done independently of upgrading PhixFlow. However, the platform components must:

Tip

We recommend that you follow PhixFlow's suggested installation or upgrade method for Java and Tomcat; see:

To upgrade PhixFlow:

  1. Check for any Special Upgrade Instructions that you need to follow
  2. Combine them with the standard steps in Upgrading PhixFlow.

What's Next?

This topic includes the pages:

Child pages (Children Display)
depth4