Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt

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.

End-Of-Life of third party components

Deltares cannot support any release that is marked as end of life by the supplier. For a quick check whether a component is still supported:

Excerpt Include
Third party software End-Of-Life schedules and security bulletins
Third party software End-Of-Life schedules and security bulletins
nopaneltrue

Components

Operating Systems

Excerpt Include
Operating System requirements - 2020.02 and later
Operating System requirements - 2020.02 and later
nopaneltrue

JDK

Excerpt Include
JDK requirement
JDK requirement
nopaneltrue

Central database

Excerpt Include
Central database hardware and software requirements
Central database hardware and software requirements
nopaneltrue

Master Controller Server

Excerpt Include
Master Controller requirements
Master Controller requirements
nopaneltrue

Admin Interface

Excerpt Include
Admin Interface requirements
Admin Interface requirements
nopaneltrue

Operator Client

Excerpt Include
Operator Client requirements
Operator Client requirements
nopaneltrue

Forecasting Shell Server

Excerpt Include
Forecasting Shell requirements
Forecasting Shell requirements
nopaneltrue

Database Proxy

Excerpt Include
Database proxy requirements
Database proxy requirements
nopaneltrue

Deltares Open Archive

Excerpt Include
Deltares Open Archive requirements
Deltares Open Archive requirements
nopaneltrue

FEWS Web Services

Excerpt Include
Delft-FEWS Webservice requirements
Delft-FEWS Webservice requirements
nopaneltrue

Requirements overview

Excerpt Include
Requirements overview - 2018.02 and later
Requirements overview - 2018.02 and later
nopaneltrue

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),  Apache Tomcat for Admin Interface
  • Open 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 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.

Security

Read more about the shared responsibility model. >>

Expand
titleShared responsibility model

Excerpt Include
Security - Shared responsibility model for Delft-FEWS system installations
Security - Shared responsibility model for Delft-FEWS system installations


...