These are the minimum system requirements for running PhixFlow

They do not include administrative access, which can be set up as standard by you for administration of the servers and databases.

Most PhixFlow operators perform at least a minimal system planning exercise (Planning your PhixFlow System), but this is not strictly necessary if you can meet these minimal requirements.

Platform requirements

System Requirements and Compatibility

Users' computers

The following is a recommended minimum specification for users' computers:

Connection from Tomcat to database

The installation must allow for a connection from the server which hosts Tomcat to the database that hosts PhixFlow. Although in general PhixFlow will be installed with the application (Tomcat) running on one server, and the database on another (see ***), it is possible to run with Tomcat and the database all on the same server. In this case, making the connection is straightforward because it is just to another service on the same server.

Client access

A connection open to all users which routes them to Tomcat on the configured listener port (usually 8080), as below. This can be through any type or firewall or gateway, or a VPN. In most cases, a reverse proxy or application gateway will handle the incoming requests and route them over a private network to Tomcat at the required port. However, these connections can be made directly to the tomcat listener port.

Access to third party systems

You must allow for access to required third party systems. By default, PhixFlow does not need access to any third party systems; the needs of your solution will dictate what connections are needed.

In each case you will need credentials that link to a user which has the required access (read, write, etc.) to the required resources.

In the table features of each type of connection have been listed.

An example Layer 3/4 route rule has also been provided for illustration, but that does not mean PhixFlow must be behind a Layer 3/4 firewall rule, not is limited to being behind such a firewall. This is merely to illustrate a typical set up on a commonly used network component. Further, this is only to illustrate potential changes to the network components that protect PhixFlow; matching rules will be needed at the remote end of each connection on the third party systems to allow the connections to proceed.

Common integrations are: