HP dx7200 HP Client Management Interface Technical White Paper - Page 9

Developing Custom Solutions

Page 9 highlights

HP System Software Manager HP System Software Manager (SSM) is a valuable tool in the custom IT solution arsenal for managing HP client computers. HP SSM supports automation of software and BIOS updates, and an ability to report and modify BIOS settings through a text-based file format. Available later this year, SSM 2.0 will leverage HP CMI to provide BIOS configuration support to 32-bit and 64-bit versions of Windows in a manner familiar to users of the utility. Developing Custom Solutions The following sections describe the HP CMI architecture at a detailed level for application developers and IT professionals familiar with WMI and CIM concepts. There are several reference links at the end of this paper to learn more information on CIM and the capabilities of WMI-based management solutions. The management classes are described that are surfaced through HP CMI in managed object format (MOF) syntax. HP CMI relies on the object inheritance capability of CIM to create a flexible and extensible interface to hardware instrumentation details. Following the explanation of the properties and methods provided via HP CMI, several examples are provided to demonstrate the capability of HP CMI in handling client management tasks. The examples presented herein are based on Windows Scripting Host technology. However, any development environment capable of connecting to WMI could be used instead. Microsoft Visual Basic Scripting Edition is used to simplify the example scenarios. Hardware Sensor Information MOF Definition #pragma namespace("\\\\.\\root\\HP\\InstrumentedBIOS"); [abstract] class HP_BIOSSensor { [read] string Name; [read] string Description; [read, ValueMap {"0","1","2","3","4","5","6","7","8","9", "10","11","12"}, Values {"Unknown","Other","Temperature", "Voltage","Current","Tachometer","Counter","Switch","Lock", "Humidity","Smoke Detection","Presence","Air Flow"}] uint32 SensorType; [read] string OtherSensorType; [read, ValueMap {"0","1","2","3","4","5","6","7","8","9", "10","11","12","13","14","15","16","17","18","..", "0x8000.."}, Values {"Unknown","Other","OK","Degraded", "Stressed","Predictive Failure","Error", "Non-Recoverable Error","Starting","Stopping","Stopped", "In Service","No Contact","Lost Communication","Aborted", "Dormant","Supporting Entity in Error","Completed", "Power Mode","DMTF Reserved","Vendor Reserved"}] uint32 OperationalStatus; [read] string CurrentState; [read] string PossibleStates[]; }; class HP_BIOSStateSensor : HP_BIOSSensor 9

  • 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

9
HP System Software Manager
HP System Software Manager (SSM) is a valuable tool in the custom IT solution arsenal for managing
HP client computers. HP SSM supports automation of software and BIOS updates, and an ability to
report and modify BIOS settings through a text-based file format. Available later this year, SSM 2.0
will leverage HP CMI to provide BIOS configuration support to 32-bit and 64-bit versions of Windows
in a manner familiar to users of the utility.
Developing Custom Solutions
The following sections describe the HP CMI architecture at a detailed level for application developers
and IT professionals familiar with WMI and CIM concepts. There are several reference links at the
end of this paper to learn more information on CIM and the capabilities of WMI-based management
solutions.
The management classes are described that are surfaced through HP CMI in managed object format
(MOF) syntax. HP CMI relies on the object inheritance capability of CIM to create a flexible and
extensible interface to hardware instrumentation details.
Following the explanation of the properties and methods provided via HP CMI, several examples are
provided to demonstrate the capability of HP CMI in handling client management tasks.
The examples presented herein are based on Windows Scripting Host technology. However, any
development environment capable of connecting to WMI could be used instead. Microsoft Visual
Basic Scripting Edition is used to simplify the example scenarios.
Hardware Sensor Information
MOF Definition
#pragma namespace("\\\\.\\root\\HP\\InstrumentedBIOS");
[abstract]
class HP_BIOSSensor
{
[read] string Name;
[read] string Description;
[read, ValueMap {"0","1","2","3","4","5","6","7","8","9",
"10","11","12"}, Values {"Unknown","Other","Temperature",
"Voltage","Current","Tachometer","Counter","Switch","Lock",
"Humidity","Smoke Detection","Presence","Air Flow"}]
uint32 SensorType;
[read] string OtherSensorType;
[read, ValueMap {"0","1","2","3","4","5","6","7","8","9",
"10","11","12","13","14","15","16","17","18","..",
"0x8000.."}, Values {"Unknown","Other","OK","Degraded",
"Stressed","Predictive Failure","Error",
"Non-Recoverable Error","Starting","Stopping","Stopped",
"In Service","No Contact","Lost Communication","Aborted",
"Dormant","Supporting Entity in Error","Completed",
"Power Mode","DMTF Reserved","Vendor Reserved"}]
uint32 OperationalStatus;
[read] string CurrentState;
[read] string PossibleStates[];
};
class HP_BIOSStateSensor : HP_BIOSSensor