...
| Anchor | ||||
|---|---|---|---|---|
|
PhixFlow uses any major a JDBC compliant database to store both configuration data and the results of analysis on data collected from other systemsworking data. Existing installations currently use either Oracle or , Microsoft SQL Server and MySQL.
The Database Server may be installed on the same machine as the PhixFlow Application Server to create a "single machine" deployment. Alternatively the Database Server may be installed on a different machine creating a "dual machine" deployment. Both are valid implementations and the deployment choice depends on the preferences of the IT infrastructure team. Figures 1 and 2 show the different deployment options.
Active Directory
In addition to managing users locally within the PhixFlow application, PhixFlow can be integrated with one or more Active Directory servers, allowing users' credentials, passwords and access rights to be managed centrally.
PhixFlow can be connected to multiple Email servers. This allows PhixFlow to process data files received as email attachments, and to publish reports and notifications to users via email.
| Anchor | ||||
|---|---|---|---|---|
|
Because of the nature of PhixFlow, good connectivity to other systems is critical. PhixFlow can be configured to fetch data via Database Collectors, FTP File Collectors and HTTP Collectors In addition PhixFlow can export data files to remote servers over FTP, update any external JDBC compliant database, and invoke web services over HTTP and send emails with file attachments. 
Figure 2 Dual Machine High Level Architecture
...
The PhixFlow Application Server provides the following services:
- Delivers the Deliverfully customized web-based client application applications over http/https
- Provides XML configuration and analysis data over http to the web-based client
- Executes unlimited, configured "analysis models" according to set schedules e.g. daily, every 5 minutes or runs analysis on user request.
- The analysis engine:
- Reads data from other JDBC compliant databases using template SQL configured within the models.
- Reads data from files according to structures configured within the models
- Reads data from websites or web services over HTTP according to logic configured within the models.
- Transforms the data according to rules configured within the models e.g. merges data from different sources, enriches the data using "Excel-like" expressions, performs referential lookups, filters data, aggregates data etc.Creates alarms based on data specific rules
- Initiates workflows based on alarms / data specific rules
- Updates external databases using template SQL or "stored procedure" calls configured within the model
- Exports structured data files e.g. CSV or Excel documents according to structure definitions defined in the model.
- Invokes web services over HTTP based on model parameters
- Emails files and spreadsheets to users
- Creates graphical reports and automatically emails them to configured users according to defined schedulesManages workflows configured within PhixFlow:
- Creates tasks according to the logic configured in workflow models
- Monitors task completion and drives workflow processing
- Creates user tasks Places external tasks on queues and monitors completion
- Creates timer tasks for time dependent logic
- Creates template email tasks to send data and/or provide data dependent messages
- Archives data according to defined, data specific schedules
- Provides user group role based security and secure access to applications, data, charting and reports
- Maintains a full and detailed audit trail
- Maintains a full and detailed log trail of all analysis
...
- UNIX (e.g. Solaris, AIX, HP-UX)
- Linux (e.g. Redhat, Ubuntu, Debian etc.)
- Windows Server (e.g. Window Server 2008)
However PhixFlow has an extremely open architecture and any environment which supports at least version 2.2. of the Java Servlet Specification should support PhixFlow. The recommended servlet container is Tomcat.
...
The following server configuration should be considered a typical minimum environment for PhixFlow deployment. A server with this specification will enable PhixFlow to process typical analysis models for medium sized organisations. For organisations with large analysis requirements e.g. rerating 30+ million events in a single analysis step, then PhixFlow consultants should be engaged to carry out a detailed machine sizing exercise based on the complexity and number of the models that need to be configured and the volume of data that will be processed.
CPU | 2 x Quad-core 2.6 GHz |
Memory | 16 GB (Expandable to 64 GB) |
Disk | 8 x 146 GB in RAID5 configuration |
Operating System | 64 bit Red Hat Linux Enterprise Edition |
Network Connection | 1 Gbit Rj45 Ethernet |
Table 1 Minimum PhixFlow Server
A typical server with this sizing is the HP ProLiant DL380.
| Anchor | ||||
|---|---|---|---|---|
|
The Database Server is any a JDBC compliant database e.g. Oracle, DB2SQL Server, SybaseMySQL, MySQL etc. and is used as an efficient repository for:
- PhixFlow models and other configuration data
- PhixFlow status information.
- PhixFlow analysis working data and results data
| Anchor | ||||
|---|---|---|---|---|
|
...
Because these browser applications run in many operating system environments, PhixFlow also naturally supports UNIX, Linux, Windows and Apple OS.
PhixFlow requires no installation on the client. Users browse to the URL which points at the PhixFlow server and the application launches within an http/https session. This also means that users can access PhixFlow from anywhere in the world provided there is secure http access to the PhixFlow server.
PhixFlow is a "multi-lingual" application i.e. it supports multiple languages in a single instance e.g. for a pan-European organisation a single instance of PhixFlow is able to support native language screens for all users.
...
- Definition of control frameworks i.e. areas of system monitoring or task automation
- Prioritisation support for control design and deployment
- Creation of unlimited analysis models through the drag and drop design screens
- Creation of unlimited workflow models through the drag and drop design screens
- Chart and report definitionAlarm lists and alarm maintenance
- User task lists and task maintenance
- Drag and drop definition of user defined dashboards
- Guided drill down into analysis results to determine root cause analysis
- Evaluation of the effectiveness of the control framework
- User administration
- Scheduled task definition
- Log viewers and drill down for Active and Completed tasks
- Audit trail summaries and detailed drill down
- Archive log viewing and archive restore
- Model import and export via XML
- Base system configuration e.g. status codes, external queues
...