System Requirements

Carmenta Server Core 2019.1

Jump to Carmenta Server 4.6 – for Windows Server

Carmenta Server Core for Windows

Development Environment

Operating Systems:

  • Windows 10, version 1809 or later

Software requirements:

  • .NET Core 2.2
  • Docker Desktop Community or Enterprise

Language requirements:

  • .NET Core API: .NET Core 2.0 or later
  • C++ API: MSVC 10 (2010) or later

Deployment Environment

Operating Systems:

  • Windows Server 2019 (Process isolation)
  • Windows Server, version 1903 and 1909 (Hyper-V isolation)

Cloud environments:

  • Amazon Elastic Container Service (ECS)
  • Azure Container Instances (ACI)

Carmenta Server Core for Linux

Development Environment

Operating Systems:

  • CentOS 7.5
  • Red Hat Enterprise Linux 6 or later
  • Ubuntu 18.04 LTS or later

Software requirements:

  • .NET Core 2.2
  • Docker Desktop Community or Enterprise

Language requirements:

  • .NET Core API: .NET Core 2.0 or later
  • C++ API: GCC 4.3.4 or later

Deployment Environment

Operating Systems:

  • CentOS 7.5
  • Ubuntu 18.04 LTS or later

Cloud environments:

  • Amazon Elastic Container Service (ECS)
  • Azure Container Instances (ACI)
  • Azure Kubernetes Service (AKS)
  • Azure Web App for Containers

Hardware recommendations

Generally speaking, the hardware requirements for Carmenta Server Core are flexible and largely determined by the number of map services being published and their characteristics (type of geodata, rendering and caching requirements etc.).

Due to its architecture with internal scaling up of multiple map server instances if possible, Carmenta Server Core will make use of all hardware that is allocated to it, to ensure maximum performance.

The minimum recommended hardware configuration for a Carmenta Server Core container is:

  • Number of CPUs: 2
    Note: 3 CPUs or more will allow multiple map server instances in the container (normally the number of map server instances will equal the number of CPUs minus one)
  • RAM: 2 GB
    Note: More RAM will allow more caching of geodata, and a larger map tile memory cache (if applicable). Some map services may require a certain amount of RAM to be loaded and published.
  • Disk space: Depends on the size of the geodata and the size of a map tile disk cache (if applicable). Note: The disk space may be allocated internally in the container, or on a mounted external volume.

 

 

 

Carmenta server 4.6

Development environment

Operating Systems:

  • Windows 7
  • Windows 8 & 8.1
  • Windows 10

Note: Only 64-bit Operating Systems are supported

Software requirements:

  • IIS 7.0 or later
  • .NET Framework 4.7.2 or later
  • .NET Core 2.0 or later
  • Java Runtime 7 or later

Language requirements:

  • .NET Core API: .NET Core 2.0 or later
  • Java API: Java 7 or later
  • C++ API: MSVC 10 (2010) or later

Hardware recommendations:

  • CPU: Minimum dual-core CPU (quad-core CPU preferred)
  • RAM: Minimum 4 GB RAM
  • Disk space: At least 10 GB free disk space

Deployment environment

Operating Systems:

  • Windows Server 2008 and 2008 R2
  • Windows Server 2012 and 2012 R2
  • Windows Server 2016
  • Windows Server 2019
  • Note: Only 64-bit Operating Systems are supported

Software requirements:

  • IIS 7.0 or later
  • .NET Framework 4.7.2 or later
  • .NET Core 2.0 or later

Hardware recommendations:

  • CPU: At least one quad-core Xeon-class CPU, or other server-grade CPU. More CPUs and/or more CPU cores per CPU will result in more map server instances running in parallel.
  • RAM: At least 4 GB or more. More RAM will allow more caching of geodata in map server instances, and a larger map tile memory cache.
  • Disk space: Depends on the size of the geodata and the size of a map tile disk cache. Typically at least 100 GB free disk space is needed. Fast disks such as hardware RAID or similar will increase the server performance significantly

Note: Due to its architecture with internal scaling by running multiple map server instances if possible, Carmenta Server will make use of available hardware in an efficient and optimal way, to ensure maximum performance.

On multi-core CPUs and/or multi-CPU systems, the CPU cores are typically used as follows:

  • One CPU core is used for the IIS working process, Tile Store and other Windows processes
  • The remaining CPU cores will allow multiple map server instances to run (typically the number of map server instances will equal the number of CPU cores minus one)