Many clients wish to know what the hardware and operating system requirements are for Delft-FEWS. On this page you can find a list of specifications. If you have any question about the list, or you do not see the operating system of your choice: please contact us. This list is not exhaustive.
Operator clients
The operator client (Gui) is the user end - thick client.
Forecasting Shell Server
The forecasting shell server is the server for execution of forecast runs. It contains the modelling software and it's operation is controlled by the Master Controller
Master Controller Server
The master controller organises task traffic and scheduling
Central Database
This is the central data repository, linked to the master controller. The live system is known to run with the following database versions:
This list is not exhaustive, so contact us if you are thinking of using a different database or a different type.
Webserver
The webserver is an optional server that hosts and distributes the webpages generated by Delft-FEWS. Hardware requirements depend on the intended use.
Virtualization
It is possible to deploy the master-controller components / forecasting shells in virtualized environments. It is recommended to contact the Delft-FEWS product management beforehand so that they may advise on virtualization options.
Component | Description | Hardware requirements | Operating system/ Software requirements | Instances |
---|---|---|---|---|
Operator Client (Gui) | The Delft-FEWS client used by end-users. | client side, normal pc | Windows 7 / 8 / 10, Server 2008 / 2012(R2) Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES 11.x | As many as there are clients |
ConfigManager
| Control and distribute configuration via the Master Controller database. | client side, normal pc | Windows 7 / 8 / 10, Server 2008 / 2012(R2) Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES 11.x | As many as there are application managers |
Forecasting Shell Server | Executes forecast models and stores the results in the central database. | Minimum 2 GB RAM and 1 one CPU core per Forecasting Shell Server instance. CPU typically Intel XEON E5606 2.33 GHz or equivalent. Always reserve 1 CPU core for the OS. | Windows 7 / 8 / 10, Server 2008 / 2012(R2) Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES 11.x
| Recommended minimum 2, more depends on computational load |
Master Controller Server | Dispatches tasks to the Forecasting Shell Servers. Maintenance of central database. Synchronisation between master-controllers. Send system alerts.
| Minimum 1 GB RAM per MC instance. CPU typically Intel XEON 2.33 GHz or equivalent. | Windows 7 / 8 / 10, Server 2008 / 2012(R2) Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES 11.x
| 1 or 2 |
Central Database | Central data repository | See Database vendor requirements + 8 GB RAM per DB server including 1 MC DB instance and. CPU typically Intel XEON E5606 2.33 GHz or equivalent. Add 1 GB RAM per extra MC DB instance. | Oracle 9 / 10 / 11 / 12 PostgreSQL 8.4 / 9.2 / 9.3 / 9.4 MS SQLServer 2008 / 2008R2 / 2012 / 2014 The database instance(s) can be a hosted on an existing database server or cluster. | 1 instance for each Master controller |
Admin Interface | Super-user monitoring, system control and task scheduling | Minimum 1 GB RAM | Apache Tomcat 6 / 7 | 1 |
Archive Server | Stores forecast data, performance indicator data and configurations on a longer time scale than in the central FEWS system. | Ample storage space for Archive files | Apache Tomcat 6 / 7 Separate database instance with same requirements as Central Database for Master Controller. | 1 |
"NFFS/FEWS" Web Server (optional) | For disseminating forecast data and data from other sources | Typically 1 GB RAM per server instance and CPU Intel Xeon 2.33 GHz or equivalent. | Weblogic 11g with an Oracle Database. JBoss as Application Server and Databases PostgreSQL 8.4 and MS SQL Server 2000/2005 supported | 1 or 2 |
The components mentioned above can all be located on one (powerful) server or each on an individual machine, with all possible configurations in between. A typical configuration is:
Typically in a dual master-controller setup every master-controller has its own machine so that maintenance can take place without offline time.