create new tag
view all tags


Story summary Deployment Framework
Iteration AnA04Architecture
FEA AnA04S05DeployFramework
Story Lead  
Next Story  
Passed acceptance test No


The purpose of these tasks is to have a better installation of the application.

Servlet container installation

Currently the servlet container that it is being used in the Debian packages and in the deployment of the application is Tomcat 6.

In the development environment it is being used Jetty.

This task consist of studying if it is better to choose Jetty over Tomcat assessing the variables which may have an influence over the application. The most important one is performance (in number of requests/second it is able to serve and in terms of the latency of each request).

It is important to configure the following things:

  • Memory configuration for the Tomcat. Now in the installations there are out of memory errors after some time with the application running.
  • Configure the logs. Decide what log implementation is going to be used. Review how the logging is done in LibrePlan and configure properly the levels of logging. It is possible to suggest some change if needed.

Set on second-level hibernate cache

Currently in the application is the second level cache configured for some entities and relationship. However, it is set off.


Study if other Hibernate optimizations can be applied or are worth. For instance:

  • Use second level cache for some queries.
  • Configure the batch size.

Stress load tests for the application

The performance of the application has to variables that have to be taken into account:

  • The performance for single user in certain screens. These screens are the resource load screen and project planning screens (project details WBS, gantt window and advance allocation window). The resource load screen performance depends on the amount of projects in the application and the performance of the project planning screens depend on the size of the project. More size, less performance.
  • The performance for number of simultaneous users connected to the application.

It is wanted to analyse both variable and to have an idea of the hardware requirements that we have to say or recommend to do a LibrePlan deployment. Questions needed to ask are:

  • What is the number of simultaneous users who can connect to LibrePlan and use it fluenty in CRUD screens and medium size projects ?
  • What are the number of projects for which the resource load window has a reasonable load time ?
  • What is the size of a project for which a small of users connected to the server has a reosonable response time?

Backups, reloading tomcat, mechanism to uload data for the application

For real environments it is needed to configure several things like:

  • A way to do backups daily.
  • If the thing of having tomcat unsteady create a script which configures the tomcat restarting after certain periods of time.
  • It is needed to design and analyse to unload data before a date. In this case this data will be backed and unloaded from the running database of the application and the app would have to be configure to avoid plan anything in the periods that have been closed and unloaded. For future.

Debian packages, Rpm packages

This task consists of having better debian packages for the application in one side. On the other side, it is wanted to have rpm packages too.

User stories

Tasks in this story

Total Hours in this Story


Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r10 - 20 Aug 2012 - mrego
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback