Server installation

Table of Content


Icons used in this guide

Some icons are used to alert you about additional informations.

"Important", showed by an exclamation mark, alerts you about important informations about the administration area of Ametys Runtime.

"Remark", showed by an i, alerts you about additional informations, for example it gives you others methods to reach your goal.

"Tips", showed by a tick, alerts you about tips to work with more efficiency.

Targeted public

This manual was written for persons who wants to perform an installation of an application based on CMS to test the Ametys v3.


If you need some help installing CMS V3, do not hesitate to ask mailing-lists or, and to add your comments and informations to this documentation.


On the site you can download the packaged version ( to deploy to a server.


Take always a note where the software binaries are installed on your system, you will need them to configure some softwares.

The technical requirements are ;

We recommend you to use the standard configuration : a Linux distribution with the Sun Java 6 and Tomcat 6.0.

In order to avoid many Java installations and servlets engines, It is possible to use a more recent version.
Warning if you decide to do that, it is possible to have some incompatibilities: in this case, it is important to specify to the support of the application which version you are using.


The packaged version comes with an integrated database Derby, which allows to start working with the application, but is not recommended for production.

Ametys also natively supports MySQL, Oracle and PostgreSQL.

Since Ametys 3.1, You will find the sql scripts in the WEB-INF/script directory.


Unzip the archive. The directory cms is the backoffice application .

CMS installation

Check the Tomcat of the cms is stopped.

Move the directory cms to the application directory of the tomcat server (webapps).

Restart the tomcat server.

CMS settings

Launch your browser (Firefox 3.5+ ) and enter the url http://serveur:port/cms/ (http://localhost:8080/cms/).

You may get a special screen if the application is not fully configured, which tells you that the application can't be loaded and prompts to update the config.

Then click to configure the application.

In Database, specify :
- the driver
- the url
- the user
- and the password of the database

In Management of contents, specify :
- the path to the repository, in default version it is in the application directory,
but it is possible to update it.

To find the definition of the others parameters, go to page Administration.

Click to "Save and restart".

You can now access to the cms : http://serveur:port/cms.

You must be authenticated. Demo version is downloaded with these users in the database:

  1. User with contributor rights on all pages contrib/contrib
  2. User with contributor and publication rights on all pages manager/manager
  3. User with extended contribution and webmastering rights webmaster/webmaster
  4. User with extended rights and debug features admin/admin

For a public application, it is recommended to set-up a static web server like Apache HTTPD ( behind the end-user and the servlet engine. This one is used to redirect the requests to your servlets engine (with mod_jk or mod_proxy) and allows you to access to some others functionalities:
- Limit the access to the administrator area to some IPs,
- Load balancing,
- Deliver static files (pictures, javascript...) directly.

For overall performance improvements, it is also recommended to enable HTTP gzip compression on both the tomcat server and the apache HTTPD front-office.
To enable gzip compression on the tomcat server, edit the <tomcat directory>/conf/server.xml file, and add the following lines in the HTTP Connector configuration:

<Connector port=...

To enable gzip compression on the apache HTTPD server, add the following line to the VirtualHost declaration:

AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript

Back to top