XML is used to define Orchestration Server policies. A policy can be deployed to the server and associated with any grid object. The policy element is the root element for policies. Policies contain constraints and fact definitions for grid objects.
You can edit a policy by clicking its icon in the Explorer tree view, making your changes, then clicking the save icon. The tab of the Policy Editor lists the jobs where the selected policy is associated.
A policy can define a collection of constraints that 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 on the Orchestration Server as an example policy file with constraints.
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 dict tag defines dictionary members.
You can see an example policy with an XML representation for all the fact types on the Orchestration Server at /opt/novell/zenworks/zos/server/examples/allTypes.policy.