Page Operations
Browse Spacee-Alerts listener
The e-Alerts listener uses the Hippo update notifier to receive events of updated/published documents.
Follow the steps of the general setup for Hippo Community Apps.
Required settings
Add the following property to the build.properties file to enable the listener service:
# Notifier listener enabled
hca.notifier.listener.enabled=true
# Files path
hca.notifier.repository.filespath=/files/${maven.cocoon.repository.name}.www
 |
In most cases you should set the filespath to the live repository, to make sure that only published documents are taken into account. |
Additional properties are required for the e-Alerts Manager. By default they are provided with the default values specified for the CMS properties, like this:
# Notifier listener
hca.notifier.jms.connection.factory=${jms.connection.factory}
hca.notifier.jms.jndi.provider=${jms.jndi.provider}
hca.notifier.jms.jndi.initial.factory=${jms.jndi.initial.factory}
hca.notifier.jms.topic=${jms.topic}
hca.notifier.jms.username=admin
hca.notifier.jms.password=openjms
hca.notifier.jms.reconnect.delay=1000
# Notifier listener webdav config
hca.notifier.repository.username=${maven.cocoon.repository.systemcredentials.username}
hca.notifier.repository.password=${maven.cocoon.repository.systemcredentials.password}
hca.notifier.repository.protocol=http
hca.notifier.repository.host=${maven.cocoon.repository.host}
hca.notifier.repository.port=${maven.cocoon.repository.port}
hca.notifier.repository.realm=${maven.cocoon.repository.authenticationrealm}
hca.notifier.repository.namespace=${maven.cocoon.repository.name}
You can override these properties in the build.properties file.
Specify paths to listen to
In the CMS you can specify the paths to listen to for each e-Alert. Only documents which reside under the specified paths are processed by the listener.