Health Events; A.2 Health Events - Novell PLATESPIN ORCHESTRATE 2.0.2 - DEVELOPMENT CLIENT REFERENCE 08-28-2009 Reference

You could attach this policy directly to the Resource grid object or to a Resource group (more
practical).
Example 2: Define a user as unhealthy if he or she has no money in their account.
<policy>
<constraint type="health">
<ge fact="user.account.balance" value="0" />
</constraint>
</policy>
You could attach this policy directly to the User grid object, or to a User group (more practical).
You can aggregate (that is, group together with "and" or "or") health constraints by using
normal rules of policy aggregation.
By default, PlateSpin Control runs health constraints every 30 seconds. To alter this interval,
you must contact Novell Support.

A.2 Health Events

Each time the value of a health fact changes, an event is generated. This event can be subscribed to
by long-running Jobs (see
Orchestrate 2.0 Developer Guide and
Scheduler (see "The PlateSpin Orchestrate Job
Development Client Reference). The event names are different for each object type.They are listed in
the following table.
Event Names for Grid Objects
Table A-1
Object
User
Resource
Repository
VmHost
"Receiving Event Notifications in a Running
Reference) or the event can be used to trigger Jobs in the Job
Scheduler" in the
Event Name
USER_HEALTH
RESOURCE_HEALTH
REPOSITORY_HEALTH
VMHOST_HEALTH
Job" in the PlateSpin
PlateSpin Orchestrate 2.0
Grid Object Health Monitoring 135