HP-UX WBEM nPartition Provider Data Sheet

components (e.g., adding or removing cells and creating or deleting nPartitions) the
operation may fail if it accesses the nPartition Provider on Windows or Linux.
2. Setting Up This Provider
 Installing this Provider on HP-UX 11i: This provider is installed with the
bundle NPar. The provider executable is:
/opt/nparprovider/lib/libHPNParProvider.1
 Installing this Provider on Microsoft Windows: A Windows Installer (.msi)
file is provided for installing the nPar provider on Microsoft Windows 2000
SP3, Windows XP, and Windows Server 2003. Simply double-click the .msi
file to initiate the installation. Note that on Windows, the nPar provider is
installed as a WMI (Windows Management Instrumentation – Microsoft’s
implementation of the WBEM standard) provider, and therefore is accessible
via the WMI client API’s on Windows. You may also access the Windows
nPar provider using the Pegasus client API’s and the “WMI Mapper” (part of
the Pegasus distribution, also delivered and installed with the nPar provider on
Windows).
 Installing this Provider on Linux: This provider is installed with the
hp.com-npartition-providers RPM. The provider executable is:
/opt/hp/nparprovider/lib/libHPNParProvider.1
 Configuring this Provider: The provider is initially configured to manage
the complex on which the provider is installed. The provider can be configured
to manage remote complexes by creating instances of the class
HP_NParRemoteComplex. A client application can create an instance of this
class to configure the provider to access a particular remote complex, and
delete the instance to deconfigure the provider so that it cannot access that
remote complex.
3. Using This Provider
 Schema supported by this provider
The tables below describe the properties and methods supported by the
provider. The property tables have 3 columns. The first is the property name
including types and units. The second is the property inheritance, including
which class or superclass defines the property. The third is a description of the
possible values and, where relevant, the data source for each property. Each
row describes a property. The tables of extrinsic methods (those that are
explicitly declared in each class) also have 3 columns. The first lists the
method name and signature. The second describes the action of the method
and all return values and arguments. The third column lists exceptions that
might be thrown by the method, if any.