Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0


_LogEvent logEvent = new LogEvent();
logEvent.setAttribute("id", ""+bitstream.getID());
logEvent.setAttribute("ip", request.getRemoteAddr());
logEvent.setAttribute("referer", request.getHeader("referer"));
logEvent.setAttribute("language", request.getLocale().getLanguage());
StatsLogger.logEvent(logEvent); _

Wiki MarkupThe main points involved in the logging-process are the components that represent and manage the items/collections/communities. The Statistics application is based on the standard DSpace Web UI, so it uses the Servlets that load data to collect statistics informations. Of course the architecture can change (with \ [ Manakin\|\] for example). In that case there will be the need to identify the points of logging in the new architecture.

JMS event system

In DSpace there is already something like the system I have proposed ( Anyway for the development of this application it isn't mandatory to use this implementation, but some ideas are the same.



Wiki MarkupThis list is based on the 1.4.2 version of DSpace and \ [ Manakin\|\] or other UI aren't considered. This statistics application can be easily used also in different version of DSpace, simply choosing classes/points that have to post log events.

Core layer

This layer is the point where the informations queued in the JMS queue will be written in the database. Every type of LogEvent have a different DAO class that manages it.


In the released dspace.cfg there already configured some reports (List and Graph)unmigrated-wiki-markup

There are others configuration file modified for Statistics Application, like \[
[etc/dspace-web.xml|] \] (with the definition of new Servlets and mappings) \[[jsp/META-INF/context.xml|
[jsp/META-INF/context.xml] \] (with the definition of JMS resources)

2) Download and install the following dependencies: