Infrastructure requirements

Table of Content

• .stat core data store
• .stat data explorer
• .stat data lifecycle manager
• ESTAT NSIWS version compatibility

.Stat Core Data Store

Software requirements

• SQL Server
  • Minimum required SQL Server 2017 or above, all editions (including free SQL Express edition)
  • Recommended SQL Server 2019
• IIS Web server 7.5 or higher
• Microsoft .NET Core 3.1
• Microsoft SQL server management studio (Optional)
• Visual Studio 2019.-Used only for compiling the solutions when doing a source code installation.

Hardware requirements
Although the requirements could vary depending on the size of your data and the amount of users, for an installation of one .Stat Core Data Store (See sample topology), we suggest as a minimum the following requirements:

• Memory: 16 GB
• vCPUs: 8 CPU @ 2.4 GHz
• Disk: 250 GB

As a general rule, we suggest to limit the amount of memory allocated to the MSSQL server; A maximum of 75% of the total memory should be allocated to MSSQL. Based on the recommended minimum requirements, MSSQL server should use at minimum 5GB, and a maximum of 10GB.

.Stat Data Explorer

pre-requisites

• (reminder) an accessible (CORS-enabled, anonymous access enabled) SDMX v7.x endpoint
• nodejs 14.x and npm 6.14.x installed
• git installed (https://gitforwindows.org/); only to use git bash instead of cmd.exe for process variables
• solr installed and running on port 8983 (default) with a core created with solr create -c sdmx-facet-search from solr console
• redis downloaded and running on port 6379 (default)
• mongo downloaded and running on port 27017 (default)

The latest compatible versions of Solr, Redis and Mongo are mentioned and available in the docker compose setup file from which the release history can be retrieved.

notes:

• solr core name can be freely picked, default configuration targets sdmx-facet-search
• ports can be freely picked, if different than defaults they should be specified when launching services

Generally speaking, we would recommend 2Go allocated Solr to have safety nets, and 1Go for redis should be enough.

.Stat Data Lifecycle Manager

pre-requisites

• (reminder) an accessible (CORS-enabled, anonymous access enabled) SDMX v7.x endpoint
• nodejs 14.x and npm 6.14.x installed
• git installed (https://gitforwindows.org/); only to use git bash instead of cmd.exe for process variables
• keycloak v7.x (minimum) - v12.0.4 (latest tested and recommended) installed and running on port 8080 (default)
• postgres 12.x installed and running on port 5432 (default) or any other relational database usable by keycloak (for more information see here)

notes:

• keycloak realm name can be freely picked, default configuration targets oecd
• ports can be freely picked, if different than defaults they should be specified when launching services
• postgres is used as keycloak database in the qa and staging environments as well as in the default docker images, but it can be replaced with your own keycloak comptatible relational database

ESTAT NSIWS version compatibility

Table of version compatibility of the Eurostat NSI Web Service (nsiws.net public mirrored source-code) with the .Stat Suite .NET and JavaScript services, and the ISTAT Data and Meta Manager DMM - previously MDM - (public mirrored source-code):

Disclaimer on ISTAT DMM: This table is filled with information publicly available regarding the ISTAT DMM application (see source here). No test has taken place, especially for checking compatibility in the configurations of the nsiws in .Stat Suite and DMM. These additional tests to take place under the aegis of the SIS-CC DMM User Group (see corresponding kanban board - to be created soon - to follow issues or file requests).