Receiving alerts in OpenESB

  Introduction: 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). An alert notification is triggered when a specified condition occurs in a component or a service unit. The condition might represent a problem that must be corrected, or the condition might be informational. Alert Notification severities could be one of the following: Fatal Critical Major Minor Warning Info Alerting in Open ESB The Alert Management is embedded in Glassfish ESB’s JBI Runtime. The alerts can be generated from various sources – BPEL, EJB, a POJO, etc. The project developer also can raise alerts at certain events when it occurs in the composite application / BPEL/Java code. These alerts can then be managed and monitored from a Alert Client. UseCases The below are the usecases where Alert Management is useful: Capture Alert Event Notifications from Composite Applications, Java EE components, the JBI runtime, JBI Component Containers, and JMS Servers Allow the Alert Client to enable/disable the persistence of events generated by the Composite application. Allow the client to define a policy that will remove alerts from the persistence to prevent persistence from degrading system performance. An Alert removal policy can define the alert max age, the alert level to discard and the total number of alerts allowed to be persisted. Allow the client to enable/disable the policy mentioned above Allow the client...