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

WBEM TC Template
Version 0.9.1 DMTF Confidential 19
Figure 7 – HP PRP: HP Processor and Consolidated Status
9.2 Find all HP profiles registered in the interop namespace
The following algorithm can be followed to find HP profiles registered in the interop namespace:
• Query for all instances of HP_RegisteredProfile in the interop namespace
• For each instance of HP_RegisteredProfile found in the previous step
• Find the references of HP_RegisteredProfile (returns list of association).
• For each association instance found in previous step
• If the association instance is a HP_ExtendsProfile
• If HP_ExtendsProfile.dependent property equals the REF of this instance of
HP_RegisteredProfile, then this profile is an extension profile. The client can
determine the profile being extended by following the antecedent property of the found
HP_ExtendsProfile association instance. NOTE:It is invalid for an extension profile to
extend 2 different profiles, thus it is an error if another HP_ExtendsProfile association
is found where the dependent property equals this HP_RegisteredProfile instances
REF.
• Else if HP_ExtensProfile.antecedent property equals this HP_RegisteredProfile
instance REF then this profile has been extended and the client can follow the
HP_ExtendsProfile.dependent to determine the profile that extends this profile
instance. NOTE: It is valid for a profile to be extended by multiple extension profiles.
Therefore, it is not an error for this case to be hit for multiple given
HP_RegisteredProfile instances.
• If the association instance is a HP_ReferencedProfile
• If HP_ReferencedProfile.antecedent equals this instance of HP_RegisteredProfile,
then this profile references another profile. The client can determine which HP profile
this registered profile references by following the dependent REF.
• If HP_ReferencedProfile.dependent equals this instance of HP_RegisteredProfile then
the profile is referenced by another profile. The client can determine which profile
references this profile by following the dependent REF.
9.3 Determining if a standard profile implementation has HP specific
extensions
The following algorithm can be followed to determine if a standard profile implementation has been
extended by a profile defined by HP:
• For any given standard profile, find its central class using the algorithms defined in DMTF Profile
Registration Profile (DSP1033).
• From the central class, find its corresponding profile registration using the algorithm defined in DSP
1033.
• Query all instances of HP_ExtendsProfile where the Antecedent property equals the instance of
profile registration found in the previous step.
• Follow the association (via the Dependent REF) to the corresponding extension profile.
• This profile will define the extension to the profile referenced in the Antecedent REF. This
includes:
• All classes that have been extended via inheritance (sub-classes)