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.

• normal pc
• minimum 512 MB RAM
• operating system: Windows 7 / 8 / 10, Server 2008 / 2012(R2), Linux RedHat / CentOS / SUSE
• amount needed: as many as there are clients
• usable in Citrix

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 / 10, Server 2008 / 2012(R2), Linux RedHat / CentOS / SUSE contains modelling software (incl. licenses), OS usually dependent on 3rd party modules and modelling software
• amount needed: minimum 2, more depends 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 / 10, Server 2008 / 2012(R2), Linux RedHat / CentOS / SUSE, Other Unix-like operating systems possible (e.g. HP-UX, Solaris), as long as there is a Java JRE with the correct version available for the OS.
• A JMS provider such as JBoss 4 / 5 or activeMQ is required but is allowed to be on a separate server. JBoss 4 and 5 cannot function with JRE 8 but require either JRE 6 or JRE 7.
• amount needed: it is recommended to have one machine per master-controller.

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 9 / 10 / 11 / 12
• PostgreSQL 8.4 / 9.2 / 9.3 / 9.4,
• MS SQLServer 2008 / 2008R2 / 2012 / 2014.

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, but generally it is not recommended to have the PiService on the same machine as the master-controller / MQ server.

Requirements overview

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. 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. Virtualization of the Forecasting Shells is currently not recommended for heavy computational models. For every 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 only uses the java JRE in embedded form.