Managing Properties

A property is a key value pair. You can set properties for entities, machines, groups, tasks, and workflows.

Property Hierarchy

Epsilon checks the following objects in this order: task, parent task (if any), workflow, machine, entity and group; and then, identifies the correct expansion of the key. The first key that is identified is picked up.

For example: “ORACLE_SID =sales-db”. The key @@ORACLE_SID@@ can be used in scripts, emails, and approval messages. Epsilon automatically expands @@ORACLE_SID@@ to sales-db (The “@@” marks ORACLE_SID as a key).

Properties reduce redundancy. For example: Instead of hardcoding the value of ORACLE_SID multiple times in a DB script, you can set a property called ORACLE_SID on each of the DB machines. When the script runs for a particular DB machine, every occurrence of @@ORACLE_SID@@ is expanded to the property value specified for that machine.