HP Insight Management WBEM Providers for HP integrated VMware ESXi 5.0 U1 June 2012 Profiles

WBEM TC Template
14 DMTF Confidential Version 0.9.1
system1:
HP_ComputerSystem
cpu1: HP_Processor:
prof3: CIM_RegisteredProfile
RegisteredOrg: DMTF (2)
RegisteredName: Base Server
prof2:
CIM_RegisteredProfile
RegisteredOrg: DMTF (2)
RegisteredName: CPU
prof1: CIM_RegisteredProfile
RegisteredOrg: DMTF
RegisteredName: Fan
prof4: HP_RegisteredProfile
RegisteredOrg: Other (1)
OtherRegOrg: HP WBEM TC
RegisteredName: HP Base Server
prof5: HP_RegisteredProfile
RegisteredOrg: Other (1)
OtherRegOrg: HP WBEM TC
RegisteredName: HP CPU
HP_ExtendsProfile
prof6: HP_RegisteredProfile
RegisteredOrg: Other (1)
OtherRegOrg: HP WBEM TC
RegisteredName: HP Fan
HP_ExtendsProfile
HP_SystemFan
HP_SystemProcessor
HP_ExtendsProfile
CIM_ElementConformsToProfile
Interop Namespace
CIM_ReferencedProfile
CIM_ReferencedProfile
fan2: HP_x86Fan
prof7: HP_RegisteredProfile
RegisteredOrg: Other (1)
OtherRegOrg: HP WBEM TC
RegisteredName: HP x86 Fan
HP_ExtendsProfile
Figure 4 – HP PRP: Fan and Processor Object Diagram (product specific extension)
Figure 5 shows the same implementation using the central class methodology for registering profiles.
Each profile is associated to its central class via a CIM_ElementConformsToProfile (for DMTF profiles) or
an HP_ElementConformsToProfile (for HP Profiles) association. Notice that a single central class
instance can be associated to multiple profiles if the central class has been extended via an HP extension
profile. For example, the instance of the DMTF FAN profile central class HP_Fan is associated to both
the DMTF Fan profile registration and the HP Fan extension profiles. In this case, a client can tell directly
that the instance of HP_Fan conforms to both the DMTF Fan profile and the HP FAN extension profiles.