Policies
Policies are visual representations
of your data center operation procedures. Policies are built by
dragging and dropping objects and connecting them with links. When
triggered, each object performs an action. Once an object has
completed it will trigger any objects that are linked to it.
Objects
Each object performs a specific
action when it is executed by the Action Server. To use an object,
drag-and-drop it to the Policy, configure its properties, and link
it to the object that will trigger it. For example, the Send Email
object is used to send email through an SMTP server. To use the
Send Email object you must configure the recipients, subject,
message body, and the SMTP server.
All objects produce data that is
published to the Databus. This data will automatically be made
available to objects further down the flow without any need to
create symbolic variables for storage. To learn more about the
databus, see “CROSS_REF”
Monitors
Some objects are triggered by
external applications and cannot be triggered by another object.
These objects are called Monitors. Monitors are used at the
beginning of Policies to create start conditions. For example, the
Monitor Folder object will wait for the files within a specified
folder to change. When a file changes the Monitor Folder object
will trigger the next object in the Policy.
Policies can only contain one
starting point. See our best-practices guide for more
information.
Links
Links are used to connect objects
and create the order in which they are triggered. Links can be
configured with Link Conditions that will filter data from the
previous object in the Policy. The filters can test any data
published to the Databus. With Link Conditions, you can build
automatic decision making in your Policies.