An action service template by default is bound to a particular action handler when the template is created. Binding a situation event to an action service template that is associated with a particular action handler allows the Adaptive Action Manager to invoke the appropriate action service.
When a situation event is detected, the Adaptive Action Manager invokes one or more action service templates according to the binding configuration. A situation event is a Common Base Event that represents a notification of a business situation. Situation events are business measures model elements that are defined in the Business Measures editor as outbound events. When the situation is triggered, the Observation Manager emits the situation event. For example, a situation event can be defined to trigger a situation when a certain Key Performance Indicator (KPI) exceeds a threshold. The situation event is then published into Common Event Infrastructure (CEI) and is routed to a WebSphere® activation specification.that is linked to a queue that the Adaptive Action Manager is listening to.
Situation events are defined into Adaptive Action Manager by a name and description. They are then bound to an action services template and thus a corresponding action handler through the Administration node on the administrative console of the WebSphere Application Server. This binding at runtime allows the Adaptive Action Manager components to use the action handler and template pairing to invoke the appropriate action service.
When the binding is set, the Adaptive Action Manager can parse the received situation event and select an appropriate action through the action catalog service. The selection is done by looking up the appropriate action in the action catalog, where information about bindings is stored. Based on this information, the Adaptive Action Manager creates entities called executable actions. An event-to-action determiner functionality determines what executable actions should be invoked for an incoming situation event, by matching it with the situation name stored in an extended data element in the Common Base Event.