Web Services Management Framework by Umut Bultan & Gül Hünerkar.

Slides:



Advertisements
Similar presentations
Web Services Architecture An interoperability architecture for the World Wide Service Network.
Advertisements

Research Issues in Web Services CS 4244 Lecture Zaki Malik Department of Computer Science Virginia Tech
TSpaces Services Suite: Automating the Development and Management of Web Services Presenter: Kevin McCurley IBM Almaden Research Center Contact: Marcus.
An Introduction to Web Services Sriram Krishnan, Ph.D.
Web Service Ahmed Gamal Ahmed Nile University Bioinformatics Group
UDDI, Discovery and Web Services Registries. Introduction To facilitate e-commerce, companies needed a way to locate one another and exchange information.
Seminarium on Component-based Software Engineering Jan Willem Klinkenberg CORBA.
OASIS Reference Model for Service Oriented Architecture 1.0
1 Introduction to SOA. 2 The Service-Oriented Enterprise eXtensible Markup Language (XML) Web services XML-based technologies for messaging, service description,
J2ME Web Services Specification.  With the promise to ease interoperability and allow for large scale software collaboration over the Internet by offering.
Kmi.open.ac.uk Semantic Execution Environments Service Engineering and Execution Barry Norton and Mick Kerrigan.
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
Web services A Web service is an interface that describes a collection of operations that are network-accessible through standardized XML messaging. A.
Processing of structured documents Spring 2003, Part 6 Helena Ahonen-Myka.
Introduction to UDDI From: OASIS, Introduction to UDDI: Important Features and Functional Concepts.
Introduction SOAP History Technical Architecture SOAP in Industry Summary References.
1 Modeling Stateful Resources with Web Services ICE Ph.D lecture Byung-sang Kim.
THE NEXT STEP IN WEB SERVICES By Francisco Curbera,… Memtimin MAHMUT 2012.
CISE Demonstrator Vincent Dijkstra DG Informatics (DIGIT)
Web Services Experience Language Web Services eXperience Language Technical Overview Ravi Konuru e-Business Tools and Frameworks,
OASIS ebXML Registry Standard Open Forum 2003 on Metadata Registries 10:30 – 11:15 January 20, 2003 Kathryn Breininger The Boeing Company Chair, OASIS.
1.View Description 2.Primary Presentation 3.Element Catalog Elements and Their Properties Relations and Their Properties Element Interfaces Element Behavior.
Software Architecture Framework for Ubiquitous Computing Divya ChanneGowda Athrey Joshi.
Web Services Description Language CS409 Application Services Even Semester 2007.
High Level Architecture Overview and Rules Thanks to: Dr. Judith Dahmann, and others from: Defense Modeling and Simulation Office phone: (703)
Dr. Bhavani Thuraisingham October 2006 Trustworthy Semantic Webs Lecture #16: Web Services and Security.
EU Project proposal. Andrei S. Lopatenko 1 EU Project Proposal CERIF-SW Andrei S. Lopatenko Vienna University of Technology
(Business) Process Centric Exchanges
1 Network Management: SNMP The roots of education are bitter, but the fruit is sweet. - Aristotle.
Interoperability between Scientific Workflows Ahmed Alqaoud, Ian Taylor, and Andrew Jones Cardiff University 10/09/2008.
XML Web Services Architecture Siddharth Ruchandani CS 6362 – SW Architecture & Design Summer /11/05.
Ocean Observatories Initiative Data Management (DM) Subsystem Overview Michael Meisinger September 29, 2009.
The High Level Architecture Introduction. Outline High Level Architecture (HLA): Background Rules Interface Specification –Overview –Class Based Subscription.
Web Services. ASP.NET Web Services  Goals of ASP.NET Web services:  To enable cross-platform, cross- business computing  Great for “service” based.
Environment Change Information Request Change Definition has subtype of Business Case based upon ConceptPopulation Gives context for Statistical Program.
WebService. Outline Overview of Web Services SOAP (messaging) WSDL (service description) UDDI (registry)
Distribution and components. 2 What is the problem? Enterprise computing is Large scale & complex: It supports large scale and complex organisations Spanning.
# 1 Application Integration Architecture A Framework For Standard Interface Development Gerald R. Gray, Consumers EnergyJune 23, 2008.
Secure Systems Research Group - FAU 1 A Trust Model for Web Services Ph.D Dissertation Progess Report Candidate: Nelly A. Delessy, Advisor: Dr E.B. Fernandez.
Registries, ebXML and Web Services in short. Registry A mechanism for allowing users to announce, or discover, the availability and state of a resource:
Web Service Resource Framework WSMO Presentation Jos de Bruijn Digital Enterprise Research Institute http ://
1 1 ECHO Extended Services February 15, Agenda Review of Extended Services Policy and Governance ECHO’s Service Domain Model How to…
Chapter 7: Creating and Consuming XML Web Services Understanding XML Web Services Creating XML Web Services Deploying and Discovering XML Web Services.
WS-CIM mapping using WSDM Igor Sedukhin Heather Kreger Andreas Maier
© Drexel University Software Engineering Research Group (SERG) 1 The OASIS SOA Reference Model Brian Mitchell.
AMI -ENT Service Definition Team Step-by-Step Modeling and Artifacts Generation Process.
Steve Graham WS-Notification Technical Overview OASIS WS-Notification TC F2F Thursday, April 29th, 2004.
Steve Graham WS-ResourceFramework Modeling Stateful Resources With Web services OASIS WSRF TC F2F Wednesday, April 28th, 2004.
Introduction to Web Services Presented by Sarath Chandra Dorbala.
© 2004 IBM Corporation WS-ResourceFramework Service Groups Tom Maguire.
1 Chapter 2 Database Environment Pearson Education © 2009.
Lecture VI: SOAP-based Web Service CS 4593 Cloud-Oriented Big Data and Software Engineering.
OASIS ebXML Registry Standard Open Forum 2003 on Metadata Registries 10:30 – 11:15 January 20, 2003 Kathryn Breininger The Boeing Company Chair, OASIS.
MIDCOM MIB Juergen Quittek, Martin Stiemerling, Pyda Srisuresh 60th IETF meeting, MIDCOM session.
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. SOA-RM Overview and relation with SEE Adrian Mocan
DEVELOPING WEB SERVICES WITH JAVA DESIGN WEB SERVICE ENDPOINT.
Dynamic/Deferred Document Sharing (D3S) Profile for 2010 presented to the IT Infrastructure Technical Committee Karen Witting February 1, 2010.
Delegation of Intent via Conversation David E. Ellis.
Service Oriented Architecture (SOA) Prof. Wenwen Li School of Geographical Sciences and Urban Planning 5644 Coor Hall
Unit – 5 JAVA Web Services
Distribution and components
Web Services CO5027.
Dugki Min Konkuk University
Unified Modeling Language
Patterns.
HP Team in OASIS WSDM TC Date: July 29, 2003
Chapter 4 Network Management Standards and Models
Chapter 4 Network Management Standards and Models
Presentation transcript:

