Using An Event Listener

For detailed information about configuration files, configuration layers and an explanation of the configuration-root placeholder used in the file paths in this section, see the CUE Content Store Server Administration Guide.

The event listeners executed by the Content Store are defined in a configuration file called configuration-root/ To enable the NewArticleNotifier listener, therefore, you must add a declaration to in one or more of your configuration layers. For example:


You must also create a properties file for the listener called, and save it in the location you have specified in the same configuration layer(s) - configuration-root/com/mycompany/ in this case. The file must at least contain $class and eventManager entries. In the particular case of the NewArticleNotifier example you will also need to set the email and emailSender properties. For example:


Finally, you must make sure that the email sender declared in configuration-root/com/mycompany/ is correctly configured. Create a configuration file called configuration-root/neo/io/services/ and configure it with appropriate settings. For example:


If you have trouble running your event listener, try checking the View Services page of the escenic-admin web application or the Content Store's log files.

Performance monitoring

If you want to use the Content Engine's HitCollector component to gather statistics about the performance of an event listener, then you can do so by adding one more line to its properties (i.e., configuration-root/com/mycompany/ in the case of this example):


You will then also need to create a configuration file for the collector you have declared (configuration-root/com/mycompany/ in this case):

denominator=events handled
description=Events handled by ''
failureDescription=failed events

The information gathered by the hit collector can be viewed on the escenic-admin web application's Performance Summary page. See here for information about escenic-admin.