alert

Component-Based Message Alerting

On AAE/AEX, the alert store is JMS queue. Each alert is actually a JMS text message, which text content is encoded to JSON format (alert payload) and instrumented with custom JMS header fields for error label, component, rule ID and scenario ID.

• Alert Configuration - Create Alert Rules in Integration Directory/NWA linking it with Alert Consumers
• Alert Creation - Local Message Processing > Alert Events > Alert Engine > Alert Store
• Alert Consumption - Alert Consumer can be Solman, Email service or any 3rd party consumer
• Enhancing CBMA Alerts with UDS Attributes
• Alerting for stuck messages on the Adapter Engine ***(using z message driven bean)

Email Consumer - Java mail client - AlertConsumerJobV2

• Michals-pi-tips-component-based-message-alerting
• Generate Formatted or structured EMAIL using CBMA - 2088606 - support custom email content

JMS Consumer - BC_JMSQUEUE

jmsqueues/alertingVP/jms/queue/xi/monitoring/alert/<alert consumer>

jmsfactory/alertingVP/AlertingConsumerConnectionFactory

• PI Alerting on AAE/AEX - JMS Hermes - View Alerts generated in CBMA
• Customize Alerts Using Job (using z message driven bean)

WS Consumer - AlertRetrieveAPI_V2 - RetrieveSingleAlerts - http://host:port/AlertRetrieveAPI_Service/AlertRetrieveAPIImplBean?wsdl

• Michal's PI tips: Component based message alerting API