Not logged in | Login
ESB Console Glassfish ESB Event Management User Guide Configuring Alert Persistence
An Alert is a machine-to-person communication that is triggered when a specified condition occurs in a Project component. The condition might represent a problem that must be corrected, or the condition might be informational. An alert may also contain user-requested content such as a reminder (important), a notification (urgent), and ultimately an alert (important and urgent).
The alert persistence architecture includes an external database that you can use to persist alerts. The external database contains one alert table per domain.
By default, alerts are not persisted to the external database. This topic describes how to enable persistence.
Be sure to understand the behavior of the various persistence configurations.
You can use any of the following database types for the external database. The Derby database is included with Sun Java System Application Server. The other database types are not included.
If you want to use a database type other Derby, then you must perform additional configuration tasks. For example, you must use JavaTM DataBase Connectivity ("JDBCTM") software and the Java Naming and Directory InterfaceTM ("J.N.D.I.") API to set up access to the database.
For all database types, you must log in to the Configuration Agent and modify the alert notification fields.