Install instructions eHour.war on Linux with MySQL or PostgreSQL
eHour requires a Java JDK, the Apache Tomcat servlet container and either a MySQL or PostgreSQL database to be installed. Although this may seem as a lot, installation is easy.
When you are upgrading an existing installation of eHour, please see the upgrade instructions; do not follow the installation instructions again.
Java 1.5+
eHour is developed using Java technology so you'll need a Java runtime environment (version 1.5 or newer), before anything happens.
Download and install the latest version from Sun's site.
Install instructions for Tomcat can be found on their site.
Database setup
Click a database to review the setup guide and any known issues.
MySQL
Install MySQL
To install MySQL use your Linux's package system or install it manually by downloading it from MySQL's site and follow their installation instructions.
Create database
With MySQL installed and started create a MySQL database named eHour by executing the following command and replacing user with a database user that has enough priviliges to create a new database:
mysqladmin create ehour -u user -p
Install eHour database
With the ehour database created the next step is to create the datamodel and fill them with some default data. In the eHour's sql/mysql/install directory there's a fresh.mysql.sql script which contains the datamodel and default data.
Execute it by running the following command (don't forget to replace the user):
Version 5.1.5 of the MySQL JDBC connector contains a bug that prevents eHour from working correctly. eHour was tested with version 5.0.8.
Unpack the downloaded archive and copy the extracted mysql-connector-5.x.x-bin.jar file to Tomcat's common/lib (Tomcat 5) directory or the lib directory on Tomcat 6.
PostgreSQL
Install PostgreSQL
To install PostgreSQL use your Linux's package system or install it manually by downloading it from PostgreSQL's site and follow their installation instructions.
Create database
With PostgreSQL installed and started create a database named eHour by executing the following command and replacing user with a database user that has enough priviliges to create a new database:
createdb ehour
Install eHour database
With the ehour database created the next step is to create the datamodel and fill them with some default data. In the eHour's sql/postgresql/install directory there's a fresh.postgresql.sql script which contains the datamodel and default data.
Execute it by running the following command (don't forget to replace the user):
Copy the downloaded jar file to Tomcat's common/lib (Tomcat 5) directory or the lib directory on Tomcat 6.
Database connection
Before you deploy eHour in Tomcat you have to configure the database connection, make sure Tomcat isn't running.
In the conf/tomcat directory of the eHour distribution you'll find an ehour_mysql.xml/ehour_postgresql.xml config file.
Edit this file in your favourite text-editor and replace the following fields:
@ehour.db.username
the database username
@ehour.db.password
the database password
@ehour.db.hostname
the hostname/IP address of your database server
@ehour.db.name
the eHour database name
When you're done editing save this file as ehour.xml in the conf/Catalina/localhost directory in your Tomcat install directory. When running Tomcat 6 create this directory first.
Don't drop the ehour war in Tomcat's webapp directory as you would do with other applications
Make sure you rename the file to ehour.xml
In the install directory of Tomcat create a directory named deploy
From the eHour distribution copy the ehour-0.8.4.war into this directory.
Start it all up !
Make sure you have started your database first.
Start Tomcat by running startup.sh in the bin directory of the Tomcat installation directory. After a couple of seconds Tomcat and eHour will be initialized and you can access the application at [http://localhost:8080/ehour/].
Are you sure that the 0.9 code is deployable. We took the latest code base from ...
Are you sure that the 0.9 code is deployable. We took the latest code base from the trunk and followed the steps here only to find that there is a dependency on <context:property-placeholder location="file:///$
Unknown macro: {ehour.home}
/conf/ehour.properties" />
there is no place where ehour.home seems to be defined.
Further the ehour.properties that is bundled with the wicketweb project does not seem to have ehour.database etc defined and the installation fails with
'getHibernateTemplate' defined in class path resource [net/rrm/ehour/persistence/appconfig/HibernateConfiguration.class]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public org.springframework.orm.hibernate3.HibernateTemplate net.rrm.ehour.persistence.appconfig.HibernateConfiguration.getHibernateTemplate() throws java.lang.Exception] threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in class path resource [net/rrm/ehour/persistence/appconfig/HibernateConfiguration.class]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public org.hibernate.SessionFactory net.rrm.ehour.persistence.appconfig.HibernateConfiguration.getSessionFactory() throws java.lang.Exception] threw exception; nested exception is java.lang.IllegalArgumentException: Failed to load database config from: hibernate_$
Unknown macro: {ehour.database}
.properties. Did you spell the database name in ehour.properties right?
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:286)
Comments (4)
Apr 26
Anonymous says:
I don't operate Tomcat but I can install web applications. In other words, "dro...I don't operate Tomcat but I can install web applications.
In other words, "drop the .war into webapps" is all I can do.
This is no accident, it's how Tomcat was designed to be used.
How hard is it for you guys to make it work?
Jun 22
Anonymous says:
Are you sure that the 0.9 code is deployable. We took the latest code base from ...Are you sure that the 0.9 code is deployable. We took the latest code base from the trunk and followed the steps here only to find that there is a dependency on <context:property-placeholder location="file:///$
/conf/ehour.properties" />
there is no place where ehour.home seems to be defined.
Further the ehour.properties that is bundled with the wicketweb project does not seem to have ehour.database etc defined and the installation fails with
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:286)
are we missing something for 0.9 ?
Jul 04
Thies Edeling says:
0.9 is not yet deployable. please use the forum (ehour.nl/forum) for more q's&nb...0.9 is not yet deployable. please use the forum (ehour.nl/forum) for more q's
Jul 21
Anonymous says:
HI ,, i would like to get clarified some features. 1.Will users get a email ale...HI ,, i would like to get clarified some features.
1.Will users get a email alert when the assignment is assigned. i know if the time allotted exceeds project manager will get the alert
2.Main thing is how to configure google apps mail in mailserver
a. Mails configured with our own mail server hosted does not send mails to other domains
b. not able to configure google apps (pls msg me the configuration)SMTP port number , smtp server address. etc..(IMP)
c. is there any ways to integrate this with LDAP (IMP)
d. can we implement this with subversion??
Add Comment