Web Services Management Framework version 2'0 A presentation to WSDMTC - PowerPoint PPT Presentation

1 / 23
About This Presentation
Title:

Web Services Management Framework version 2'0 A presentation to WSDMTC

Description:

HP presentation template user tutorial. Introduction ... HP presentation template user tutorial. Submission to WSDM TC. Submission of WSMF to the WSDM TC ... – PowerPoint PPT presentation

Number of Views:44
Avg rating:3.0/5.0
Slides: 24
Provided by: williamv1
Category:

less

Transcript and Presenter's Notes

Title: Web Services Management Framework version 2'0 A presentation to WSDMTC


1
Web Services Management Framework - version
2.0A presentation to WSDM-TC
  • HP Team in OASIS WSDM TC
  • Date July 29, 2003

2
Agenda
  • Introduction
  • Technical overview
  • Current Status
  • Submission to WSDM TC
  • Call for action
  • Q/A and discussion

3
Introduction
  • Web Services Management Framework (WSMF) 2.0
    publicly released on 7/21/03
  • Specifications available at http//devresource.hp.
    com/wsmf/
  • WSMF is a set of specifications that address the
    requirements of a manageability solution for both
    MUWS and MOWS.
  • Developed by HP over the course of one year with
    input from partners and customers.
  • Share experience in the Web services Mgmt. area
    gained by developing and testing new interface
    technology with our ISV partners.
  • Contributed to OASIS WSDM TC.

4
WSMF Technical Overview
  • Whats and Whys
  • WSMF components
  • Relationship with existing technologies
  • WSMF-Foundation
  • WS-Events
  • How does it work?
  • WSMF-WSM

5
What WSMF IS
  • A manageability framework for interfacing
    management systems and resources in a platform
    (e.g. information model) independent way
  • Using Web services
  • description, discovery and access of interfaces
  • distributed computing environment
  • Open, flexible and extensible architecture
  • Flexibility in distribution of implementation and
    who, where and how many can access
  • can be implemented gradually by an ISV
  • A collection of specifications

6
What WSMF IS NOT
  • A modeling framework
  • Common modeling elements or a specific model
  • however, WSMF-WSM includes a model for Web
    services domain
  • An instrumentation or agent technology
  • A product

7
Why WSMF?
  • Started with a need to manage Web services as
    resource but there are much greater needs
  • Today's IT systems are getting complex!
  • Multiple users of manageability information
    brought on by this complexity and distribution of
    the resources being managed (e.g., federation of
    management functionality, distribution of the
    management system, "plug" management products and
    resources)
  • Management system functionality is moving towards
    the infrastructure (e.g., self healing systems,
    load balancing, cluster management)
  • IT services (or service view) introduce dynamic
    element (create/modify/EOL)
  • WSMF directly addresses some of the problems and
    provides a platform from which to address others
  • Applications need a language and platform
    independent way to expose their management
    capability
  • Web services are becoming pervasive for such uses

8
WSMF Components
Service
Conversation
WSMF-WSM
WsExecutionEnvironment
Attributes
Operations
MO interface collection
WSMF- Foundation
Error Reporting
Grouping/Categorization
Identification
Relationships
Life-cycle
Bindings
WS-Events
Notification Schema
Subscription
Delivery
Discovery
Description
Security
Messaging

Web Services
9
Relationship to the existing work
10
Relationship to the existing work
11
WSMF-Foundation Conceptual Architecture
Resources
Managed Object Hierarchy
WSDL
intf1
intf2
porttype1
Relationship
Relationship
porttype2
capabilities
collection of interfaces
12
WSMF-Foundation Architecture (Contd.)
  • Managed Objects are the management representation
    of managed resources.
  • implement collection of interfaces which define
    management capabilities.
  • supply these capabilities to the managed
    resources.
  • may be implemented as part of the managed
    resource or in a different environment.
  • When a Managed Object implements an interface, it
    is referred to as that Managed Object type.
  • Relationships define the behavior and the
    dependencies between managed objects (model) and
    consequently the resources that they represent.
  • To better support the various Web services
    managed domains, WSMF intends to remain model
    neutral and will support any model.

13
WSMF-Foundation Architecture (Contd.)
  • Collection of Interfaces are logical
    representations of a set of capabilities for MOs.
  • Collection of Interfaces have the following
    components
  • namespace
  • Attributes
  • Operations
  • Notifications
  • Each attribute, operation, or notification
    belongs to a category
  • WSMF has one abstract core interface Managed
    Object
  • There are 6 core categories
  • Monitoring
  • Discovery
  • Control
  • Performance
  • Configuration
  • Security
  • Additional categories for notifications
  • Interfaces can be further extended.

