Configuration

• edit the server ServletProperties file (it is in serveur/WEB-INF/classes/paellos)
• edit SITENAME/constantes.jsp in the UTF-8 character encoding. The site name must match the web application name, and therefore the folder name (it will be called SITENAME from now on).
• make sure the configuration files are not readable by all (but Tomcat must be able to read them)
• If necessary, to let Tomcat manage the "SITENAME" application, add in Tomcat's conf/server.xml the informations in exemple_pour_tomcat_6_de_server.xml (there is for instance a connector to redirect queries from Apache). Initially, it is better to try without changing this file (it's edition is no longer necessary since Tomcat 6).
• replace the logo.png file by your training's logo
• make sure Tomcat's connector uses URIEncoding="UTF-8" in conf/server.xml (otherwise search queries will not work with accented characters).

If a security manager is enabled (this is for instance the case by default with Ubuntu 9), the web application has to be authorized to do local connections to mySQL, as well as reading the website files, use the indexation files for search queries on the website, and use certain classes : create a file named tomcat6/conf/policy.d/paellos.policy, with (by changing "SITENAME", "serveur.smtp", "/var/www" and ".../index_lucene" if necessary) :

grant codeBase "file:${catalina.base}/webapps/SITENAME/-" {
  permission java.net.SocketPermission "localhost:3306", "connect,resolve"; // access to the SQL database
  permission java.net.SocketPermission "smtp.exemple.fr:25", "connect,resolve"; // sending emails
  permission java.io.FilePermission "/var/www/webjaxe/-", "read"; // reading WebJaxe files
  permission java.io.FilePermission "/var/www/public", "read"; // generating the public website
  permission java.io.FilePermission "/var/www/public/-", "read,write,delete"; // generating the public website
  permission java.io.FilePermission "${catalina.base}/webapps/SITENAME/WEB-INF/sites", "read"; // training websites
  permission java.io.FilePermission "${catalina.base}/webapps/SITENAME/WEB-INF/sites/-", "read,write,delete"; // training websites
  permission java.io.FilePermission "${catalina.base}/webapps/SITENAME/WEB-INF/index_lucene/-", "read,write,delete"; // indexation files
  permission java.lang.RuntimePermission "accessClassInPackage.org.apache.jasper.compiler"; // jsp compilation
  permission java.lang.RuntimePermission "accessClassInPackage.org.apache.jasper.compiler.*"; // jsp compilation
};

• If Apache is used as the main web server, it is possible to use it for all queries with specific paths, and to redirect the queries to Tomcat. This can be done with Apache's mod_jk module. It might be necessary to install mod_jk if it is not already installed (on Ubuntu, it can also be necessary to install the mods include, rewrite and suexec for Apache, and to change the owner of the webapps folder). For instance, here is how mod_jk can be configured in httpd.conf :

  # warning: with Apache 2, do not use AddModule, and replaced httpd by apache2 in the paths
  AddModule mod_jk.c
  <IfModule mod_jk.c>
    JKLogFile /var/log/httpd/mod_jk.log
    JKWorkersFile /etc/httpd/workers.properties
    JKMount /SITENAME/* PAELLOS
  </IfModule>
  

  and workers.properties should be added next to it (if it already exists, it should be combined).

  In each Virtualhost (typically the files in sites-enabled), the following code must be added :

  <IfModule mod_jk.c>
    JkMountCopy On
  </IfModule>
  

  On Tomcat side, a matching connector is required to listen to incoming queries, as described in the exemple_pour_tomcat_6_de_server.xml file included in PAELLOS

• possibly change the site home page, index.html (located in SITENAME/site/) (for instance to disable the links to the forum and the chat room if they are not used).