Setting up the pulse container
The next chapters will explain the directory structure of pulse and how to configure the pulse container.
This guide only deals with pulse internals whereas the quick guide also contains useful information regarding the setup of the environment
The main configuration – pulse.xml
The central configuration of the system is located in WEB-INF/conf/pulse.xml. It controls the setup of the pulse containers core components such as the internal mail queue, the virtual file system and the JPA2 and JAXB contexts.
Second level cache configuration
The second level cache of Hibernate is always activated for pulse installations. The
configurations are split into two files: 2ndLevelCache.xml and ehcache.xml
The workings of the second level cache are rather obvious and you can browse through the default settings to get a grip of what is cached in pulse. Obviously, adjusting these settings to match your website can greatly improve performance. The settings chosen as the default a quite generous and should be fine for most sites.
More container configurations
Configure logging and authentication settings, define available locales and control content-negotiation, set up the InputStream scanner chain to protect your website from malicious uploads and provide further central settings and configurations.
There are quite a few more settings for the pulse container. All their configurations are also located within WEB-INF/conf.