|  |
WSDM Browser for CIM and OSGi
A demonstration of WSDM's interface, which allows a single application to manage disparate types of resources. (This is an ETTK technology.)
Date Posted: December 14, 2005
|
This is an  technology.
|
|
|
|
Update: September 14, 2006
Updated configuration file now refers to two CIM servers accessible via the Internet.
What is WSDM Browser for CIM and OSGi?
Web Services Distributed Management (WSDM) is an Oasis standard for Web services management. It provides a flexible Web services interface that can manage a wide variety of resources. WSDM does not define resource models. These design criteria make WSDM an excellent candidate for a generalized front-end interface to back-end resources served by other management technologies.
WSDM Browser for CIM and OSGi is a demonstration that illustrates how WSDM's consistent interface allows a single application to manage disparate types of resources without requiring any special knowledge of the types of resources, their models, or their implementation technologies. This demonstration shows WSDM's flexibility as an interface to two different management technologies and models: Windows Common Information Model CIM/WMI WindowManagement Instrumentation (WMI) objects and OSGi devices. The demonstration also shows interoperability between the WSDM implementation to WMI on Microsoft .Net and the WSDM browser implementation on WebSphere®.
This demonstration consists of several components:
- WSDM resource browser: This WebSphere-based Web application is capable of viewing WSDM resources and resource collections.
- WSDM interface to CIM/WMI: This interface is a partial implementation of the CIM to WSDM mapping proposal submitted to the Distributed Management Task Force (DMTF) CIM working group. It is written using Microsoft .Net, demonstrating that WSDM implementations based on different tool sets can be interoperable.
- New in the updated release is a WSDM-CIM bridge that also provides a partial implementation of the above-referenced CIM-to-WSDM mapping proposal. This bridge is able to communicate with existing CIM servers that support CIM-XML.
The WSDM Browser is preconfigured to point to an IBM System p and IBM System i CIM server. Specifically, one can view system properties such as operating system and processes running through the WSDM browser. The WSDM Browser can also be used to browse CIM information on your own System z or System i servers.
Additional information about CIM on z/OS is available in the z/OS V1R7.0 Common Information Model (CIM) User's Guide (PDF). Information about CIM on i5/OS is available at the iSeries infocenter for CIM.
- WSDM interface to DMS (Device Management Server): This interface allows management of multiple types of pervasive devices including OSGi devices. It provides another example of WSDM's ability to serve as an interface to disparate resources.
Documentation for installation on their respective run-time environments, as well as usage information, is included in the downloadable packages.
This technology is part of the Emerging Technologies Toolkit (ETTK), a special collection of emerging technologies from IBM's software development and research labs.
How does it work? The WSDM-CIM/WMI mapping provides a WSDM Web services interface and interacts with WMI in order to access CIM objects within the current Windows environment. It is installed on the user's machine and runs on IIS.
The WSDM-CIM bridge provides a WSDM Web service interface. It uses the SBLIM CIM Java™ client to communicate with CIM servers that are compliant with CIM-XML. The bridge is installed on the user's machine and runs on WebSphere.
The WSDM interface to DMS is a Web service deployed on WebSphere, which communicates with a Device Management Server (DMS) instance also running within WebSphere on Linux. This service is hosted on alphaWorks and is not installed on the user's local machine.
The WSDM browser is a servlet hosted by WebSphere, which acts as a WSDM client. This client makes standard WSDM requests against a list of Endpoint References (EPRs), which are configured in a user-editable file. The WSDM resource browser is downloaded and installed on a user's machine. It is preconfigured to refer to the WSDM-DMS Web service hosted by alphaWorks and to the WSDM-CIM service on the local machine.
|
|
|
| | About the technology author(s):
David Melgar is a software developer at the IBM Research Triangle Park (RTP), N.C. He has been actively involved in IBM and Tivoli systems management product development since 1995. Mr. Melgar currently works within the Emerging Standards organization and is a member of the Oasis WSDM Technical Committee (T.C.); he has been working with Web Services and emerging standards since 2000.
Barry Atkins works as an advisory software developer for the Emerging Technologies Toolkit (ETTK) team at IBM RTP. Mr. Atkins is a member of the OASIS WSDM T.C. and has been involved in Blackberry-specific implementations of the WSDM technology. He has been working with Web Services and emerging standards since 2000.
James Snell is a member of IBM's Software Standards Strategy Group, which focuses on the prototype development of pre-emerging software technologies and standards. He is currently a member of the Emerging Technologies Toolkit for Web Services and Autonomic Computing development team. Mr. Snell has made significant direct and indirect contributions to nearly every aspect of IBM's Web services and Service-Oriented Architecture strategy, as well as serving as a strong advocate for the practical application of key emerging technologies within and across IBM's own lines of business.
Brian Price is a software developer at IBM RTP. As part of the Emerging Technologies Tookit development team, Mr. Price has been involved with the implementation of emerging Web service standards and specifications for several years.
Ginny Ghezzo and Matthew Marum also contributed to this technology.
|
|
|
| |
|