14
Dynamic Attributes and Meta Information
  • Changing the current attributes support approach
    (get/set operations per attribute) to better
    support
  • Scalability as the number of attributes increase
  • Dynamic creation of attributes
  • Bulk access to multiple attributes (without the
    use of the collection interface)
  • Various information models
  • A global pair of get/set operations
  • Add Meta information support for managed objects
    and its components (attributes, operations,
    notifications)
  • Introspection
  • Access control
  • Policies
  • Finer granularity of meta information
  • Etc.
  • Supported by
  • Direct operations
  • getOperationMetaInfo()
  • setAttributesMetaInfo()
  • Use of XPATH filters supported by a global pair
    of get/set operations

15
WS-Events
  • Base schema for event notifications
  • Subscription based delivery
  • Discovery of event types
  • Two modes of notification delivery
  • pull (synchronous)
  • push (asynchronous)
  • Exposed through Web service interfaces

16
How does it work?
  • Design time
  • From scratch (no model/implementation exists)
  • Create the model. Identify manageable resources,
    their attributes, operations, relationships and
    events.
  • Develop the WSDL of managed objects corresponding
    to manageable resources
  • Do the implementation using your favorite Web
    services platform
  • A model/implementation exists using a technology
    for which WSMF adapter does not exist
  • Create a WSMF adapter
  • A model/implementation exists using a technology
    for which WSMF adapter exists
  • Deploy the WSMF adapter

17
How does it work? (Contd.)
  • Runtime
  • A WSMF compliant manager discovers an initial
    set of managed object WSDL URLs
  • It discovers more managed objects by accessing
    relationships of already discovered managed
    objects
  • It accesses these managed objects, their
    attributes and operations through the interface
    specified in their WSDLs
  • It subscribes for event notifications and
    receives them (either in pull or push mode)
  • It can perform the same operation on a collection
    of managed objects through the collection
    interface

18
WSMF-WSM
  • WSMF-WSM is an application of WSMF-Foundation to
    providing manageability information with the
    effect that Web services can be managed by a
    management system.
  • WSMF-WSM can be further extended as required to
    support additional features of Web services
  • WSMF-WSM defines three managed objects
  • Service
  • WSEE
  • Conversation

19
WSMF-WSM
WSEE1
WSEE2
ContainedIn
ContainedIn
ContainedIn
ContainedIn
Contains
Contains
Contains
Contains
DependsOn
DependsOn
Service1
Service2
Service3
Service4
DependedUpon
DependedUpon
Contains
Contains
ContainedIn
ContainedIn
ContainedIn
CorrespondsTo
Contains
Contains
ContainedIn
Conv3
Conv5
Conv6
CorrespondsTo
Contains
Conv2
CorrespondsTo
CorrespondsTo
CorrespondsTo
CorrespondsTo
ContainedIn
Contains
ContainedIn
Conv1
CorrespondsTo
Conv4
CorrespondsTo
20
Current Status
  • Has gone through multiple rounds of HP-internal
    and partner reviews
  • HP-internal and partner implementations exist
  • Defining a WSMF/CIM mapping
  • Working with GGF
  • We have reviewed the WSMF contribution with the
    Globus in a two day working session.
  • We are working with Globus to refactor WSMF
    Foundation and Events specifications to exploit
    OGSI to achieve a more powerful expression of a
    generalized web services framework for building
    management interfaces
  • We are looking to WSDM to build on these
    interfaces to incorporate the WSMF WSM
    Foundation contributions towards management of
    web services using web services.

21
Submission to WSDM TC
  • Submission of WSMF to the WSDM TC
  • Complies with OASIS IPR policies
  • Not all parts of WSMF might be appropriate for
    the WSDM TC to tackle. HP is open to working with
    other groups (e.g. GGF) if better suited to use
    some parts of WSMF.
  • HP will commit several of the WSMF authors to
    participate in WSDM for efficiency and to provide
    the benefit of lessons learned in creating WSMF.

22
Call for action
  • WSMF is a modular and validated solution to
  • Events
  • MUWS
  • MOWS
  • The WSDM TC has the skills and variety of
    experience to improve it further.
  • Starting with a strong basis like WSMF is key to
    meeting our charter goals and schedule. And most
    importantly, meeting the needs of the industry.

Call for participation
First meeting
NOW
Final deliverable
February 13, 2003
April 2, 2003
July 28, 2003
January 2004
23
(No Transcript)
Write a Comment
User Comments (0)
About PowerShow.com