Page Comparison

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.

Image Removed

Figure 1  Dual Server High Level Architecture

This page gives some indicative sizings for the servers you will need to run PhixFlow. The exact resource levels you need will depend on the details of your solution, how complex the calculations it has to perform, and how many concurrent users you need to handle. In many virtualised environments it is straightforward to change the level of CPU and memory (see Resizing servers for the server configruation changes you need to make after doing this). It is worth monitoring the performance of PhixFlow and the database to get the right balance of performance and cost.

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 indicative sizings are the same regardless of operating system (Windows or linux) and the chosen database.

...

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

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

...

xx.yy@zz.com

...

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:

Notes:

...