Deployment modes

Three deployment modes are available.

Portlet deployment

This deployment is proposed for portal administrators, it deploys esup-helpdesk as a JSR-168 portlet, in order to execute it within a JSR-168 compliant portal (uPortal, Liferay, infoglue, ...).

If you are no portal administrator or you do not know what a portlet is, select a servlet or quick-start deployment.

Servlet deployment

This deployment is proposed for deployers who want to run the application into an existing servlet container (such as Tomcat).

If you do not know what a servlet is or if you do not have a J2EE runtime available, select a quick-start deployment.

Quick-start deployment

This deployment allows esup-helpdesk to run as a stand-alone application.

It can be used in order to test the application, but some deployers (especially those who d not have J2EE competences) run in production this way; quick-starts are full-featured applications.

Requirements

Installing esup-helpdesk needs a few requirements. 

• esup-helpdesk is provided as a zip file that contains all the sources. The sources must be compiled, which needs a Java Development Kit (a Java Runtime Environment is not enough).
• Installation commands and asynchroneous tasks are run using ant.
• esup-helpdesk is configured by default to connect to a MySql database; Hibernate allows the usage of any other database manager (see Configuration de la connexion à la base de données).

Unix requirements

Java 

Any Unix administrator knows how to install a JDK, embedded in most distributions. If not, download from http://java.sun.com/javase/downloads/index.jsp.

Ant

If ant is not available as a package (RPM or any), it can be downloaded from http://ant.apache.org/bindownload.cgi  and installed for instance in /usr/local/.

Java/ant environment variables

In order to simplify administration commands and asynchroneous tasks (see Scripts d'administration et tâches asynchrones), deployers may create in the folder /etc/profile.d the following java.sh script (adapt to your onfiguration) :

export JAVA_HOME=/usr/java/jdk1.6.0_05
export ANT_HOME=/usr/local/apache-ant-1.7.0
export PATH=$PATH:$JAVA_HOME/bin:$ANT_HOME/bin

Windows requirements

• 02 Download 
• 03 Uncompressing the sources
• 04 Propriétés de déploiement (build.properties)

The properties of the configuration file /build.properties tell the way the application is deployed.

Once set, the application itself must be configured by setting the properties of the configuration file /properties/config.properties, which defines the behaviour of the application at runtime (see 01 Configuration).