...
Many clients wish to know what the hardware and operating system requirements are for a Delft-FEWS live system. 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.
Components
Operator client
The Operator Client (Gui) is the thick client for end users.
...
This is an optional service which allows SOAP clients to interact with and retrieve data from the Delft-FEWS system. Hardware requirements depend on the intended use. In general it is not recommended to have the PiService on the same machine as the master-controller.
Requirements overview
| Component | Description | Hardware requirements | Operating system / Software requirements | Instances |
|---|---|---|---|---|
| Operator Client (Gui) | The Delft-FEWS client used by end-users. | client side, normal pc Screen resolution depends upon the hardware supplied not on the Delft-FEWS software | Windows 7 / 8 / 10, Server 2012(R2), 2016 Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES (11.x, 12.x) | As many as there are clients |
ConfigManager
| Control and distribute configuration via the Master Controller database. | client side, normal pc | Windows 7 / 8, Server 2012(R2), 2016 Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES (11.x, 12.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 2012(R2), 2016 Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES (11.x, 12.x)
| recommended minimum 2, add more depending on computational load |
| Master Controller Server | Dispatches tasks to the Forecasting Shell Servers. Maintenance of central database. Synchronisation between master-controllers. Sends system alerts.
| Minimum 1 GB RAM per MC instance. CPU typically Intel Xeon 2.33 GHz or equivalent. | Windows 7 / 8 / 10, Server 2012(R2), 2016 Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES (11.x, 12.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 10 / 11 / 12 for versions up to Delft-FEWS 2017.01, Oracle 12c for Delft-FEWS 2017.02 and later PostgreSQL 9.6 MS SQL Server 2012 / 2014 / 2016 MS SQL Server 2012 or later for Delft-FEWS 2017.02 and later. The database instance(s) can be a hosted on an existing database server or cluster. | One instance per Master controller |
| Admin Interface | Super-user monitoring, system control and task scheduling | Minimum 1 GB RAM | 2018.02 requires Tomcat 9 2017.02 and before: Apache Tomcat 6 or higher The web application runs over the Internet, E.g. Internet Explorer , FireFox, Chrome, Safari | One instance per Master-Controller machine |
| "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. Weblogic as Application Server . | One instance per Master-Controller machine (optional) |
| PiService (optional) | Data access component. | Typically 1 GB RAM per server instance and CPU Intel Xeon 2.33 GHz or equivalent. | Apache Tomcat 6 / 7 or later Preferrably not on the same machine as the master-controller / MQ server. | 1 (optional) |
| JMS Server | Messaging communication between FEWS components | No longer present in 2017.02. Minimum 1 GB RAM per JMS instance. CPU typically Intel Xeon 2.33 GHz or equivalent. Minimum 1GB disk space for cache. | Windows 7 / 8, Server 2012(R2) (32bit, 64bit) Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES (11.x, 12.x) | One instance per Master controller |
| Archive Server (optional) | Stores forecast data, performance indicator data and configurations on a longer time scale than in the central FEWS system. For new projects consider using the Deltares Open Archive instead. | No longer supported in 2017.02, please migrate to the open archive. Ample storage space for Archive files | Apache Tomcat 6 / 7 or later Separate database instance with same requirements as Central Database for Master Controller. | 1 (optional) |
...
Typically in a dual master-controller setup every master-controller has its own machine so that maintenance can take place without offline time.
Virtualization
It is very well possible to deploy the master-controller components / forecasting shells in virtualized environments. The Deltares ICT team has most experience with Delft-FEWS on VMWare VSphere with in-depth knowledge but Delft-FEWS is also known to run on Microsoft Hyper-V. Virtualization of the Delft-FEWS back-end services can generally be done without problems. Take into account that (not Delft-FEWS related) modelling software may have other requirements or limitations with respect to virtualization of the Forecasting Shells.
Grid computing
FEWS can work with grid computing. Especially when working with heavy computations, e.g. ensemble forecasting or 3d hydraulic computing, this can be an interesting option to explore. It is recommended to contact the Delft-FEWS product management beforehand.
...