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.

• If persistence is disabled, then alerts are generated and sent to any monitoring instances that are currently running. The monitoring instances can include no more than one instance of Enterprise Manager, as well as any number of clients that use the Alert Management API. For detailed information about the Alert Management API, see Java CAPS Management and Monitoring APIs.
• If persistence is enabled and journaling is disabled, then the alerts are stored temporarily in the external database. The system makes a best effort to send the alerts to all monitoring instances. When the reliable client indicates that it received an alert, the alert is deleted from the database.
  • There can be only one reliable client at a time. The most recent client to request reliable delivery becomes the reliable client.
  • Enterprise Manager requests reliable delivery when you start the server. Clients that use the Alert Management API can request reliable delivery when they subscribe to the alert notification service.
  • Note - If the reliable client is shut down, then there is no reliable client until the next request for reliable delivery is made.
• If persistence and journaling are both enabled, then alerts are stored permanently in the external database. When a client consumes an alert, the alert is not deleted from the database.

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.

• DB2
• Derby
• Oracle
• PointBase
• Sybase

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.

• Back to Glassfish ESB Event Management User Guide
• Back to ESBConsoleAlerting
• Back to ESBConsoleDetails
• Back to ESBConsoleGettingStarted

Quick Navigation Links

• Navigate to About
• Navigate to Getting Started
• Navigate to Community
• Navigate to Screencasts and Demos
• Navigate to Technical Information
• Navigate to How Tos
• Navigate to Project Details
• Navigate to Source Code
• Navigate to Frequently Asked Questions(FAQ)

This page (revision-5) was last changed on 25-Nov-09 06:03 AM, -0800 by Gopalan Suresh Raj.
This page was created on 25-Nov-09 05:47 AM, -0800 by Gopalan Suresh Raj.

More info...