HP WBEM Services Version A.02.09.14 Release Notes HP-UX 11i v2

1. Change the InterfaceVersion from “2.1.0” to “2.5.0”.
2. Add the new property UserContext = 4.
Example using an updated PG_ProviderModule instance definition for the Operating System
Provider Module:
instance of PG_ProviderModule
{
Name = "OperatingSystemModule";
Vendor = "OpenPegasus";
Version = "2.0.0";
InterfaceType = "C++Default";
InterfaceVersion = "2.5.0";
Location = "OSProvider";
UserContext = 4;
};
Alternative 2
To support running in the “Requestor” context, ensure that the provider is written to allow multiple
instances of the provider to run at the same time (in different user contexts). In some cases, the
provider might need to coordinate the actions of the provider instances. When the provider is a
“pass-through” to a managed resource, no coordination might be necessary.
In addition, providers running in the “Requestor” context must only perform privileged operations.
If those operations are only expected/required to succeed, when invoked by a user who already
has the necessary privileges.
Installation information
This section describes the prerequisites and the procedures for installing HP WBEM Services.
Prerequisites for installing HP WBEM Services
Following are the prerequisites for installing HP WBEM Services Version A.02.09.14:
• HP-UX 11i v2
• OpenSSL must be installed before installing HP WBEM Services Version A.02.09.14.
NOTE: After the OpenSSL updates are installed, the HP WBEM Services cimserver process
must be shutdown and restarted in order to run against any new version of OpenSSL. For
more information on shutting down and restarting the cimserver, see the HP WBEM Services
System Administrator Guide.
• Disk space requirements
HP WBEM Services requires the following disk space to install:
5 MB/
46 MB/opt
184 KB/var
1 MB/usr
Depending on the number of CIM objects to be stored in the CIM Repository, additional disk
space might be needed for the/var/opt/wbem directory.
• Port requirements
HP WBEM Services uses dedicated ports for CIM-XML traffic. Two ports are dedicated for
CIM-XML communications between CIM clients and the CIM Server. One port is dedicated
Installation information 11