scrollbar |
---|
Table of Contents |
---|
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. ComponentsOperator |
...
clientThe Operator Client (Gui) is the thick client for end users.
|
...
|
...
Forecasting Shell ServerThe Forecasting Shell Server (FSS) is the server for execution of forecast runs and import tasks. It contains the modelling software and it's operation is controlled by the Master Controller
|
...
|
...
|
...
Master Controller ServerThe master controller organises task traffic and scheduling
|
...
|
...
JMS Server (no longer required in 2017.02 and beyond)Java Messaging Service (JMS) controls a large part of the communication between the components.
|
...
|
...
|
...
This component can often be installed on the same server as the Master Controller.
|
...
Central DatabaseThis is the central data repository, linked to the master controller. The live system is known to run with the following database 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
...
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)
...
ConfigManager
...
Control and distribute configuration via the Master Controller database.
...
Windows 7 / 8, 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, Server 2008 / 2012(R2)
Linux RedHat Enterprise, CentOS (6.x 64 bit, 7.x 64 bit) / SLES (11.x, 12.x)
...
This list is not exhaustive, so contact us if you are thinking of using a different database or a different type.
Open ArchiveThe Open Archive is an optional 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 requirementsOpenArchive poses modest requirements to host hardware:
Software requirements
Required permissionsThe file system containing archive data:
WebserverThe webserver is an optional server that hosts and distributes the webpages generated by Delft-FEWS. Hardware requirements depend on the intended use. PiServiceThis 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. Requirements overview
|
...
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)
...
Minimum 1 GB RAM per JMS instance. CPU typically Intel Xeon 2.33 GHz or equivalent. Minimum 1GB disk space for cache.
...
|
...
|
...
|
...
Oracle 10 / 11 / 12
PostgreSQL 9.3 / 9.4
MS SQL Server 2008 / 2008R2 / 2012 / 2014
...
|
...
Super-user monitoring, system control and task scheduling
...
Apache Tomcat 6 / 7
The web application runs over the Internet, E.g. Internet Explorer , FireFox, Chrome, Safari
...
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.
...
Apache Tomcat 6 / 7
Separate database instance with same requirements as Central Database for Master Controller.
...
|
...
Apache Tomcat 6 / 7
Preferrably not on the same machine as the master-controller / MQ server.
...
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 serversThe 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:
Typically in a dual master-controller setup every master-controller has its own machine so that maintenance can take place without offline time. VirtualizationIt 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 computingFEWS 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. Embedded Java JRE software versions and other dependencies
Java JRE versions (from 2018.02)++++++ provisional text ++++++++ In two other locations java is required to run a Delft-FEWS client-server system: in Tomcat (for deploying the Admin Interface or Open Archive) and for the Master Controller. These are part of the server-package we distribute to you. Although these jre's are not embedded, they can be treated similarly with respect to replacing them (or not) by another open source version or commercially supported version of java 11. The decision to arrange additional 'support for Java' is up to the end user of Delft-FEWS. If - at some point in time - crucial (security) fixes are required to the embedded jre in the client-package of Delft-FEWS, Deltares will distribute a new 'base-build' for 2018.02 (or higher). Since the distribution of this (new) base-build will take place via the database (and is uploaded via the Admin Interface), updating of all FSS and OC machines will be rather simple. The update of the base-build (including updated embedded jre) will then take place automatically and will neither be a large maintenance burden nor very time-consuming.
NB. only the jvm.dll and not the java executable is shipped with the base build. The jre release version is listed in windows\jre\release and linux/jre/release. NB2. The Master Controller and Apache Tomcat 9 (Admin Interface, Open Archive, Fews Web Services and Database HTTPS Proxy) are known to work with the OpenJDK 11 as distributed by RedHat, our test suite). Java JRE versions (2017.02 and earlier)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.
Tomcat webcontainer for Admin Interface / PiService / ProxyWhen multiple components require one and the same dll (e.g. for Active Directory / kerberos integration), it is required to run those components in a separate tomcat instance to avoid problems.
JMS providers and their Java JRE versions (no longer present in 2017.02 onwards)
|
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 2016.02 and newer | #todo | Java JRE 8 update 102 | 32 / 64 bit |
64 bit |
32 / 64 bit |
Delft-FEWS 2016.01 | #62543 | 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 |
Java JRE versions for JMS providers
...
JRE version
...
32 / 64 bit
...
|
...
|
...
Windows VC-RedistributablesThe Delft-FEWS software contains Windows executables requiring a VC++ Redistributable Package being installed.
|
...
|
...
|
...
|
...
...
SecurityRead more about the shared responsibility model. >>
|
...