Reference information for CIM

The Common Information Model (CIM) standard provides the ability to develop management application that work with the systems management data that is made available by the CIM providers and included with the operating system.

The following Common Information Model Object Manager (CIMOM) functions are supported:

  • Large address-space models

    The IBM® Universal Manageability Enablement licensed program can use a maximum of 8 segments or 2 GB memory.

  • Secure Sockets Layer support
    Secure Sockets Layer (SSL) is supported both for external connections over SSL-secured ports for CIM client connections and for the connections with a CIM export client. CIMOM supports the following ports:
    • wbem-https port (5989 by default)
    • wbem-exp-https port (5990 by default)
      Note: The original wbem-http port (5988 by default) is also supported.

    In addition to the support for SSL-secured data transmission, IBM i Portable Application Solutions Environment (IBM i PASE) also supports SSL certificate-based client authentication on CIM requests from CIM clients and supports the CIM exports carrying indication data.

  • Common Manageability Programming Interface support

    Common Manageability Programming Interface (CMPI) defines a common C-based resource extension interface. Resource extensions can be reused in any management server environment supporting this interface. CMPI is implemented such that the provider can run with any CIM server, not just with Pegasus. The providers use CMPI instead of the Pegasus C/C++ interface. Currently, CMPI supports instance, method, association, and indication providers.

  • Out-of-process provider support

    Out-of-process (OOP) isolates the providers from the main CIM server by running them in a separate process. All providers are OOP providers for reliability, performance, and security reasons. With OOP, the CIM server does not crash due to a provider crash. Also, the CIM server has granular security control over providers. If one process crashes, it does not cause the crash of other processes and can recover when the next request for that given provider module comes in.

  • DMTF schema 2.29

    Schema 2.29 contains both experimental and final builds of the schema. This provides you with early access to experimental parts of the model that do not have sufficient implementation experience to be included in the final schema. Experimental elements might change in a backward-incompatible way.