fbpx
Wikipedia

Web-Based Enterprise Management

In computing, Web-Based Enterprise Management (WBEM) comprises a set of systems-management technologies developed to unify the management of distributed computing environments. The WBEM initiative, initially sponsored in 1996 by BMC Software, Cisco Systems, Compaq Computer, Intel, and Microsoft, is now widely adopted.[1] WBEM is based on Internet standards and Distributed Management Task Force (DMTF) open standards:

Web-Based Enterprise Management
AbbreviationWBEM
StatusPublished
Year started1996; 28 years ago (1996)
OrganizationDistributed Management Task Force
Base standardsCIM and WS-Management
DomainSystems management
Websitewww.dmtf.org/standards/wbem

Although the name labels WBEM as "web-based", it is not necessarily dependent on any particular user interface (see below). Other systems-management approaches include remote shells, proprietary solutions and IETF standardized network-management architectures like the SNMP and Netconf.

Features edit

WBEM allows the management of any element in a standard and inter-operable manner.

WBEM provides the technology underlying different management initiatives in information technology:

  • Desktop management (DASH)
  • Network management (NetMan)
    • There is a DMTF page that shows a number of DSP pdfs that are the published profiles of the NetMan Initiative[3]
  • Storage management (SMI)
  • Systems management (SMASH)
  • Virtualization management (VMAN)
    • There is a DMTF page that shows a number of DSP pdfs that are the published profiles of the VMAN Initiative[4]

Architecture edit

To understand the WBEM architecture, consider the components which lie between the operator trying to manage a device (configure it, turn it off and on, collect alarms, etc.) and the actual hardware and software of the device:

  1. The operator will invoke some form of graphical user interface (GUI), Browser User Interface (BUI), or command-line interface (CLI). The WBEM standard has nothing to say about this interface (although the definition of a CLI for specific applications has started): WBEM operates independently of the human interface, since human interfaces can change without the rest of the system needing to note such changes.
  2. The GUI, BUI or CLI will interface with a WBEM client through a small set of application programming interfaces (APIs). This client will find the WBEM server for the managed device (typically on the device itself) and construct an XML message containing the request.
  3. The client will use the HTTP (or HTTPS) protocol to pass the request, encoding it in CIM-XML, to the WBEM server.
  4. The WBEM server will decode the incoming request, perform the necessary authentication and authorization checks and then consult the previously defined model of the managed device to see how to handle the request. This model provides the power of the architecture: it represents the pivot point of the transaction, with the client simply interacting with the model and the model interacting with the real hardware or software. The model uses the Common Information Model standard; the DMTF has published many models for commonly managed devices and services: IP routers, storage servers, desktop computers, etc.
  5. For most operations, the WBEM server determines from the model that it needs to communicate with the actual hardware or software. So-called "providers" handle the interaction: small pieces of code interface between the WBEM server (using a standardized interface known as CMPI)[5] and the real hardware or software. Because the interface is well-defined and the number of types of call is small, it is normally easy to write providers. In particular, the writer of the provider knows nothing of the GUI, BUI, or CLI used by the operator.

WBEM specifications edit

  • Mappings
    • URI (WBEM URI Mapping Specification 1.0)
    • XML (xmlCIM as used in CIM-XML)
    • XML (WS-CIM as used in WS-Management)
    • UML
  • Protocols
  • Discovery
    • SLP (WBEM Discovery using SLP; SLP Template)
  • Query Language
    • CQL (CIM Query Language 1.0)[7]
    • FQL (Filter Query Language 1.0)[8]

Implementing support edit

The implementation of the management system requires three components:

  • The model
Normally done by extending as necessary one of the standard models published by the DMTF.
  • The BUI, GUI, or CLI.
The client and server usually do not need to be written because there are many open-source and commercial implementations available. (see External links below)
  • The providers
WBEM architecture allows the manufacturer of a device or developer of a service to provide a standards-compliant management interface to that device simply and cheaply.

Implementations edit

WBEM in operating systems edit

