DTD <objects> and <object> elements
The <objects> tag holds the definition of the objects to be acted on, and so contains a number of <object> tags. Each object tag represents a single asset in the OpsCenter Analytics configuration.
Each object has the following properties that define it in the XML file:
id | The ID of the object. This value is not the actual object ID but a unique value that identifies the object in the working XML. |
name | The actual name of the object. |
action | The action to be taken for the object. |
add | Add the object. |
delete | Delete the object. Note that for an object, delete operation does not delete the object from the OpsCenter database. For a view or node, the delete operation deletes the view or node but does not delete the related object from the OpsCenter database. |
update | Update the properties of the object. |
declare | No action. You may need this object in XML at a later stage. In some cases, another object already present in the OpsCenter Analytics configuration may be required to take action using this object (for example, setting it as a master object for a newly defined object). To be able to do that, the object must first be "declared" in the XML. |
type | The type of the object. Currently, an object can be one of the following types: |
GENERIC | A generic object such as a hierarchical node in the View tree. |
FILE_SYSTEM | A file system object. |
MEDIA_CLIENT | Host that acts as both media server and client. |
MEDIA_SERVER | Host that is only a media server. |
POLICY | A policy object |
dbid | The database ID of the object. This field is optional and is written when the data is exported. It is very useful in cases where you want to update or declare objects. Because the dbid is an ID in the database, lookups are much faster. So, it is recommended to use the dbid to speed up the overall XML processing whenever possible. This ID is entirely database dependant and is created when the object is created. One cannot specify an object to have a specific dbid. |