Requirements
In this section you can have a glance of the minimum and recommended versions of the tools needed to build/debug/install MapStore
War Installation
You can download a java web container like Apache Tomcat from and Java JRE
| Tool | Link | Minimum | Recommended | Maximum |
|---|---|---|---|---|
| Java | link | 171 | 17 | 21 |
| Tomcat | link | 10.12 | 11 | 11 |
Debug / Build
These tools needs to be installed (other than Java in versions above above):
| Tool | Link | Minimum | Recommended | Maximum |
|---|---|---|---|---|
| npm | link | 8 | 10 | |
| NodeJS | link | 22 | 24 | 263 |
| Java (JDK) | link | 17 | 17 | 21 |
| Maven | link | 3.1.0 | 3.6 | |
| python4 | link | 2.7.9 | 3.7 |
Notes
Here some notes about some requirements and reasons for max version indicated, for future improvements and maintenance :
- 1 Java 17 is the minimum version required since the upgrade to Spring 7 (see the migration guidelines). Previous versions of MapStore could run on Java 8/11.
- 2 Since the upgrade to Spring 7 / Jakarta EE 10, MapStore requires a servlet container supporting the Jakarta Servlet API 6.0 (
jakarta.*namespace): Tomcat 10.1 is the minimum version, Tomcat 11 is the recommended one and the one shipped with the binary distribution. Tomcat 9 or older (based on thejavax.*namespace) is not supported anymore. - 3 Latest version tested.
- 4 Python is only needed for building documentation.
Running in Production
System requirements
| Resource | Minimum | Recommended |
|---|---|---|
| Processor | 2 Core | 2 Core |
| Memory | 2 GB | 4 GB |
Database
In production a PostgreSQL database is recommended:
| Tool | Link | Minimum | Recommended | Maximum |
|---|---|---|---|---|
| Postgres | link | 13 | 17 | 18 |
Tip
If you need to configure the database connection (and other settings) for a production deployment, it is recommended to use the externalized configuration (-Ddatadir.location=) instead of setting only the database override file. This allows you to manage all MapStore configuration files (database, proxy, JSON configs, etc.) in a single external directory that persists across updates.