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.
The Operator Client (Gui) is the thick client for end users.
The Forecasting Shell Server (FSS) is the server for execution of forecast runs and import tasks. It contains the modelling software and it's operation is controlled by the Master Controller
The master controller organises task traffic and scheduling
Java Messaging Service (JMS) controls a large part of the communication between the components.
This component can often be installed on the same server as the Master Controller.
For the JMS to function properly, it is strongly recommended that clients and master-controller components synchronise with the same NTP server so that they run with the same clock time. |
This is the central data repository, linked to the master controller. The live system is known to run with the following database versions:
Delft-FEWS 2017.02 and later require Oracle 12c |
Delft-FEWS 2017.02 requires MS SQL Server 2012 or later |
PostgreSQL 9.6 or later (9.6 is supported from 2016.01 onwards)
Stop using Postgres 9.2 or earlier, please migrate to a newer Postgres version. Binary transfer is more efficient in newer PostgreSQL versions. |
This list is not exhaustive, so contact us if you are thinking of using a different database or a different type.
The webserver is an optional server that hosts and distributes the webpages generated by Delft-FEWS. Hardware requirements depend on the intended use.
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.
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) | 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) | 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)
| 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)
| 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 | Requires internet browser with javascript and session cookies enabled. 2018.02 requires Tomcat 9, Internet Explorer 10 or older is not supported. 2017.02 and before: Apache Tomcat 6 or higher The web application runs over the Internet, E.g. Internet Explorer, Edge, Firefox, Chrome. | 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) | 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) |
New table: to be included/finalised
Version | Base-build | Operator Client Forecasting Shell | Tomcat |
---|---|---|---|
2019.02 | |||
2018.02 | embedded | openjdk11.0.2 |
|
Version | Product |
---|---|
Delft-FEWS 2018.02 | Tomcat 9 |
Delft-FEWS 2017.02 and before | Tomcat 5, 6, 7, 8, 9 |
Version | Product | JRE version | Windows / Linux | Remarks |
---|---|---|---|---|
Delft-FEWS 2017.02 | No JMS provider required anymore. Direct database access (DDA) is replacing synchronisation via JMS. Https (as supported by JMS) is not supported. | |||
Delft-FEWS 2017.01 | ActiveMQ 5.14.5 | Java JRE 8 |
64 bit (installation of 32 bit is not recommended) | ActiveMQ 5.14.5 requires JRE 8 (best 64 bit), but may also be used with JRE 7. |
Delft-FEWS 2016.02 and older | ActiveMQ 5.11.1 | ActiveMQ 5.11 requires JRE 8 (best 64 bit), but may also be used with JRE 7. | ||
Delft-FEWS 2017.01 and older | JBoss 4 / 5 / 7 | Java JRE 6 / 7 | Does not function with JRE 8. Note that JBoss4 requires a jdbc driver for storing temporary messages. The JRE version with which this driver is compiled should be compatible with the JRE used for Jboss4. |
Executable | Installer | Download location |
---|---|---|
JavaService.exe | Microsoft Visual C++ 2008 Redistributable Package (x86) | https://www.microsoft.com/en-us/download/details.aspx?id=29 |
JavaService_x64.exe | Microsoft Visual C++ 2010 Redistributable Package (x64) | https://www.microsoft.com/en-us/download/details.aspx?id=14632
|