WBEM implementations edit

  • WS-Management
  • OpenPegasus, open-source client and server written in C++
  • Open Management Infrastructure, open-source client and server written in C
  • SBLIM (pronounced "sublime") Standards Based Linux Instrumentation for Manageability, C, C++, Java
  • Pywbem,[10] open-source WBEM library written in Python
  • WBEM Solutions J WBEM Server and SDK

See also edit

  • SMI-S, Storage Management Initiative - Specification. Based on WBEM, used for SAN devices
  • JSR-48, Java API for developing WBEM Clients and WBEM Providers
  • CMPI, C provider API for developing WBEM Providers

References edit

  1. ^ Todd, Greg (June 30, 1998). "What is WBEM?". Windows IT Pro. from the original on 13 November 2015. Retrieved 13 November 2015. In 1996, BMC Software, Cisco Systems, Compaq Computer, Intel, and Microsoft sponsored the Web-Based Enterprise Management (WBEM) initiative, an effort to provide a unifying mechanism for describing and sharing management information.
  2. ^ ""CIM Operations over RESTful Services" (PDF)" (PDF).
  3. ^ "DMTF NetMan page".
  4. ^ "DMTF VMAN webpage".
  5. ^ The Common Manageability Programming Interface
  6. ^ ""CIM Operations Over RESTful Services" (PDF)" (PDF).
  7. ^ ""DSP0202 - CIM Query Language Specification" (PDF)" (PDF).
  8. ^ ""DSP0212 - Filter Query Language" (PDF)" (PDF).
  9. ^ [1] Solaris WBEM Developer's Guide
  10. ^ "Pywbem Documentation".

External links edit

  • Official WBEM page at DMTF (Distributed Management Task Force), including standards documents