Web Services Management Framework by Umut Bultan & Gül Hünerkar

Web Services Management Framework (WSMF) Web Services Management Framework is a management framework to provide a consistent and secure mechanism based on Web services for managing various types of resources, including Web services themselves. Web Services Management Framework is a management framework to provide a consistent and secure mechanism based on Web services for managing various types of resources, including Web services themselves.

Hewlett-Packard & WSMF WSMF is HP’s effort to create an industry standards-based platform for Web-services management. WSMF is HP’s effort to create an industry standards-based platform for Web-services management. WSMF is an accepted standard by OASIS (Organization for the Advancement of Structured Information Standards), an international consortium focused on the development and adoption of e-business standards for information exchange. WSMF is an accepted standard by OASIS (Organization for the Advancement of Structured Information Standards), an international consortium focused on the development and adoption of e-business standards for information exchange.

Advantages of WSMF Current standards (eg. SNMP, CIM)   offer subset of needed functionality   manage subset of manageable resources   manageability often secondary aspect in design WSMF: consistent and secure management of   various types of resources using Web Services   represent resources as managed objects   manage them through Web Services

Terminology Managed object: A managed object is a management representation of a resource. A managed object implements one or more management interfaces to provide a means to monitor and/or control the underlying resource. Managed object: A managed object is a management representation of a resource. A managed object implements one or more management interfaces to provide a means to monitor and/or control the underlying resource. Management interface: A management interface represents management capabilities of a resource. A management interface is presented as a set of attributes, operations, and notifications to be accessed through a WSDL portType. Management interface: A management interface represents management capabilities of a resource. A management interface is presented as a set of attributes, operations, and notifications to be accessed through a WSDL portType. Interface collection: An interface collection is a group of management interfaces that represent the management capabilities of a type of managed object. Interface collection: An interface collection is a group of management interfaces that represent the management capabilities of a type of managed object. Event: An event is a change in the state of a resource or request for processing. Event: An event is a change in the state of a resource or request for processing. Notification: A notification is a message that is sent to or retrieved by one or more subscribers to inform them that an event has occurred. Notification: A notification is a message that is sent to or retrieved by one or more subscribers to inform them that an event has occurred.

Terminology Subscriber: A subscriber is an entity that is interested in selected notifications from managed objects. These notifications contain information about the state change in a managed object. Subscriber: A subscriber is an entity that is interested in selected notifications from managed objects. These notifications contain information about the state change in a managed object. Resource: A resource is a component of a deployed environment. Resource: A resource is a component of a deployed environment. Relation: A relation is a type of association between two managed objects. Relation: A relation is a type of association between two managed objects. Relationship: A relationship specifies two managed objects and the relation to define how two specific objects are associated. Relationship: A relationship specifies two managed objects and the relation to define how two specific objects are associated. Model: A model is a set of objects, properties, and their relationships. Model: A model is a set of objects, properties, and their relationships.

