Server Architecture Overview
...
- 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.
...
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 |
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:
- IP address
- Port requirements
- Database/Instance name
- User/Schema
If needed, document individual read/write access requirements:
- Tables, Views, Stored procedures etc.
PhixFlow will require access to the following servers and file systems:
System
Access Requirement
<Name>
For each system provide: