Overview of WS-Management, CIM-XML, WS-CIM Rick Landau System Management Architecture & Standards 2006/04/04 v0.4.

Slides:



Advertisements
Similar presentations
Pierre-Johan CHARTRE Java EE - JAX-RS - Pierre-Johan CHARTRE
Advertisements

Oct, 26 th, 2010 OGF 30, NSI-WG: Network Service Interface working group Web Services Overview Web Services for NSI protocol implementation
CTO Office - Standards & System Management Architecture 1 Rick Landau CTO Office, Standards & System Management Architecture Sept 2007 Understanding Web.
What's a Proxy Printer Provider? PWG WIMS-CIM Working Group Rick Landau Dell, CTO Office 2008/07/15 v0.1.
1Copyright © 2008, Printer Working Group. All rights reserved. PWG WIMS-CIM WG Status Rick Landau, Dell PWG F2F Meeting Phoenix,AZ April 2008.
Status of the Proxy Printer Provider Prototype PWG WIMS-CIM Working Group Rick Landau Dell, CTO Office 2008/10/21 v0.2.
What's a Proxy Printer Provider? PWG WIMS-CIM Working Group Rick Landau Dell, CTO Office 2008/08/08 v0.2.
PWG F2F Mtg June 2008 WIMS-CIM WG What's a Prototype Proxy Printer Provider Rick Landau Dell, CTO Office 2007/06/25 v0.1.
18 Copyright © 2005, Oracle. All rights reserved. Distributing Modular Applications: Introduction to Web Services.
Addition Facts
cetis SWNI: Implementation & Testing By Scott Wilson, CETIS.
EThOSnet Repositories and Web Services Workshop 2 nd June2009 Richard Green
Overview Environment for Internet database connectivity
CIS* Service-Oriented Computing
Server Access The REST of the Story David Cleary
Copyright © 2010 Accenture All Rights Reserved. 1 Copyright © 2010 Accenture All Rights Reserved. Accenture, its logo, and High Performance Delivered are.
Web Service Architecture
Chapter 19 – Service-oriented Architecture
Service Description: WSDL COMP6017 Topics on Web Services Dr Nicholas Gibbins –
Yunling Wang VoIP Security COMS 4995 Nov 24, 2008 XCAP The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
CSE 6331 © Leonidas Fegaras Web Services1 Web Services (adapted from Erdogan Dogdu's presentation) Leonidas Fegaras.
Component-Based Software Engineering Main issues: assemble systems out of (reusable) components compatibility of components.
IONA Technologies Position Paper Constraints and Capabilities for Web Services
WS-RT Update Ian Robinson. WS-RT and WSRF Page 2 WS-ResourceTransfer – from Roadmap document [1] WS-Transfer (Sep 2004) WS-Metadata Exchange 1.1 (new)
An Introduction to Web Services Sriram Krishnan, Ph.D.
31242/32549 Advanced Internet Programming Advanced Java Programming
Node Lessons Learned James Hudson Wisconsin Department of Natural Resources.
Proposed update of Technical Guidance for INSPIRE Download services based on SOS Matthes Rieke, Dr. Albert Remke (m.rieke, 52°North.
Addition 1’s to 20.
Presentation 7 part 2: SOAP & WSDL.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 31 Slide 1 Service-centric Software Engineering 1.
FRED Interlinked Registries DRAFT roadmap for consideration.
General introduction to Web services and an implementation example
Accessing PI System using OPC Unified Architecture
Simple Object Access Protocol (SOAP) v1.1 CS-328 Dick Steflik.
SOAP.
XML in the real world (2) SOAP. What is SOAP? ► SOAP stands for Simple Object Access Protocol ► SOAP is a communication protocol ► SOAP is for communication.
SOAP SOAP is a protocol for accessing a Web Service. SOAP stands for Simple Object Access Protocol * SOAP is a communication protocol * SOAP is for communication.
Topics Acronyms in Action SOAP 6 November 2008 CIS 340.
Information Management NTU Web Services. Information Management NTU What Are Web Services? Semantically encapsulate discrete functionality Loosely coupled,
Web Services Darshan R. Kapadia Gregor von Laszewski 1http://grid.rit.edu.
Web Services Nasrullah. Motivation about web service There are number of programms over the internet that need to communicate with other programms over.
SOAP Lee Jong-uk. Introduction What is SOAP? The features of SOAP The structure of SOAP SOAP exchange message model & message Examples of SOAP.
Peoplesoft: Building and Consuming Web Services
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
Introduction to UDDI From: OASIS, Introduction to UDDI: Important Features and Functional Concepts.
© 2005 Global Grid Forum The information contained herein is subject to change without notice Leading the pervasive adoption of grid computing for research.
CIMOM Implementation. What is Pegasus? Pegasus is an open-source reference implementation of the DMTF WBEM specifications Pegasus is a work project of.
December 3-6, 2007, Santa Clara Marriott, Santa Clara, CA Wiseman: enabling JMX applications via WS-Management JSR-262(Web Services Connector): JMX apps.
Microsoft Visual Studio 2010 Muhammad Zubair MS (FAST-NU) Experience: 5+ Years Contact:- Cell#:
Microsoft Visual Studio 2010 Muhammad Zubair MS (FAST-NU) Experience: 5+ Years Contact:- Cell#:
September 12-15, 2004 Philadelphia Marriott Philadelphia, Pennsylvania Web Services Distributed Management Heather Kreger – IBM Igor Sedukhin – CA William.
XML Web Services Architecture Siddharth Ruchandani CS 6362 – SW Architecture & Design Summer /11/05.
Copyright © 2013 Curt Hill SOAP Protocol for exchanging data and Enabling Web Services.
DSP0226: WS-Management WS-Management is now a DMTF standard Based on a proposal submitted by Microsoft and Co-Authors in August 2005 Foundation of 1G Effort.
Kemal Baykal Rasim Ismayilov
WS-CIM mapping using WSDM Igor Sedukhin Heather Kreger Andreas Maier
DMTF Standards Overview WBEM and CIM September 18, 2002 Andrea Westerinen Julie Schott Cisco Systems.
Overview of Pegasus An Open-Source WBEM implementation 12 June 2001 Michael Brasher Karl Version.
OASIS ebXML Registry Standard Open Forum 2003 on Metadata Registries 10:30 – 11:15 January 20, 2003 Kathryn Breininger The Boeing Company Chair, OASIS.
21 July DMTF CIM (Common Information Model) Ellen Stokes, IBM
PyWBEM Python WBEM Client: Overview Karl Schopmeyer Andreas Maier February 2016 SNIA SMI plugfest #2 Version:
Software Architecture Patterns (3) Service Oriented & Web Oriented Architecture source: microsoft.
WEB SERVICES From Chapter 19 of Distributed Systems Concepts and Design,4th Edition, By G. Coulouris, J. Dollimore and T. Kindberg Published by Addison.
WEB API.
WEB SERVICES From Chapter 19, Distributed Systems
Web Services Distributed Management
Presentation transcript:

Overview of WS-Management, CIM-XML, WS-CIM Rick Landau System Management Architecture & Standards 2006/04/04 v0.4

Stds & System Mgt Arch 2 Three Things Today WS-Management web service (WS) protocol CIM-XML WS protocol WS-CIM DMTF working group, specs

Stds & System Mgt Arch 3 What is a Web Service Many early-generation examples in the market Realistic definition – Is addressed at some URI – Uses XML to represent data – Includes an XML schema to describe a valid data structure – Uses SOAP to structure messages – Uses WSDL to describe interfaces, if necessary

Stds & System Mgt Arch 4 Interaction with a Web Service

Stds & System Mgt Arch 5 5 Why Care Easier to implement – Plain text, XML More secure – Plain text header for filtering, firewalls – Opaque contents may be encrypted – Security protocols may be layered onto base Mix and match protocol components to meet needs – Pieced together from "composable" protocols Optional add-in features, separate specs, orthogonal – If you need more function, just add headers and messages – E.g., atomic transactions

Stds & System Mgt Arch 6 Where It Fits in Dell Unified Manageability Architecture Access layer (Interface Service) Orchestration layer Resource management layer Aggregation layer (Repository/Database) Logical mapping layer (Providers) Platform layer (HW / FW / SW) Interactive Programmatic Access Interfaces Remotely accessible Existing and emerging standards Aggregation Interface Local interfaces predominantly defacto standards Logical Interface CMPI is the only open standard Platform Interface Small compact and typically low cost Managed Node Architecture Access layer Orchestration layer Resource management layer Aggregation layer Logical mapping layer Platform layer

Stds & System Mgt Arch 7 WS-Management & CIM-XML Protocols Both access protocols to repository of management data WS-Management uses new web service protocol structure CIM-XML uses older protocols (where "old" = 3-5 years)

Stds & System Mgt Arch 8 WS-Management WS protocol (suite) Originally from Microsoft, Intel, CA, BMC, Dell, et al. Being worked on in DMTF WG, in a subgroup of WIP – WIP = WBEM Infrastructure & Protocols WG of DMTF Not CIM-based per se – Could use any data model – Everyone wants to use CIM – WS-CIM WG is creating the CIM schema to be used by WS-Man and other WS protocols Specs: go to microsoft.com, search for "ws-management"

Stds & System Mgt Arch 9 WS Composed Protocols WS-Addressing (endpoint references) SOAP (envelope=header+body structure) WS-Transfer (get, put) WS-Enumeration (enumerate, pull) WS-Eventing (subscribe, unsubscribe) WS-Security (authenticate) Etc.

Stds & System Mgt Arch 10 WS-Man Operations Protocol operation specifies request and response Target: resource instance – Create, Delete – Get, Put (properties of an instance) Target: collection of instances – Enumerate (get handle), Release (handle) – Pull (instances) Target: event streams – Subscribe, GetStatus, Renew, Unsubscribe – Pull (collections of events) Normal mode is push from service to client – Ack – Etc.

Stds & System Mgt Arch 11 WS-Man Example Message : /wsman?ResourceURI=( uuid:20CBF75C-008E-4C68-AA14-F3EB9D94E617 ComputerSystem IPMI%20Controller%2032 PT60.000S

Stds & System Mgt Arch 12 WS-Man Catalog Contents Data only, accessed thru WS-Man agent Catalog lists resource class names – E.g., disk, memory, printer – Use these names to talk to agents about resource instances Catalog lists attributes of each resource class – ResourceURI – DisplayName, Keywords, Notes, Vendor – Relationships – Compliance (spec version) – Action(s), Operation(s) – SelectorSetRef(s), OptionSetRef(s), SchemaRef – FilterDialect for Enumerate & Subscribe, DeliveryMode

Stds & System Mgt Arch 13 Process of Discovery Find a node (S.E.P.) Find WS-Man service(s) on that node (S.E.P.) – Sticky point recently, general problem One system may have multiple agents, OR Multiple nodes with agents need to be correlated Read catalog to get resource classes (ResourceURIs) Enumerate resource instances of resource classes (Selectors) Get or Put to a resource instance

Stds & System Mgt Arch 14 Discovery of Multiple MAPs

Stds & System Mgt Arch 15 Where WS-Man is Implemented Windows Linux (need an open source service) Sun Solaris

Stds & System Mgt Arch 16 CIM-XML Access protocol for CIMOM data – Protocol-independent operations and data representation, plus HTTP binding – Implemented Windows WMI OpenWBEM on Suse – Docs DSP200 on dmtf.org, "CIM Operations over HTTP" DSP201, "What is xmlCIM?" Function style – Operation and arguments To be replaced by WS protocols

Stds & System Mgt Arch 17 WBEM Operations Basic read and write – GetClass, EnumerateClasses, EnumerateClassNames – GetInstance, EnumerateInstances EnumerateInstanceNames – GetProperty, SetProperty Instance create and delete – CreateInstance, ModifyInstance, DeleteInstance Metadata – CreateClass, ModifyClass, DeleteClass – GetQualifier, SetQualifier, DeleteQualifier, EnumerateQualifiers Navigation – Associators, AssociatorNames – References, ReferenceNames Invoke method Etc.

Stds & System Mgt Arch 18 CIM-XML Example M-POST /cimom HTTP/1.0 Content-Type: text/xml;charset=UTF-8 Accept: text/xml, application/xml Man: 48-CIMProtocolVersion: CIMOperation: MethodCall 48-CIMMethod: GetClass 48-CIMObject: root%2Fcimv2 User-Agent: Java1.2.1 Host: edoc5-pc Content-length: 445

Stds & System Mgt Arch 19 WS-CIM Confusion in name – "WS-CIM" used to be thought of as a single combined protocol Produced only requirements for two other protocols – Name WS-CIM reused for new data mapping effort Establishing XML schema for WS-Man and WSDM to use – Mapping datatypes and other CIM attributes to XML – Rules for algorithmic translation Example not available yet

Stds & System Mgt Arch 20 Questions?