Versions Compared

Key

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


Excerpt

Children Display
alltrue
pageDelft-FEWS supported release versions

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, 1 GB RAM
  • operating system: Windows 7 / 8 / 10, Server 2008 / 2012(R2), Linux RedHat / CentOS / SUSE
  • amount needed: as many as there are clients
  • possibilities to use under 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

  • advised internal memory and CPU: Minimum 2 GB RAM and 1 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
  • a master-controller can use Windows and linux forecasting shells simultaneously

Master Controller Server
The master controller organises task traffic and scheduling

  • advised internal memory and CPU: 1 GB RAM per MC 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.

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.

Requirements overview

 

...

The Delft-FEWS client used by end-users.

...

Windows 7 / 8 / 10, Server 2008 / 2012(R2)

Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES (11.x, 12.x)

...

ConfigManager

 

...

Control and distribute configuration via the Master Controller database.

...

Windows 7 / 8 / 10, Server 2008 / 2012(R2)

Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES (11.x, 12.x)

...

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 2008 / 2012(R2)

Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES (11.x, 12.x)

...

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 2008 / 2012(R2)

Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES (11.x, 12.x)

...

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 9 / 10 / 11 / 12

PostgreSQL 8.4 / 9.2 / 9.3 / 9.4

MS SQLServer 2008 / 2008R2 / 2012 / 2014

...

Super-user monitoring, system control and task scheduling

...

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

...

Apache Tomcat 6 / 7

Separate database instance with same requirements as Central Database for Master Controller.

...

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.

Java JRE versions

Note that java should never be installed in a browser. Delft-FEWS only uses the java JRE in embedded form.

...