| LFX Database of Managed Objects (DMO): User Guide for the Database of Managed Objects | ||
|---|---|---|
| <<< Previous | Definitions and their Attributes | Next >>> |
There are two types of Attributes associated with Definitions and Instances. Core attributes are available for all definitions of every type, and are fixed by the DMO system (i.e., their type cannot be changed.) They include the following:
Table 3. Table of Core Attributes
| Core Attribute Name | Description |
|---|---|
| Definition Name | This is the unique name for the definition. This is one of the two core attributes which are mandatory. |
| Child Of | This specifies the location of the definition within the Definition Tree, by indicating the parent definition. This is the other mandatory core attribute. |
| Revision | This is a revision number, which is incremented each time the definition is changed. |
| Number | This is a unique number used to identify the definition. By default, we use a variation of ASN.1 numbering, which identifies each node in the definition tree according to its relative place in the tree, starting from the second level definitions. For example, a LAN is 1.2.1. |
| Description | The description of the definition. Not required, but certainly recommended. |
| Lock Inheritance | This is a check box, which defines whether instances for this definition and their child instances will inherit so-called "inheritable attributes." See the Chapter on inheritance for more details. |
| Owner | A select box showing the list of persons who might own this definition -- this actually functions as a default, so that when instances are created, they inherit this owner information from the definition. |
| Group | A select box showing the list of groups who might own this definition -- this actually functions as a default, so that when instances are created, they inherit this group information from the definition. |
| Type | A general way of classifying definitions (now obsolete, but retained for backwards compatibility.) New types may be added --- this is usually selected from second-level definitions. |
| Hidden | This core attribute defines whether the definition will be hidden. Rather than deleting a definition from the tree if it is not being used, it is better to mark it as hidden, so it doesn't confuse users. |
Regular Attributes are different from core attributes, in that their type, name and availability may be changed by the systems administrator. See the previous section on regular Attributes for more details.
| <<< Previous | Home | Next >>> |
| What is a regular Attribute? | Up | Viewing Definition Details |