...
...
...
...
...
...
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:
...
- 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
For medium and large implementations the database should be configured for high performance throughput. In particular database performance is significantly affected by the way that the database server disks are configured. Organisations requiring this size of server will generally have their own database administrators who are familiar with this level of planning, however, for clarity the following shows a typical disk configuration:
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 | 4 x 146 GB in RAID 1+0 configuration (Used for Oracle Redo) Format the mirror with a block size of 512 bytes. 2 redo groups multiplexed |
Disk Group 3 | 2 * 146 GB in RAID 1+0 configuration (Used for Oracle Undo) Format the mirror with 4Kb block size |
Linux:
...
Limit on Open File Descriptors
On Linux, set the "open files" limit for the user that will run Tomcat to at least 50,000. By default this value is set to 1024. This setting controls the number of open file descriptors a user can have. You can see the current limit by running the ulimit command:
...
Note that PhixFlow will generally open only a fraction of 50,000 file descriptors, however, it is best to ensure that this limit can never be reached, since otherwise numerous low level errors can occur.
Server Access to Other Systems
Email Server
In order to email reports and alerts to users, PhixFlow requires access to an email account via an SMTP gateway. Please provide PhixFlow with full connection settings e.g.:
Configuration Setting | Example |
Host Address | auth.smtp.xxxx.yy.xx |
Port | 25 |
Username | |
Password | |
SMTP Auth required | true |
Import / Export Data on other Servers
In test and live operation the PhixFlow server will need to gather data from and write data to other systems via JDBC or via FTP. The access requirements change over time as new models are added to PhixFlow. Please ask your PhixFlow administrator for a full list of access requirements documented as:
PhixFlow will require access to the following databases:
System | Access Requirement |
<Name> | For each system provide:
If needed, document individual read/write access requirements:
|
PhixFlow will require access to the following servers and file systems:
System | Access Requirement |
<Name> | For each system provide:
|