OMI 1.0.7 Release Notes
=======================

Each section below describes a new feature or a bug that was fixed in OMI 1.0.7.

HTTP Headers visible in providers:
==================================

Caution: OMI must be configured with the --enable-httpheaders option to
use this option.

Providers may now obtain HTTP-headers passed in the originating WS-Management
request. To obtain these, the provider uses the following context methods
(see <MI.h> for details):

    MI_Context_GetCustomOptionCount()
    MI_Context_GetCustomOptionAt()
    MI_Context_GetCustomOption()
    MI_Context_GetStringOption()

Note that all HTTP-header options are of type string. Also note that each
HTTP header name is "fixed up" by prepending "HTTP_" and translating certain
characters to "_". For example:

    Content-Type

Is renamed to:

    HTTP_Content_Type

The following snippet retrieves the value of this option.

    MI_Result r;
    const MI_Char* value;

    r = MI_Context_GetStringOption(
        context,
        MI_T("HTTP_Content_Type"),
        &value);

    if (r != RESULT_OK)
    {
        /* Failed! */
    }

To use this feature, configure OMI with the --enable-httpheaders option. For
example:

    $ ./configure --enable-httpheaders ...

OMI now supports schema retrieval:
==================================

The OMI 1.0.7 server now handles "GetClass" requests from WS-Management
clients (using the WS-Transfer Get operation). The only WS-Management client
that supports "GetClass" today is WinRM. In OMI, all class information
is contained in provider libraries (the OMI server does not maintain a formal
class repository). The classes of any registered provider are subject to the
"GetClass" request, but the provider must be re-registered using the 'omireg'
tool, since the .reg files contain additional information about which classes
the provider contains. Metadata is returned as CIM-XML. For more information
on GetClass, see the DMTF "WS-Management CIM Binding Specification" (DSP0227,
version 1.1.0), section 15.

Changed the default HTTP ports:
===============================

The OMI server now listens on HTTP port and 5985 and HTTPS port 5986. Formerly
it listened on 7778 and 7779 respectively. Note that it is possible to override
this when configuring with these options:

    --httpport=HTTPPORT
    --httpsport=HTTPSPORT

For example:

    $ ./configure --httpport=7778 --httpsport=7779

Deriving from CIM_Error:
========================

Providers can now derive from CIM_Error and extend it with new custom
properties. These new properties will now be exposed to clients. For more
information on CIM_Error, see the DMTF "WS-Management CIM Binding Specification"
(DSP0227, version 1.1.0), section 12.

Bug: serialization of string-arrays between server and agent (32-bit):
======================================================================

OMI 1.0.7 fixes a bug which caused a crash when passing string-array
properties from the omiserver to the omiagent on 32-bit systems.

Bug: WQL string comparison:
===========================

WQL string comparison is now case insensitive. Formerly is was case sensitive.
For example, in the following example, the comparison is case insensitive:

        SELECT * from CIM_ComputerSystem WHERE Name = "system.1001"