Alerts engine architecture

 

This topic describes and illustrates the key components of the alerts feature set.

The IBM® WebSphere® Dashboard Framework feature set consists of several components that work together to provide model-based portlets with access to application alerts. The alerts engine is responsible for obtaining alert definitions from the persistence manager, which is responsible for storing alert definitions and user preferences related to alerts. The alerts engine also determines when the alert definitions need to be evaluated in response to requests from portlets and caches the state of evaluated alerts to improve performance for all portlets in an application. The alerts engine delegates alert evaluation to application-specific evaluators. These evaluators contain all of the business logic that defines when alerts are activated, their priority, and many other attributes.

The following diagram illustrates how these components relate to each other at a high level.

Alerts engine architecture

     

  • Alert state caching
    Use alert state caching to reduce the number of repetitious alert evaluations.

Parent topic: Working with alerts

Library | Support | Terms of use |

Last updated: Thursday, March 15, 2007 11:57am EST

This information center is powered by Eclipse technology. (http://www.eclipse.org)