The Policy Object; Computed Fact Objects; Event Objects; Metrics - Novell PLATESPIN ORCHESTRATE 2.0.2 - DEVELOPMENT CLIENT REFERENCE 08-28-2009 Reference

Development client reference
Table of Contents

Advertisement

Section 5.8.3, "Event Objects," on page 125
Section 5.8.4, "Metrics," on page 125

5.8.1 The Policy Object

XML is used to define PlateSpin Orchestrate policies. A policy can be deployed to the server and
associated with any grid object. The
contain constraints and fact definitions for grid objects.
You can edit a policy by clicking a policy in the Explorer tree view, making your changes, and then
clicking the Save icon. The Where Used tab of the Policy Editor lists the jobs where the selected
policy associated.
Policy Constraints
A policy can define a collection of constraints which are applied appropriately based on context. For
example, a resource constraint can limit the selection of a resource to a subset based on resource
group membership, or any number of other fact-based evaluations.
You can use
/opt/novell/zenworks/zos/server/examples/customNode.policy
the PlateSpin Orchestrate Server as an example policy file with constraints.
Policy Facts
The XML fact element defines a fact to be stored in the grid object's fact namespace. The name, type
and value of the fact are specified as attributes. For list or array fact types, the element tag defines
list or array members. For dictionary fact types, the
You can see an example policy with an XML representation for all the fact types on the PlateSpin
Orchestrate Server at
/opt/novell/zenworks/zos/server/examples/allTypes.policy

5.8.2 Computed Fact Objects

Computed facts are used when you want to run JDL to generate the value for a fact. Although
computed facts are not jobs, they use the same JDL syntax. You can see examples of computed facts
on the PlateSpin Orchestrate Server at
and
activejobs.cfact

5.8.3 Event Objects

An Event object in the Explorer tree represents a user-described set of rules which can be associated
with a schedule trigger or handled by long-running jobs written to respond to events.
For more information about using events, see
PlateSpin Orchestrate 2.0 Developer Guide and
guide, and
Section A.2, "Health Events," on page 135

5.8.4 Metrics

Although the Metrics object is visible in the Explorer panel, configuration for this object is not
available in this release.
element is the root element for policies. Policies
policy
/opt/novell/zenworks/zos/server/examples/
/opt/novell/zenworks/zos/server/examples/repostiory.cfact
"Using an Event Notification in a
Reference,
tag defines dictionary members.
dict
"Event Triggers" on page 32
of this guide.
located on
.
.
Job" in the
of this
The Explorer Tree 125

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the PLATESPIN ORCHESTRATE 2.0.2 - DEVELOPMENT CLIENT REFERENCE 08-28-2009 and is the answer not in the manual?

Questions and answers

This manual is also suitable for:

Platespin orchestrate 2.0.2

Table of Contents