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

Management Interface Format MIF, MIF Database, MIF File, Overlay Component

Page 15 highlights

Introduction Terminology Management Interface Format (MIF) DMTF's standard syntax for describing computer system components, groups and attributes. MIF Database The MIF database is a data store which the Service Provider maintains. It holds the following information: • Names, descriptions, and ID numbers of installed components. • Names, descriptions, classes and ID numbers of the groups within the installed components. • Names, descriptions, types, values and ID numbers of the attributes within the groups within the installed components. • Flags telling whether the attributes are stored in the MIF database (static data) or whether component instrumentation must be called to retrieve or set the attribute. • Entry points into the component instrumentation that must be called to retrieve or set attributes (dynamic data). MIF File DMI component providers ship the MIF file with the component instrumentation to describe the instrumented component. A single MIF file describes exactly one component. The component can have any number of groups and groups can have any number of attributes. The Service Provider uses the MIF file to generate entries within the MIF Database that describe the component identified by the MIF file. Overlay Component Developers write an Overlay component as a shared library. The DMI SP loads the shared library to handle requests for information related to the component. As a shared library, the Overlay component is a part of the DMI Service Provider's process. DMI SP explicitly loads and unloads the shared library as needed for each data request. Chapter 1 15

  • 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

Chapter 1
15
Introduction
Terminology
Management Interface Format (MIF)
DMTF's standard syntax for describing computer system components,
groups and attributes.
MIF Database
The MIF database is a data store which the Service Provider maintains.
It holds the following information:
Names, descriptions, and ID numbers of installed components.
Names, descriptions, classes and ID numbers of the groups within
the installed components.
Names, descriptions, types, values and ID numbers of the attributes
within the groups within the installed components.
Flags telling whether the attributes are stored in the MIF database
(static data) or whether component instrumentation must be called
to retrieve or set the attribute.
Entry points into the component instrumentation that must be
called to retrieve or set attributes (dynamic data).
MIF File
DMI component providers ship the MIF file with the component
instrumentation to describe the instrumented component. A single MIF
file describes exactly one component. The component can have any
number of groups and groups can have any number of attributes. The
Service Provider uses the MIF file to generate entries within the MIF
Database that describe the component identified by the MIF file.
Overlay Component
Developers write an Overlay component as a shared library. The DMI
SP loads the shared library to handle requests for information related
to the component. As a shared library, the Overlay component is a part
of the DMI Service Provider's process. DMI SP explicitly loads and
unloads the shared library as needed for each data request.