here's an initial design doc -- http://support.rhq-project.org/display/RHQ/Design+-+Extending+Alert+Operations

questions i would like to see answered:

* are we shooting for single or multiple operations executed as the result of an alert
** if multiple, are they ordered or unordered
*** if ordered, do we support halt on failure
* what contextual information will we make available to operation as arguments - just static info (declared at the time the alert def is created), or dynamic info (the details found instead the alert itself)

also, it might be a good idea to do circularity checking, to make sure users don't inadvertently create an alert definition which executes an operation that happens to trigger an alert which executes an operation...that eventually makes it way back around to the original alert definition.

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2045

This will be the new alert-operations sender.

This can be achieved now, by script execution for a relative resource type. 

1.Browse through to the JBoss AS Server
2.Create a new alert definition with condition when JVM Free mem reaches critical value.
3.Click on Edit for the Alert Notification.
4.On the Alert notification page, click on Add New. Select the Alert sender
type as Resource Operations.
5.Select the resource selection mode as Relative Resource. 
6.Click Save
7.Select Start search from as "JBoss AS Server"
8.Click Save.
9.Select Then Filter by as "Script"
10.Provide the restart script name. (Ensure that this script is under ~/jbossas/bin directory.
11.Select operation name as "Execute Script"
12.Click Save.

The other way to do this is,
1.Browse through to the JBoss AS Server
2.Create a new alert definition with condition when JVM Free mem reaches
critical value.
3.Click on Edit for the Alert Notification.
4.On the Alert notification page, click on Add New. Select the Alert sender
type as Resource Operations.
5.Select the resource selection mode as This Resource
6.Select Operation name "Restart".
7.Click Save.

Mass-closure of verified bugs against JON.