HP WBEM Services Version A.02.07 Release Notes, September 2008, Second Edition

HP WBEM Services makes it easier for software developers to create management
applications that manage HP-UX systems, and makes HP Servers and workstations
easier for system administrators to manage.
The following version of the HP WBEM Services product is now being made available:
For HP-UX: WBEMSvcs A.02.07.02
What's in This Version
HP WBEM Services for HP-UX version A.02.07.02 is a minor update to the HP WBEM
Services A.02.07 currently released with HP-UX 11i v1, 11i v2 and 11i v3.
HP WBEM Services for HP-UX version A.02.07.02 is based on OpenPegasus 2.7.1 source
base and CIM Schema 2.13.1.
The following is the key differentiator from HP WBEM Services A.02.07 to A.02.07.02:
• A new configuration parameter called idleConnectionTimeout
This option allows you to set a time period after which all idle connections are
timed out.
Following are key differentiators from HP WBEM Services A.02.05 to A.02.07:
• Audit Logging - Provides a mechanism from which auditors can use to track
various WBEM client operations and provider usages. The audits include access,
activity, and configuration changes on the selected CIM server for the WBEM
client(s).
A dynamic configuration property, enableAuditLog, is used to enable or disable
audit logging at run time. By default, enableAuditLog is set to false. You will
need to run cimconfig to enable audit logging:
# cimconfig -s enableAuditLog=true -c
By default all the audit messages are written into the system log file /var/adm/
syslog/syslog.log. Each system log file entry (e.g. in the syslog file) has a
well-defined tag (e.g. cimserver audit) to distinguish an entry made by audit
logging.
NOTE: Only those CIM "Write" events are logged, along with the timestamp.
Sensitive or private data and method parameters are not logged. The only exception
are "schema-related" parameters, such as class names and qualifier names.
• Repository Archive (cimreparchive) - Provides a mechanism to create an archive
copy of the CIM Server repository without stopping the CIM Server. Refer to the
man page for more information.
The administrator can explicitly issue lock and unlock repository update
commands, while the repository archive is being created. Keeping the "lock" and
What's in This Version 9