These are the minimum system requirements for running PhixFlow
They do not include adminstrative administrative access, which can be set up as standard by you for administration of the servers and databases.
Most PhixFlow operators perfrom 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.
...
The following is a recommended minimum specification for users' computers:
Memory | 4 GB |
CPU Speed | 2 GHz |
Disk | N/A (nothing is installed on the client machine) |
Resolution | 1280x800 |
Browser | PhixFlow supports any standard browser. See System Requirements and Compatibility. |
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.
Application server | Database server | |
|---|---|---|
Protocol | JDCB | JDCB |
Commonly used ports | Depends on database | Depends on database |
Typical L3/4 firewall rule | Traffic Type: TCP Port: (as above) Direction: outgoing | Traffic Type: TCP Port: (as above) Direction: incoming |
PhixFlow configuration reference |
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.
PhixFlow (Tomcat) | |
|---|---|
Protocol | HTTP |
Commonly used ports | 8080 |
Typical L3/4 firewall rule | Traffic Type: TCP Port: (as above) Direction: incoming |
PhixFlow configuration reference |
Access to third party systems
...
In each case you will need credentials that link to a user which has the requireed required access (read, write, etc.) to the required resources.
...
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 typcial 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:
Remote database | Remote file server | Web service | ||
|---|---|---|---|---|
Protocol | SMTP | JDBC | FTP | HTTP |
Commonly used ports | 25, 587 | Depends on third party database | 22 | 443 |
Typical L3/4 firewall rule | Traffic Type: TCP Port: (as above) Direction: outgoing | Traffic Type: TCP Port: (as above) Direction: outgoing | Traffic type: TCP Port: (as above) Direction: outgoing for collection, incoming for |
receipt | Traffic type: TCP Port: (as above) Direction: outgoing | |||
PhixFlow configuration reference |