Download pulse

Understanding pulse - A detailed configuration guide

A basic overview of all directories

The basic structure of pulse is organised as any standard Java webapp. It contains some public directories available via HTTP (css, lib-js, resources and the files in the base directory) and the configuration and library directories (META-INF and WEB-INF) which are not available via HTTP.

Setting up the pulse container

The container is the heart of every pulse installation. It controls the lifecycle of the whole web application and provides central services such as the global JAXB context, access to JPA persisted objects or the mail queue. Moreover it controls the user interaction with pulse as it processes all incoming requests, checks whether the current user has the required privileges for the requested action and then forwards the request to the bundles and components which actually provide and expose the end-user functionality.

Of bundles and components

Aside of the web frameworks core – the container – pulse is organised in bundles and components. Components provide new functionality for pulse in providing additional controllers, joblets (scheduled tasks) and persistent business objects. A bundle – as the name suggests – packages the functionality from one or more components as a part of your website, thus making it available to be used.