2. Prerequisites and recommendations


  1. Software requirements
    1. Java
  2. Hardware recommendations
    1. Material recommendations for assessing CMS Ametys
    2. Hardware recommendations for putting the CMS Ametys

Software requirements

Java

Ametys requires server-side installation of a Java Runtime Environment (JRE ) or Java Developers Kit (JDK) platform.

To install a version of Java supported by Ametys, please refer to the system tips page.

It is important to note that you need at least version 11 of Java for versions prior to 4.6, or version 17 for versions from 4.6 onwards, and that it must be 64-bit, regardless of the operating system used. On the other hand, non-Oracle JDKs are not supported.
If you are working on Mac OSX, a JVM is already installed and optimized for the environment, but it is not compatible with Ametys, so you will need to install an additional JRE in order to use CMS.

This page lists the platforms supported by Ametys 4.x.

 

Supported platform(s)

Supported version(s)

Notes

Java

Oracle JRE

11 prior to version 4.6

17 from version 4.6

64-bit version only

 OpenJDK versions are supported but not tested.

Example: https: //adoptopenjdk.net/releases.html?variant=openjdk11&jvmVariant=hotspot

Operating system

Microsoft windows

 

Ametys is a Java application and must run on operating systems with a compatible JDK or JRE...

Linux

 

File systems

 

 

NFS mounts are not supported due to Lucene prerequisites. For more information: IndexWriter

Virtualization

 

 

Ametys is used in most cases on virtualized servers. The virtual server must have the supported platforms specified in this guide, as well as the prerequisites below.

Application server

Apache Tomcat

9.0 and higher

Ametys must work with Tomcat 9 and +.

Ametys has been tested with one instance of Tomcat containing the back-office and front-office, or with one instance for each application. 

https://tomcat.apache.org/download-90.cgi

Database

MySQL

5.7 and + with the

JDBC Connector/J 5.7

For licensing reasons, the Oracle driver is not included in the Ametys downloads. It must be added manually to the WEB-INF/lib directory of the back-office application.

Oracle

 

PostgreSQL

 

Derby

 

Web browsers (back-office)

 

 

Please refer to the Supported browsers page.

 

Hardware recommendations

Material recommendations for assessing CMS Ametys

CMS Ametys will run smoothly on a recent desktop or laptop PC. The amount of memory (RAM - Java Heap Size) required depends on the number of contents, cache settings and site accesses. 512MB - 1GB is sufficient to evaluate CMS Ametys .

Hardware recommendations for putting the CMS Ametys

The following values are provided as examples, and are highly dependent on the volume of data handled, the plugins installed, the number of simultaneous contributors, etc.

  • Small institutional sites
    • 1~2 sites, 200~300 pages (99% cacheable), 300~400 contents, 1~2 charters (2 templates: home, page), 1~2 contributors producing 1~20 editions per day and 1~3 publications / day.
    • 50~200 visits / day
    • Java Heap Size: 2GB~4GB, 1 application server, 1 processor, 500~600MB of data (1 year of history) -> 10 to 20GB of disk space (7200rpm or +) + additional backup space.
  • Medium-sized corporate sites
    • 1~2 sites, 500~1000 pages (99% cacheable), 1000~1500 contents, 500 attached files (~1GB), 1~3 charters (6~8 templates), 5 to 20 contributors producing 10~50 editions / day and 5~15 publications / day
    • 500~1000 visits / day
    • 1 virtual server, 2 application servers, 4~8G RAM, 5~7GB data (2-year history) -> 80~100GB disk space + additional backup space.
    • Back-office: Java Heap Size: 6Go~10Go
    • Front-office: Java Heap Size: 512Mo~1Go
  • Medium-sized institutional sites++
    • 3~8 sites, 15000~20000 pages (95% cacheable), 10000~15000 contents, 500 MB of attached files, 3~8 charters (10~15 templates), 50 contributors producing numerous editions and publications per day
    • 8000~15000 visits / day with peaks of 30000~40000 visits / day
    • 2 Virtual servers
    • Back-office: 4 cpus, Java Heap Size: 6GB~10GB, 8~10GB of data (3 years of history) -> 100~150GB of disk space (SAS disk) + additional backup space.
    • Front-office: 2 cpus, Java Heap Size: 512Mo~1Go, 10Go file cache -> 60G disk space (SAS disk)
  • Larger institutional sites
    • 50 sites, 50000~70000 pages (95% cacheable), 50000~80000 contents, 2GB of attached files, 50 charters (130 templates), 300~500 contributors producing numerous editions and publications per day
    • 100000~150000 visits / day with peaks of 300000~400000 visits / day
    • 2 Virtual servers
    • Back-office: 4 cpus, Java Heap Size: 8Go~20Go, 100Go of data (3 years of history) -> 500Go of disk space (SSD or SAS disk) + additional backup space.
    • Front-office: 2 cpus, Java Heap Size: 512Mo~1Go, 10Go file cache -> 40Go disk space (SSD or SAS disk)

 

Back to top

Installation and operation manual