Server Architecture Overview
PhixFlow is built on a single Java-based architecture i.e. it is not made up of several products with different architectures bolted together. There are two main elements in the server architecture:
- PhixFlow Application Server - The PhixFlow application server is a Java-based application which runs within an Apache Tomcat container. PhixFlow supports installation on both Linux and Windows based servers.
- Database Server - PhixFlow uses any major JDBC compliant database to store both configuration data and the results of analysis on data collected from other systems.
See System Requirements and Compatibility for information about supported versions of third party software that should be installed on the PhixFlow server, in particular, databases, Java and Tomcat.
Figure 1 shows the most typical deployment of PhixFlow in which the application server and database server run on separate machines, however, for small proof of concept installations a single server may be used to host both the application and database servers.
Figure 1 Dual Server High Level Architecture
Typical Server Sizes
The following are typical server sizes for small, medium and large installations. For large installations we recommend that you engage a PhixFlow consultant to verify requirements and analyse data volumes to be processed and retained within PhixFlow. Please note that backup/recovery capacity is excluded in these sizing estimates.
...
- The disk space on the application server is sized assuming that there may be files placed on the server disk for PhixFlow to read. If no files are to be placed on the application server (e.g. PhixFlow will read files from an external location) then only a small disk is required for the operating system and PhixFlow application software.
- Note that these figures indicate the amount of database disk storage required which scales with the amount of raw and result data configured to be retained by PhixFlow. Some implementations with a high number of daily records but which only maintain problematic data may require less space than this.
Database Server Disk Configuration
...
- this
...
Disk Group 1
...
8 x 300 GB in RAID5 configuration (Used for Oracle Data Tablespace) Format the stripe with a block size that is optimal for data throughput. (typically 4Kb)
...
Disk Group 2
...
- .
...
Disk Group 3
...