Referential integrity check

HCL Workload Automation automatically performs referential checks to avoid lack of integrity in the object definitions in the database whenever you run commands that create, modify, or delete the definition of a referenced object. These are the checks performed by the product:

• Every time you use a command that creates a new object in the database, HCL Workload Automation checks that:
  • An object of the same type and with the same identifier does not already exist.
  • The objects referenced by this object already exist in the database.
• Every time you run a command that modifies an object definition in the database, HCL Workload Automation checks that:
  • The object definition to be modified exists in the database.
  • The objects referenced by this object exist in the database.
  • To avoid integrity inconsistencies, the object definition does not appear in the definition of an object belonging to the chain of his ancestors.
• Every time you run a command that deletes an object definition in the database, HCL Workload Automation checks that:
  • The object definition to be deleted exists in the database.
  • The object definition to be deleted is not referenced by other objects defined in the database.

Table 1 shows, for each object type, the identifiers that are used to uniquely identify the object in the database when creating or modifying object definitions:

In general, referential integrity prevents the deletion of objects when they are referenced by other objects in the database. However, in some cases where the deletion of an object (for example a workstation) implies only the update of a referencing object (for example a workstation class that includes it), the deletion might be allowed. Table 2 shows all cases when a referenced object can be deleted even if other objects reference it:

Table 3 describes how the product behaves when it is requested to delete an object referenced by another object with using a specific relationship: