Managers Development Conference

Track - Developer

The Common Manageability Programming Interface (CMPI)
Robert Kieninger, IBM

The Common Manageability Programming Interface (CMPI) is a standard interface for CIM providers published by The Open Group. It is supported by many popular CIM Servers such as OpenPegasus, OpenWBEM and SBLIM Small Footprint CIM Broker (sfcb). CMPI is a binary compatible provider interface that makes the development of CIM providers independent from a particular CIM Server implementation. The session covers the concepts of CMPI and shows the CMPI Provider Interface by the means of code examples.

JSR48 – Creating WBEM Clients & Providers using Java^TM
Jim Davis, WSI

This presentation will provide a complete description of the Java WBEM API. The presentation will include code samples and demos for client applications and instrumentation providers. JSR48 is the Java Specification Request for developing a Java WBEM API through the JCP (Java Community Process).

Implementing a Profile
Carl Chan, WSI

A profile is a definition of the set of CIM classes and properties that must be implemented to perform a particular management function. The DMTF and SNIA use profiles to promote interoperability of CIM and WBEM based management solutions and consistency of management functionality between vendors. This lecture discusses the recommended steps a developer must take to efficiently implement a profile. The lecture first explains at a high level the thought processes involved for each step that are common to all profiles. Next, the lecture will walk through a generic profile implementation example.

PyWBEM is a CIM client library written entirely in the Python programming language and distributed under the GNU GPL. PyWBEM is written with an emphasis on usability and simplicity and is suitable for tasks ranging from simple testing and exploration, to writing an entire CIMOM. This presentation will be a brief tutorial of the PyWBEM API with examples and demonstrations.

Writing WBEM Clients & Provider using C++
An Lam, 3PARdata, Inc.

This is a hands on session for client and provider developers. The session will provide coding examples and a live demo. The session will start with an overview of the different provider types (instance, method, association and indication).  The session will walk the audience through a step by step process for creating different types of providers.  The session will also walk the audience through creating a client that uses the providers developed.  The OpenPegasus C++ API and implementation will be used.

Writing a provider to send secure indications
Aparna Vasanth, Brocade

This presentation demonstrates the necessary development and configuration steps to writing a provider to deliver secure indications over SSL. The demonstration includes writing a simple provider to accept indication subscriptions and deliver both a lifecycle and alert indication, configuring the agent and its key store, and delivering the indication to a client using mutual authentication.

QA and testing for CIM/WBEM/SMI
Ernest Yu, Brocade

This presentation discussed taking your companies provider implementation and bringing it to release from a QA perspective. It will address nuances of QA for CIM/WBEM and SMI, understanding what specifications apply, gotchas, using SNIA CTP in QA, etc. It will include understanding trace output from a CIM Server and validate the defect including isolating defects to the CIM Server or the underlying provider implementation.

How to Implement CIM Providers and Listeners
An Lam, 3PARdata, Inc.

Developing CIM Indication providers and listeners is considered a challenging task for many new developers due to the complexity nature of indication and the lack of comprehensive tutorials on this topic. This presentation discusses both concepts and implementations. Some key concepts such as CIM Indication class hierarchy, indication filter, indication handler, subscription and delivery process are covered. Live demo and detailed coding examples demonstrate step-by-step how to write indication providers and listeners. Pegasus is used as a CIM Server for this demo. However, the concepts and implementations can be applied to any other CIM Server. After attending this tutorial, the audience will clearly understand how the CIM event model works and how to develop supporting code.

Introduction to Developing with OpenWBEM
Norm Paxton, Novell, Inc.

OpenWBEM is an Open Source CIMOM and WBEM framework used in many commercial products and enterprise settings.  This presentation will introduce the OpenWBEM provider and client API's by showing how to write a simple provider and simple client application.