The administrative functions of the Adaptive Action Manager are
handled through the Adaptive Action Manager node
under WebSphere® Business Monitor on the administrative
console of WebSphere Application
Server.
The Adaptive Action Manager is one of the
key components in WebSphere Business Monitor.
Adaptive is the characteristic that allows the Adaptive Action Manager to
modify its behavior in response to changes in the target business processes
and the character of the environmental stimulus. The Adaptive Action Manager receives
situation events, which are notifications of business situations, emitted
by the Monitor Server or other applications. It then selects the actions to
take, based on predefined rules and policies set by the user.
Finally, the Adaptive Action Manager invokes
a selected action or a set of actions.
The Adaptive Action Manager helps you to
perform the following:
- Add or modify static configuration data to a table in the action
catalog database, which is the configuration table that contains the static
information for setting up the SMTP Server and the LDAP Server. When
you set up or update the general configuration properties and the LDAP Server configuration properties,
the information is stored and updated in the action catalog table.
Important: You must restart the Adaptive Action Manager from
the WebSphere Application
Server administrative
console after you update any values in the general configuration properties
for your values to take effect.
- Add or modify template definitions When you create and modify templates,
such as notification templates and Web Services templates, the information
is stored and updated in the action catalog database. A template is information
that is used by a particular action service (such as e-mail). When you create
a template, you also bind a particular action service to the template.
- Bind situation events by linking the situation events with action
services (target actions that you intend to invoke, for example, Web service).
You do this by binding a situation-event name with a particular template.
Because a template is already bound to a particular action service, this binds
an event to an action service. Multiple action services (templates) can be
bound to a single situation-event name.