Excerpt | ||||||
---|---|---|---|---|---|---|
|
...
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.
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
| ||||||||
Component | Description | Hardware requirements | Operating system / Software requirements | Instances | ||||
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. | 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. | 1 or 2 |
Central Database | Central 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 12c, 18c, 19c for Delft-FEWS 2017.02 and later Oracle 10 / 11 / 12 for versions up to Delft-FEWS 2017.01, PostgreSQL 9.6, PostgreSQL 11. 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. Supported browsers in preferred order :
2017.02 and before: Apache Tomcat 6 or higher The web application runs over the 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 sources | Typically 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 (optional) | ||||
PiService (optional) | Data access component. | Typically 1 GB RAM per server instance and CPU 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 Server | Messaging 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 | ||||
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. | Ample storage space for Archive files | 1 (optional) |
Warning |
---|
Before starting to use Oracle JRE packages released after April 2019, please be aware of changes in the Oracle Java License model, see https://java.com/en/download/release_notice.jsp. Our software is known to work with the following OpenJDK alternatives (recommended):
|
Java JRE versions (from 2018.02)
++++++ provisional text ++++++++
The new client-package of Delft-FEWS 2018.02 (OC/CM/SA/FSS) will contain a 'embedded' stripped-down jre (java runtime environment) based on OpenJDK 11. Together with the Delft-FEWS binaries, it forms the Delft-FEWS base-build. The java runtime libraries are placed in an operating system specific sub-folder in the well-known Delft-FEWS bin folder. The jre sub-folders are clearly recognizable under /bin/windows/jre or /bin/linux/jre. This jre can be easily replaced by any other open source or commercially supported version of java 11. Since an Operator Client/Stand Alone and in most cases also Forecasting Shell Server run in a controlled (and secured) environment, it is not necessary to have this jre sub-folder replaced, although it is technically feasible.
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.
Warning | ||
---|---|---|
| ||
The openJDK supplied in 2018.02 and later is not the full JDK but bundled by the jlink executable to a stripped-down JRE with only those modules that the OC / FSS / CM client needs. This is the consequence of java 11 having become a modular system and this saves the number of bytes that needs to be copied to every FSS host. This is different from 2017.02 and earlier where the full JRE was normally installed. If a model adapter or external model to be run by the Forecasting Shell or Operator Client is also using this stripped down version of the JRE for its operation, it is possible that some of the java modules required are missing from the shipped jre and the adapter or model won't be able to run properly. It is the responsibility of the application managers / model configurators to ensure that their adapter and models requiring Java are already supplied with the correct java runtime modules. The Forecasting Shell Launcher startup script should not be contaminated by additional path variables, instead the models should contain their own embedded jre. See the General Adapter Module for more details . |
Forecasting Shell
Tomcat
MC / AI
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.
style | width: 500npx; height: 300px; overflow: auto |
---|
JRE version
Operator Client /
Forecasting Shell Server /
ConfigManager
Master-controller /
Tomcat
#67816
32 / 64 bit
32 / 64 bit (beta)
32 bit
Tomcat webcontainer for Admin Interface / PiService / Proxy
When 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)
JRE version
64 bit
(installation of 32 bit is not recommended)
Does not function with JRE 8. Note that JBoss4 requires a jdbc driver for storing temporary messages.
The JRE version with which this driver is compiled should be compatible with the JRE used for Jboss4.
Windows VC-Redistributables
The Delft-FEWS software contains Windows executables requiring a VC++ Redistributable Package being installed.
https://www.microsoft.com/en-us/download/details.aspx?id=14632
Security
Read more about the shared responsibility model. >>
title | Shared responsibility model |
---|