based, enterprise, management, computing, wbem, comprises, systems, management, technologies, developed, unify, management, distributed, computing, environments, wbem, initiative, initially, sponsored, 1996, software, cisco, systems, compaq, computer, intel, m. In computing Web Based Enterprise Management WBEM comprises a set of systems management technologies developed to unify the management of distributed computing environments The WBEM initiative initially sponsored in 1996 by BMC Software Cisco Systems Compaq Computer Intel and Microsoft is now widely adopted 1 WBEM is based on Internet standards and Distributed Management Task Force DMTF open standards Common Information Model CIM infrastructure and schema CIM XML CIM operations over HTTP WS Management for web services CIM Operations over RESTful Services 2 Web Based Enterprise ManagementAbbreviationWBEMStatusPublishedYear started1996 28 years ago 1996 OrganizationDistributed Management Task ForceBase standardsCIM and WS ManagementDomainSystems managementWebsitewww wbr dmtf wbr org wbr standards wbr wbem Although the name labels WBEM as web based it is not necessarily dependent on any particular user interface see below Other systems management approaches include remote shells proprietary solutions and IETF standardized network management architectures like the SNMP and Netconf Contents 1 Features 2 Architecture 3 WBEM specifications 4 Implementing support 5 Implementations 5 1 WBEM in operating systems 5 2 WBEM implementations 6 See also 7 References 8 External linksFeatures editWBEM allows the management of any element in a standard and inter operable manner WBEM provides the technology underlying different management initiatives in information technology Desktop management DASH Network management NetMan There is a DMTF page that shows a number of DSP pdfs that are the published profiles of the NetMan Initiative 3 Storage management SMI Systems management SMASH Virtualization management VMAN There is a DMTF page that shows a number of DSP pdfs that are the published profiles of the VMAN Initiative 4 Architecture editTo understand the WBEM architecture consider the components which lie between the operator trying to manage a device configure it turn it off and on collect alarms etc and the actual hardware and software of the device The operator will invoke some form of graphical user interface GUI Browser User Interface BUI or command line interface CLI The WBEM standard has nothing to say about this interface although the definition of a CLI for specific applications has started WBEM operates independently of the human interface since human interfaces can change without the rest of the system needing to note such changes The GUI BUI or CLI will interface with a WBEM client through a small set of application programming interfaces APIs This client will find the WBEM server for the managed device typically on the device itself and construct an XML message containing the request The client will use the HTTP or HTTPS protocol to pass the request encoding it in CIM XML to the WBEM server The WBEM server will decode the incoming request perform the necessary authentication and authorization checks and then consult the previously defined model of the managed device to see how to handle the request This model provides the power of the architecture it represents the pivot point of the transaction with the client simply interacting with the model and the model interacting with the real hardware or software The model uses the Common Information Model standard the DMTF has published many models for commonly managed devices and services IP routers storage servers desktop computers etc For most operations the WBEM server determines from the model that it needs to communicate with the actual hardware or software So called providers handle the interaction small pieces of code interface between the WBEM server using a standardized interface known as CMPI 5 and the real hardware or software Because the interface is well defined and the number of types of call is small it is normally easy to write providers In particular the writer of the provider knows nothing of the GUI BUI or CLI used by the operator WBEM specifications editMappings URI WBEM URI Mapping Specification 1 0 XML xmlCIM as used in CIM XML XML WS CIM as used in WS Management UML Protocols CIM XML WS Management CIM RS 6 Discovery SLP WBEM Discovery using SLP SLP Template Query Language CQL CIM Query Language 1 0 7 FQL Filter Query Language 1 0 8 Implementing support editThis article s tone or style may not reflect the encyclopedic tone used on Wikipedia See Wikipedia s guide to writing better articles for suggestions June 2020 Learn how and when to remove this template message The implementation of the management system requires three components The modelNormally done by extending as necessary one of the standard models published by the DMTF The BUI GUI or CLI The client and server usually do not need to be written because there are many open source and commercial implementations available see External links below The providersWBEM architecture allows the manufacturer of a device or developer of a service to provide a standards compliant management interface to that device simply and cheaply Implementations editWBEM in operating systems edit Apple Inc uses an implementation of WBEM in its Apple Remote Desktop management tool and Mac OS X clients ship with support for Remote Management Hewlett Packard has included WBEM Services CORE Product in the HP UX operating system with all operating environments since version 11iv1 and OpenVMS V8 3 1H1 and V8 4 IBM ships support in z OS and AIX Microsoft has developed the WMI technology and has included it in Microsoft Windows Red Hat ships OpenPegasus as part of Red Hat Enterprise Linux Oracle has WBEM Services for the Solaris operating environment 9 Ubuntu ships with an updated CIM instrumentation stack powered by the latest version of the lightweight CIMOM SBLIM SFCB WBEM implementations edit WS Management OpenPegasus open source client and server written in C Open Management Infrastructure open source client and server written in C SBLIM pronounced sublime Standards Based Linux Instrumentation for Manageability C C Java Pywbem 10 open source WBEM library written in Python WBEM Solutions J WBEM Server and SDKSee also editSMI S Storage Management Initiative Specification Based on WBEM used for SAN devices JSR 48 Java API for developing WBEM Clients and WBEM Providers CMPI C provider API for developing WBEM ProvidersReferences edit Todd Greg June 30 1998 What is WBEM Windows IT Pro Archived from the original on 13 November 2015 Retrieved 13 November 2015 In 1996 BMC Software Cisco Systems Compaq Computer Intel and Microsoft sponsored the Web Based Enterprise Management WBEM initiative an effort to provide a unifying mechanism for describing and sharing management information CIM Operations over RESTful Services PDF PDF DMTF NetMan page DMTF VMAN webpage The Common Manageability Programming Interface CIM Operations Over RESTful Services PDF PDF DSP0202 CIM Query Language Specification PDF PDF DSP0212 Filter Query Language PDF PDF 1 Solaris WBEM Developer s Guide Pywbem Documentation External links editOfficial WBEM page at DMTF Distributed Management Task Force including standards documents Retrieved from https en wikipedia org w index php title Web Based Enterprise Management amp oldid 1208499201, wikipedia, wiki, book, books, library,

article

, read, download, free, free download, mp3, video, mp4, 3gp, jpg, jpeg, gif, png, picture, music, song, movie, book, game, games.