Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX 11i Version 3 Release Notes: HP 9000 and HP Integrity Servers > Chapter 5 General System Administration

HP WBEM Services for HP-UX

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

Web-Based Enterprise Management (WBEM) (http://www.dmtf.org/) is a platform and resource independent Distributed Management Task Force (DMTF) standard that defines both a common model (i.e., description) and protocol (i.e., interface) for monitoring and controlling a diverse set of resources.

The HP WBEM Services for HP-UX version A.02.05 is the HP-UX implementation of the DMTF WBEM standard for release on HP-UX 11i v3.

This product is based on The Open Group (TOG) Pegasus Open Source Software (OSS) project (http://www.openpegasus.org/).

Summary of Change

What’s New for Customers Migrating from HP-UX 11i v1 September 2005?

HP WBEM Services for HP-UX version A.02.05 is a major update to the HP WBEM Services for HP-UX version A.02.00 currently released with HP-UX 11i v1. HP WBEM Services for HP-UX version A.02.05 is based on OpenPegasus 2.5 source base and CIM Schema 2.9, whereas the HP WBEM Services for HP-UX version A.02.00 released with the September 2005 11i v1 OE is based on OpenPegasus 2.3.1 source base and CIM Schema 2.7.

The following are key differentiators from HP-UX 11i v1 to HP-UX 11i v3:

  • Association providers

  • Internationalization support for CIM operations

  • CIM Schema Upgrade

  • Out-of-Process Support

  • Run-as-Requestor Support

  • Certificate Based Authentication

  • Email and Syslog indication handlers

What’s New for Customers Migrating from HP-UX 11i v2 June 2006?

HP WBEM Services for HP-UX version A.02.05 is a major update to the HP WBEM Services for HP-UX version A.02.00 currently released with HP-UX 11i v2. HP WBEM Services for HP-UX version A.02.05 is based on OpenPegasus 2.5 source base and CIM Schema 2.9, whereas the HP WBEM Services for HP-UX version A.02.00 released with the June 2006 11i v2 OE is based on OpenPegasus 2.4.2 source base and CIM Schema 2.7.

The following are key differentiators from HP-UX 11i v2 to HP-UX 11i v3:

  • Association providers

  • Internationalization support for CIM operations

  • CIM Schema Upgrade

  • Out-of-Process Support

  • Run-as-Requestor Support

  • Certificate Based Authentication

  • Email and Syslog indication handlers

Impact

HP WBEM Services for HP-UX allows customers to manage their HP-UX systems, providing integrated solutions that optimize a customer’s infrastructure for greater operational efficiency.

Compatibility

Starting with the A.02.05 release, HP WBEM Services for HP-UX will support an option that allows a WBEM Provider (i.e., the management instrumentation) to run as the user who issued the management request. Prior to this release, all WBEM Providers executed in a privileged context. With the release of HP-UX 11i v3, WBEM Providers will, by default, be invoked in the context of the user requesting an operation (i.e., “Run-As-Requestor”). This default setting can break backward compatibility for certain types of Providers.

This means that existing Providers that run in the user context of the CIM Server may break. To remedy this situation, developers have the following alternatives:

  1. To continue running their Provider in a privileged context, developers will need to explicitly register their Provider to run in a “Privileged User” context. This is a configuration file change and should not require a change to the Provider library. That is, developers will not be required to recompile/relink their providers to continue running in a privileged context.

    To register their Provider to run in a “Privileged User ” context, developers need to modify the PG_ProviderModule instance definition in their Provider Registration mof as follows:

    1. Change the InterfaceVersion from “2.1.0” to “2.5.0

    2. Add the new property UserContext = 2

      Example using an updated PG_ProviderModule instance definition for the OperatingSystem Provider Module:

      instance of PG_ProviderModule

      {
      Name = "OperatingSystemModule";
      Vendor = "OpenPegasus";
      Version = "2.0.0";
      InterfaceType = "C++Default";
      InterfaceVersion = "2.5.0";
      Location = "OSProvider";
      UserContext = 2;
      };
  2. To support running in the “Requestor” context, developers need to ensure that their Provider has been written to allow multiple instances of the Provider to run at the same time (in different user contexts). In some cases, the Provider may need to coordinate the actions of the Provider instances. In cases where the Provider is simply a “pass-through” to a managed resource, no coordination may 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.

Performance

There is no foreseen degradation in performance for this version of HP WBEM Services for HP-UX.

Documentation

For further information, see the HP WBEM Services for HP-UX manpages included with product:

  • cimmof(1)

  • cimprovider(1)

  • osinfo(1)

  • wbemexec(1)

  • cimauth(1M)

  • cimconfig(1M)

  • cimserver(1M)

  • ssltrustmgr(1M)

  • cimserverd(8)

  • cimtrust(1M)

In addition, see the following documents, available at http://docs.hp.com (navigate to Network and Systems Management, then to HP WBEM Services for HP-UX):

  • HP WBEM Services for HP-UX Release Notes

  • HP WBEM Services Software Developer’s Kit Release Notes

  • HP WBEM Services for HP-UX System Administrator’s Guide

  • HP WBEM Services Software Developer’s Kit for HP-UX Provider and Client Developer’s Guide

Obsolescence

Not applicable.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2006-2007 Hewlett-Packard Development Company, L.P.