Versions Compared

Key

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

...

  • 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

...

Open Archive

The webserver Open Archive is an optional server that hosts and distributes the webpages generated by component for Delft-FEWS that stores forecast data, performance indicator data and configurations on a longer time scale than in the central database of the Delft-FEWS system.

Hardware requirements

...

OpenArchive poses modest requirements to host hardware:

  • Storage. The most important requirement for the file system is that it keeps on functioning after the failure of a single disk. Any RAID (https://nl.wikipedia.org/wiki/Redundant_array_of_independent_disks) will be sufficient.
  • Memory. The server should have at least 4 GB memory available for the elasticsearch catalogue and the tomcat instance which hosts the archive server.
  • CPU. The speed of the catalogue (searching in the archive) depends heavily on the CPUs of the server. It is recommended to have at least 4 CPUs available.
Software requirements
  • The archive is a web application running inside a tomcat web server. Both Linux and Windows are supported.
Required permissions

The file system containing archive data:

  • Must be accessible by the THREDDS server with read permissions.
  • Must be accessible by the Deltares Archive Server with full permissions.
  • Must be accessible by the Forecasting Shell Servers with write permission

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

PiService

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.

...

For disseminating forecast data and data from other sources33 GHz or equivalent.Typically 1 GB RAM per server instance and CPU .No longer supported in 2017.02, please migrate to the open archive. 6 / Separate database instance with same requirements as Central Database for Master Controller.
ComponentDescriptionHardware requirementsOperating system / Software requirementsInstances
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)


Contains modelling software (incl. licenses), OS usually dependent on 3rd party modules and modelling software

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)


Other Unix-like operating systems possible (e.g. HP-UX, Solaris), as long as there is a JDK of the correct version available for the OS. For 2017.01 and before, JBoss 4 / 5 or ActiveMQ are required for the JMS layer.

1 or 2
Central DatabaseCentral 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, Chromethe 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 sourcesTypically 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 "NFFS/FEWS" Web Server (optional)
PiService (optional)Data access component.Typically 1 GB RAM per server instance and CPU Intel Xeon 2.Weblogic 11g with an Oracle Database. Weblogic as Application Server .One instance per Master-Controller machine (optional)PiService (optional)Data access component.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 ServerMessaging 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

Apache Tomcat 6 / 7 or later

Preferrably not on the same machine as the master-controller / MQ server.

1 (optional)
JMS ServerMessaging 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

. 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)
Open Archive

New version of the Archive Server replacing the old one.

Stores forecast data, performance indicator data and configurations on a longer time scale than in the central FEWS system.

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

7 or later

(for 2018.02 Apache Tomcat 9)

JRE for running Apache Tomcat version 8 (for 2018.02 OpenJDK version 11)

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.

...