Specification Documents WSMF-Foundation defines the base framework for management using Web services. WS-Events defines the Web services based event notification mechanism. This mechanism is used by WSMF-Foundation. WSMF-Web Services Management defines the model for management of Web services.

Managed Object and Management Interfaces A managed object provides management capabilities by implementing management interfaces. Management interfaces are grouped into collections of interfaces to describe a group of management capabilities about a specific type of managed object.

Managed Object and Management Interfaces(Cont) A management interface have:   Attributes: The set of properties representing information about a managed object.   Operations: The set of functions that can be provided to support the management of a managed object.   Notification types: The set of events and state changes that can be reported by a managed object Management interfaces are mapped to WSDL portTypes.

Attributes and Operations WSMF groups attributes and operations into six categories defined by OSI. The categories are:   monitoring   discovery   control   performance   configuration   Security Attributes support different access policies   read-only and read/write.

Relations and Relationships A relation specifies only the association without the context of which objects are part of the association. Examples are: dependsOn, isDuplicatedBy, isTheSameColorAs, etc. A relation specifies only the association without the context of which objects are part of the association. Examples are: dependsOn, isDuplicatedBy, isTheSameColorAs, etc. A relationship adds the context of the participants in the association. A relationship is an ordered association. For example, "A dependsOn B", is not the same as "B dependsOn A". A relationship adds the context of the participants in the association. A relationship is an ordered association. For example, "A dependsOn B", is not the same as "B dependsOn A". Think of the relation as a verb, one managed object as the subject, and the other managed object as the object of the relationship. Think of the relation as a verb, one managed object as the subject, and the other managed object as the object of the relationship.

Events and Notifications There are two modes to get notifications:   In the push mode, when an event occurs, the managed object sends a notification to the subscribers to inform them of a change of state.   In the pull mode, the subscriber issues calls to the managed object to request all the notifications that happened since the last pull call. In both modes, a subscribe call is used to register an interest for one or more event types

WS-Events Event Producer: An event producer is an entity which generates notifications. Event Producer: An event producer is an entity which generates notifications. Event Consumer: An event consumer is a receiver of notifications. Event Consumer: An event consumer is a receiver of notifications. Event Broker: An event broker is an entity which routes notifications. Brokers typically aggregate and publish events from other producers. An event broker can also apply some transformation to the notifications it processes. Event Broker: An event broker is an entity which routes notifications. Brokers typically aggregate and publish events from other producers. An event broker can also apply some transformation to the notifications it processes.

Event Discovery GetAllEventTypes() : returns the list of all events accesible by an event consumer (namely EventTypeList) GetAllEventTypes() : returns the list of all events accesible by an event consumer (namely EventTypeList) GetEventType Definition(): returns the detailled definition of an event (namely EventTypeDefinitionList) GetEventType Definition(): returns the detailled definition of an event (namely EventTypeDefinitionList) GetEventInstanceInfo(): returns events that have happened before a subscriber started its subscription (namely EventInstanceInfoList) GetEventInstanceInfo(): returns events that have happened before a subscriber started its subscription (namely EventInstanceInfoList)

Event Discovery Example

Event Notification Subscription Subscriptions allow the notification producer to plan and allocate resources depending on Subscriptions allow the notification producer to plan and allocate resources depending on  the number of subscribers  event notification types  access modes  length of subscriptions Subscriptions have a limited duration in time. For instance, it might last for an hour. This ensures that if a subscriber went away and forgot to cancel its subscription, resources would not be held indefinitely and recovered by the event producer. Subscription can be renewed before it expires. Subscriptions have a limited duration in time. For instance, it might last for an hour. This ensures that if a subscriber went away and forgot to cancel its subscription, resources would not be held indefinitely and recovered by the event producer. Subscription can be renewed before it expires.

Event Notification Subscription Example

Web Services Management(WSM) Application of WSMF-Foundation to management of (resources involved in) Web Services Managed object types:   Web Service   Web Services Execution Environment(hosts Web Services)   Conversation(individual view of this interaction) Relations:   contains/contained-in   depends-on/dependent-on   corresponds-to

WSM Relations A WSExecutionEnvironment contains 0 to many Services A WSExecutionEnvironment contains 0 to many Services A Service is contained in a WSExecutionEnvironment A Service is contained in a WSExecutionEnvironment A Service depends on 0 to many Services A Service depends on 0 to many Services A Service is depended upon by 0 to many Services A Service is depended upon by 0 to many Services A Service contains 0 or more Conversations A Service contains 0 or more Conversations A Conversation is contained in a Service A Conversation is contained in a Service A Conversation corresponds to one or more Conversations A Conversation corresponds to one or more Conversations

Conclusion We argue that Web services technologies form the likely future platform for management since it is language and platform independent, interoperable, industry momentum and it hides implementation. We argue that Web services technologies form the likely future platform for management since it is language and platform independent, interoperable, industry momentum and it hides implementation. Currently there is no standard for managing Web Services. Further work is needed. Currently there is no standard for managing Web Services. Further work is needed.