HP WBEM Services Software Developer's Kit for HP-UX Provider and Client Developer's Guide A.01

Provider Implementation
Provider Design Considerations
Chapter 462
ClassName = "ACME_ComputerSystem"; // required
namespaces = { "root/cimv2" }; // required
ProviderType = { 2 }; // 2=InstanceProvider // required
SupportedProperties = NULL; // NULL=All properties
SupportedMethods = NULL; // NULL=All methods
};
The instance of PG_ProviderCapabilities in Example 4-8 informs the
CIM Server as follows:
• This capability instance is for a provider named
ACME_ComputerSystemProvider in the module
ComputerSystemModule.
• There can be more than one instance for the same provider; this one
has a unique CapabilityID of 1. A different set of capabilities might
specify a different class instrumented by this provider, or the same
(or different) classes in different namespaces, possibly with different
characteristics.
• The ClassName property identifies the class instrumented by the
provider. A single provider can support more than one class, but each
Capabilities instance describes the provider's capabilities for a single
class. If, for example, the provider will respond to operations at
different levels of the model hierarchy, additional Capabilities
instances would be required. In this example, we could have another
Capabilities instance specifying that the same provider supports
operations on CIM_ComputerSystem, the parent class of
ACME_ComputerSystem.
• The provider instruments ACME_ComputerSystem only in the
root/cimv2 namespace. It is possible to support the same class in
several namespaces with the same provider. Note that the definition
of the instrumented class itself (ACME_ComputerSystem, in this
example) must be declared in the specified namespace.
• This provider implements the Instance Provider interface,
supporting instance manipulation operations. The values for the
ProviderType property are:
— Instance
— Method