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.
Operator clients
The Operator Client (Gui) is the thick client for end users.
- normal pc
- minimum 512 MB RAM, 1GB recommended
- operating system: Windows 7 / 8, Server 2008 / 2012(R2), Linux RedHat / CentOS / SUSE
- amount needed: as many as there are clients
- usable in Citrix
- users run with their own log on credential, no admin privileges required
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
- minimum 2 GB RAM
- one CPU core per FSS instance,
- CPU typically Intel Xeon 2.33 GHz or equivalent.
- operating system: Windows 7 / 8, Server 2008 / 2012(R2), Linux RedHat / CentOS / SUSE contains modelling software (incl. licenses), OS usually dependent on 3rd party modules and modelling software
- recommended minimum 2, add more depending on computational load
- Windows and linux forecasting shells can be used simultaneously
Master Controller Server
The master controller organises task traffic and scheduling
- minimum 1 GB RAM per Master Controller instance
- CPU typically Intel Xeon 2.33 GHz or equivalent.
- operating system: Windows 7 / 8, Server 2008 / 2012(R2), Linux RedHat / CentOS / SUS. Other Unix-like operating systems are possible (e.g. HP-UX, Solaris), as long as there is a Java JRE with the correct version available for the OS.
JMS Server
Java Messaging Service (JMS) controls a large part of the communication between the components.
- minimum 1GB RAM per JMS instance
- minimum 1GB disk space for caching purposes:
- CPU typically Intel Xeon 2.33 GHz or equivalent
- operating system: Windows 7 / 8, Server 2008 / 2012(R2), Linux RedHat / CentOS / SUSE
- Supported JMS Servers: JBoss 4, JBoss 5, AcitveMQ 5.11 (as of release 2015.02 default JMS)
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.
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:
- Oracle 10 / 11 / 12 for versions up to Delft-FEWS 2017.01, Oracle 12c for Delft-FEWS-12017.02
Delft-FEWS 2017.02 requires Oracle 12c
- MS SQL Server 2008 / 2008R2 / 2012 / 2014
- PostgreSQL 9.4 / 9.5 / 9.6 (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.
- advised internal memory and CPU: See Database vendor requirements. Typically 1 GB RAM per DB instance and CPU Intel Xeon 2.33 GHz or equivalent.
- The database instance(s) can be a hosted on an existing database server or cluster.
- uses 1 instance for each Master controller
Webserver
The webserver is an optional server that hosts and distributes the webpages generated by Delft-FEWS. Hardware requirements depend on the intended use.
PiService
This is an optional service which allows SOAP clients to interact with and retrieve data from the 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 / MQ server.
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, Server 2008 / 2012(R2) 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 2008 / 2012(R2) 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, Server 2008 / 2012(R2) 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, Server 2008 / 2012(R2) Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES (11.x, 12.x)
| 1 or 2 |
JMS Server | Messaging communication between FEWS components | 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 2008 / 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 |
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 PostgreSQL 9.4 / 9.5 / 9.6 MS SQL Server 2008 / 2008R2 / 2012 / 2014 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 | Apache Tomcat 6 / 7 The web application runs over the Internet, E.g. Internet Explorer , FireFox, Chrome, Safari | One instance per Master-Controller machine |
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. | Ample storage space for Archive files | Apache Tomcat 6 / 7 Separate database instance with same requirements as Central Database for Master Controller. | 1 (optional) |
"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 Preferrably not on the same machine as the master-controller / MQ server. | 1 (optional) |
All activities contribute to resource consumption on a computing box, whether that box is hardware or virtual and Delft-FEWS will consume resources when running.
Scalability, number of servers
The components mentioned above can all be located on one (powerful) server or each on an individual machine, with all possible configurations in between. It is however common practice to separate the Forecasting Shell server from the Master-controller server. When using multiple machines it is essential that all machines have matching clocks. This can be achieved by making use of one and the same ntp server.
A typical configuration is:
- Master Controller server running Master Controller(s), Application Server (JBoss or Weblogic), Apache Tomcat for Admin Interface and Archive Server
- Database Server
- Forecasting Shell Server(s)
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 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. 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. Best practice is to build small appliances so that the Master Controller, MQ Server (Jboss / ActiveMQ) and Tomcat Servlet Engine (Admin Interface) all have their separate virtual machines. This setup guarantees the individual components do not compete for the same resources such as CPU and memory. Virtualization of the Forecasting Shells is currently not recommended for heavy computational models. When using virtualization, for every logical Forecasting shell there should be a separate virtual forecasting shell server. The number of virtual processor cores issued should never exceed the number of physical cores for 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.
Java JRE versions
Note that for security reasons, java should never be installed inside a browser. Delft-FEWS should only be using the java JRE in embedded form.
Since 2014.01 Delft-FEWS requires a base-build. This base-build requires a (minimal) jre-version. See the table below. For 2015.01, 2015.02 and 2016.01 with Java JRE 8 upgrades above _100, a new base-build is required.
Version | Base-build | JRE version | Operator Client / Forecasting Shell Server / ConfigManager | Master-controller / Tomcat | |
---|---|---|---|---|---|
Windows | Linux | ||||
Delft-FEWS 2017.01 | #67816 | Java JRE 8 update 131 | 32 / 64 bit | 64 bit |
32 / 64 bit
|
Delft-FEWS 2016.02 | #68073 | Java JRE 8 update 102 | 32 / 64 bit |
64 bit | |
Delft-FEWS 2016.01 | #62571 | Java JRE 8 update 100+ | 32 / 64 bit (beta) | ||
#62088 | Java JRE 8 update 77 | ||||
Delft-FEWS 2015.02 | #62545 | Java JRE 8 update 100+ |
32 bit | ||
#57990 | Java JRE 8 update 45 | ||||
Delft-FEWS 2015.01 | #62465 | Java JRE 8 update 100+ | |||
#54888 | Java JRE 8 update 45 | ||||
Delft-FEWS 2014.02 | #50595 | Java JRE 7 update 71 | |||
Delft-FEWS 2013.01 - 2014.01 | n/a | Java JRE 7 update 71 | |||
Delft-FEWS before 2013.01 | n/a | Java JRE 6 update 45 |
JMS providers and their Java JRE versions (no longer required in 2017.02)
Version | Product | JRE version | Windows / Linux | Remarks |
---|---|---|---|---|
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. |
Windows VC-Redistributables
The Delft-FEWS software contains Windows executables requiring a VC++ Redistributable Package being installed.
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
|