HP Model 755/125cL HP-UX DMI 2.0 Developer's Guide: HP-UX/HP 9000 Computers, - Page 26

Static vs. Dynamic Data

Get HP Model 755/125cL - Workstation PDF manuals and user guides View all HP Model 755/125cL manuals
Add to My Manuals
Save this manual to your list of manuals

Page 26 highlights

Component Interface Concepts Static vs. Dynamic Data Figure 3-1 Static vs. Dynamic Data Components have one or more named attributes that collectively define the information available to a management application. Attributes are collected into named groups for ease of reference. So, within a system, there are many components, each with one or more groups. Each group has one or more attributes. System Components Showing Groups and Attributes The data stored within attribute values may be dynamic or static. If the data is unlikely to change, you should consider making the data static. If the data is likely to change often, you should make the data dynamic. The following paragraphs describe the differences between the two types of data and provide some examples. Static data does not require component instrumentation to get and set its attribute values. Instead, the attribute values are stored in an associated MIF file and installed into the SP's MIF (information) database. The DMI SP gets and sets the data from the MIF. The following example shows the attribute values of ComponentID: a group required by the MIF file. If a management application needs the attribute value for Manufacturer, the SP gets the attribute value directly from the MIF database and returns it to the management application: Start Component Name = "DMTF Unix Standard Groups Definition" Description = "The DMTF system standard groups" "definition for Unix vendors." Start Group Name = "ComponentID" Class = "DMTF|ComponentID|001" 26 Chapter 3

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
26
Chapter 3
Component Interface Concepts
Static vs. Dynamic Data
Static vs. Dynamic Data
Components have one or more named attributes that collectively define
the information available to a management application. Attributes are
collected into named groups for ease of reference. So, within a system,
there are many components, each with one or more groups. Each group
has one or more attributes.
Figure 3-1
System Components Showing Groups and Attributes
The data stored within attribute values may be dynamic or static. If the
data is unlikely to change, you should consider making the data static.
If the data is likely to change often, you should make the data dynamic.
The following paragraphs describe the differences between the two
types of data and provide some examples.
Static data does not require component instrumentation to get and set
its attribute values. Instead, the attribute values are stored in an
associated MIF file and installed into the SP's MIF (information)
database. The DMI SP gets and sets the data from the MIF.
The following example shows the attribute values of ComponentID: a
group required by the MIF file. If a management application needs the
attribute value for Manufacturer, the SP gets the attribute value
directly from the MIF database and returns it to the management
application:
Start Component
Name = "DMTF Unix Standard Groups Definition"
Description = "The DMTF system standard groups”
“definition for Unix vendors."
Start Group
Name = "ComponentID"
Class = "DMTF|ComponentID|001"